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
Originally reported by: f-fish (Bitbucket: f-fish, GitHub: Unknown)
Loving the ability to log stuff via MQTT - thanks for this and you continued effort. On sonoff-ds18b20-debug, 1.6.8 I am tracking the mqtt messages to a text dummy device as indicated in #85 and spotted a few of these -127 messages, not often but they do happen that something is not 100% and we get a -127 for whatever the reason.
I think it is good to see that on the web UI and also in the standard MQTT topic. But maybe for domoticz sending a -127 is not ideal. Since the result could be - depending on timing ->
I know I can shift and click on the domoticz data point to remove it
, but not logging a -127 to domoticz would be much better I suspect - not logging anything to domoticz would be preferable when the read is -127.
Later Ferdie
The text was updated successfully, but these errors were encountered:
Originally reported by: f-fish (Bitbucket: f-fish, GitHub: Unknown)
Loving the ability to log stuff via MQTT - thanks for this and you continued effort. On sonoff-ds18b20-debug, 1.6.8 I am tracking the mqtt messages to a text dummy device as indicated in #85 and spotted a few of these -127 messages, not often but they do happen that something is not 100% and we get a -127 for whatever the reason.
I think it is good to see that on the web UI and also in the standard MQTT topic. But maybe for domoticz sending a -127 is not ideal. Since the result could be - depending on timing ->
I know I can shift and click on the domoticz data point to remove it
, but not logging a -127 to domoticz would be much better I suspect - not logging anything to domoticz would be preferable when the read is -127.
Later Ferdie
The text was updated successfully, but these errors were encountered: