You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When integrating my AgoControl environment with Domoticz/Dashticz I noticed that Dashticz behaves weird when working with devices that are essentially just a barometer, i.e. without a temperature component.
When checking main.js, in particular getTempBumBarBlock I understand that a Temp block is always being created, even in the case that no temp information will be available.
The issue was quickly fixed by making the creation of the Temp Block depending on the presence of a Temperature device. What I'm not sure is whether I'm destroying a certain concept that I overlooked or whether this was a real ommision.
What is the device type and the device subtype? (You can find them in the Domoticz devices overview)
Interpreting the original code then sometimes there is no 'temperature' field, but only a 'data' field. In that case the 'data' field should be interpreted as temperature. I think we should keep that behavior.
When integrating my AgoControl environment with Domoticz/Dashticz I noticed that Dashticz behaves weird when working with devices that are essentially just a barometer, i.e. without a temperature component.
When checking main.js, in particular getTempBumBarBlock I understand that a Temp block is always being created, even in the case that no temp information will be available.
The issue was quickly fixed by making the creation of the Temp Block depending on the presence of a Temperature device. What I'm not sure is whether I'm destroying a certain concept that I overlooked or whether this was a real ommision.
The text was updated successfully, but these errors were encountered: