Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[shelly] Item State 0.00W #19

Closed
alaub81 opened this issue Nov 29, 2023 · 2 comments
Closed

[shelly] Item State 0.00W #19

alaub81 opened this issue Nov 29, 2023 · 2 comments

Comments

@alaub81
Copy link

alaub81 commented Nov 29, 2023

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.
Bildschirmfoto 2023-11-29 um 16 42 11

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

@markus7017
Copy link
Owner

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

@alaub81
Copy link
Author

alaub81 commented Jan 11, 2024

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.

@alaub81 alaub81 closed this as completed Jan 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants