-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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] Roller control channel flipping between 0 and 100 #10219
Labels
bug
An unexpected problem or unintended behavior of an add-on
Comments
markus7017
added
the
bug
An unexpected problem or unintended behavior of an add-on
label
Feb 23, 2021
one year later, I am still experiencing this issue. I use OH 3.2.0 and binding ver.3.2.0. Is there any workaround ? |
This issue has been mentioned on openHAB Community. There might be relevant details there: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem description
Everything works fine with the latest Shelly binding (and also the 3.0.1 stable version) with buttons, sensors, curtains and windows. The only small problem I have is that every fifteen seconds or so, Shelly (I guess) reports the state like this, over and over again:
14:15:20.423 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Curtains' changed from 0.0 to 100.0
14:15:22.865 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Curtains' changed from 100.0 to 0.0
14:15:35.438 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Curtains' changed from 0.0 to 100.0
14:15:38.152 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Curtains' changed from 100.0 to 0.0
14:16:01.225 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Curtains' changed from 0.0 to 100.0
14:16:02.689 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Curtains' changed from 100.0 to 0.0
....
So everything is working fine except the logging. Buttons respond correctly, window and curtains open/close correctly and show up in the openHAB interface and can be controlled from there.
The text was updated successfully, but these errors were encountered: