dashticz field naming?
Posted: Monday 06 February 2023 11:58
When developing my dashticz dashboards I often have great difficulty finding the correct identification/naming of the fields to use.
For example I want to add a customHeader to a graph with data from 2 sensors:
1) One is a kWH device and therefore I include "devices[3].Usage" (with capital) in the header definition and this works fine (the domoticz field is "usage" without a capital)
2) The other is a custom sensor and therefore I try "devices[106].SensorValue" (since the domoticz field is sensorValue) but this results in "undefined" to be displayed. I have tried many other variations........ The only solution I have found is to use "devices[106].Data" but this then also includes the unit of measure.
In custom graphs I can use d.v_3 but then this is not working in custom headers.
What is the logic for conversion from domoticz to dashticz naming? Where can I find this in the documentation?
For example I want to add a customHeader to a graph with data from 2 sensors:
1) One is a kWH device and therefore I include "devices[3].Usage" (with capital) in the header definition and this works fine (the domoticz field is "usage" without a capital)
2) The other is a custom sensor and therefore I try "devices[106].SensorValue" (since the domoticz field is sensorValue) but this results in "undefined" to be displayed. I have tried many other variations........ The only solution I have found is to use "devices[106].Data" but this then also includes the unit of measure.
In custom graphs I can use d.v_3 but then this is not working in custom headers.
What is the logic for conversion from domoticz to dashticz naming? Where can I find this in the documentation?