A lot of great changes have been implemented since the previous master release 3.3.3.1 4 months ago.
Dashticz 3.5 contains all changes from the beta releases.
Special thanks to @clinkadink for all the new block types, @HansieNL for maintaining the documentation, and @PietjePuck-132 for the alarmmeldingen.
And of course to all people who helped testing the beta releases.
Just newly installed Dashticz on my Raspberry Pi. So I am complete new to Dashticz. It looks great.
The doc is quite clear for the installation. A few questions.
What is the file where Dashticz makes it initial dashboard with devices from my Domoticz?
Why have a number of blocks the same name? See picture below? Can not find this in the doc.
The file 'custom/CONFIG.js' contains the Dashticz configuration. If not screens/columns have been defined in CONFIG.js then Dashticz will show all you Domoticz devices that are marked as Favorite.
The devices you see are the subdevices of a P1 smart meter. In general, if a Domoticz device contains several data items, like a P1 Smart Meter, or a TemperatureHumidityBarometer device, for each data element a block will be created.
If you only want to show a specific subdevice, for instance subindex 2 of device 34, then use the following key in CONFIG.js: '34_2'
For a temphumbar device it's possible to combine the data into a single block by setting the block parameter 'single_block' to true. (not yet documented ...)
I experience the same problem. Does that mean I have to add this switch to every block on my dashboard? I mean, it's a matter of starting and finishing the job, but why is this necessary all of a sudden? You want, for instance, to read the temperature, knowing the place of the block on the screen. Therefore the title text is not that important, but the sensor value is.