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
I think I found a shelly binding bug. I try to explain:
I wondered, that in my influxDB persistence, only, when I restart a shelly Device, or restart the thing, I get a 0 Watt into the database. So I tried to figure out why this is happening and I think I found it. It is because ItemStateUpdatedEvent and ItemStateEvent is getting the last none zero value.
See screenshot attached.
Perhaps there is a simple fix for that. My grafana graphs are looking weird without a zero. I am using a persistence rule with at everyUpdate option. Also I do not see any continuous updates, when 0 Watt is on for a long time. But perhaps that's fine.
I hope you will understand the problem. If not, feel free to ask.
cheers
Andreas
The text was updated successfully, but these errors were encountered:
I don't het what you are meaning. The binding reads the device data and updates the channel, everything else is not under control of the binding.
Check events.log to see the updates processed by the framework
Found the problem. persistence configuration was the problem. Updating only every 30s can cause, that the 0 value, which is only published once, is not written to the database.
Hi there,
I think I found a shelly binding bug. I try to explain:
I wondered, that in my influxDB persistence, only, when I restart a shelly Device, or restart the thing, I get a 0 Watt into the database. So I tried to figure out why this is happening and I think I found it. It is because ItemStateUpdatedEvent and ItemStateEvent is getting the last none zero value.
See screenshot attached.
Perhaps there is a simple fix for that. My grafana graphs are looking weird without a zero. I am using a persistence rule with at everyUpdate option. Also I do not see any continuous updates, when 0 Watt is on for a long time. But perhaps that's fine.
I hope you will understand the problem. If not, feel free to ask.
cheers
Andreas
The text was updated successfully, but these errors were encountered: