v3.4.1: Redesign block definition

Note

Breaking changes. See notes below.

Although not so visible from the outside v3.4.1 contains a significant design update on how Dashticz blocks are managed internally.

Some advantages:

• You can use the same Domoticz ID with different block settings:

  blocks['first_one'] = {
      idx: 123,
      width:4
  }
  
  blocks['second'] = {
      idx: 123,
      width:12
  }
  
  columns[1]['blocks'] = [
      'first_one', 'second'
  ]
  

This will display Domoticz device <123> twice: the first one having width 4, the second one having width 12.

• Inline block definition:

  columns[1]['blocks'] = [
      { idx: 123, width: 4},
      { idx: 123, width: 12}
  ]
  

This will give the same results as the previous example.

• The on and off classes will be added automatically to a switch-block. This enables auto-hide possibility in combination with the addClass parameter

blocks[123] = {
    addClass: 'myClass'
}

And in custom.css:

.myClass.off {
    display: none
}

Block parameters

Note

Breaking change: refresh interval parameter

Setting the refresh interval of a block now has been standardized to the refresh parameter. You may have to replace interval by refresh for some blocks. The value represents the refresh interval in seconds.

A new block parameter:

Parameter	Description
addClass	The CSS class name, that will be added to the block.

custom.js

Note

Breaking change: getBlock, getStatus and getChange interface in custom.js

There are changes in the function parameters for the following functions:

• getBlock_IDX

• getStatus_IDX

• getChange_IDX

These functions now receive block as parameter, containing all relevant parameters for the block.

The examples in Functionality via custom.js have been updated.