Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Occasional wrong states on pico button press
See original GitHub issueNot sure how to best troubleshoot this.
Seemingly randomly some of my pico remotes will stop working correctly. These remotes aren’t paired to an actual caseta dimmer, just to the hub, and I use an automation to make them control non-caseta lights.
I put some logging on it and found out that when this happens, the numeric state on the sensor entity is wrong. Everything is +8 - so when no buttons are pressed, the state is 8 instead of 0, on is 9 instead of 1, favorite is 10 instead of 2, up is 16 instead of 8, etc.
Usually a restart of Home Assistant will fix the issue, or sometimes it will fix itself after a couple hours.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I have attempted to simplify the state updates again for the sensor. Releasing the button will always set the state back to zero and the states are no longer combined on update.
This may not fix the problem if the component never receives the message for the button release, but it will at least simplify the logic.
Just had it happen again this evening, but this time everything is +4 instead of +8, which is different from all the other times this has happened in the past that I’m aware of. Only 1 pico though, the others all seem to be working fine.