homebridge-hue: Double Trigger when using Hue Wall Switch
Have seen a strange behaviour, that in case I press one of the Buttons which are connected to a hue Wall Switch, i see twice the status change in the logs which toggle also every automation configured in homekit.
Homebridge.log
[04/03/2023, 23:35:44] [Hue-Bridge] SWI - Spots Rocker 2: homekit button single press
[04/03/2023, 23:35:46] [Hue-Bridge] SWI - Spots Rocker 1: homekit button single press
[04/03/2023, 23:35:46] [Hue-Bridge] SWI - Spots Rocker 1: homekit button single press
[04/03/2023, 23:35:49] [Hue-Bridge] SWI - Spots Rocker 1: homekit button single press
[04/03/2023, 23:35:53] [Hue-Bridge] SWI - Spots Rocker 2: homekit button single press
[04/03/2023, 23:35:56] [Hue-Bridge] SWI - Spots Rocker 1: homekit button single press
[04/03/2023, 23:35:56] [Hue-Bridge] SWI - Spots Rocker 1: homekit button single press
As you can see in the logs, the switch looks like it has been pushed twice, even though I did it just one time. This is causing a flapping in my automations with Special conditions.
The question is now, why does the clock gets reported two times? I tested all of this independent in the view app without any homebridge or third party integration, and all works fine.
There is probably a race condition happening, as there are also times when it works.
Any hints or anything I can help with in the sense of lots of debugging? Thanks a lot.
Kind regards Maik Brauer
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 19 (9 by maintainers)
Commits related to this issue
- Update HueSensor.js Issue #1148. — committed to ebaauw/homebridge-hue by ebaauw a year ago
- Update HueSensor.js Issue #1148. — committed to ebaauw/homebridge-hue by ebaauw a year ago
- Update HueSensor.js Issue #1148, take 2. — committed to ebaauw/homebridge-hue by ebaauw a year ago
- Update HueBridge.js Issue #1148, take 3. — committed to ebaauw/homebridge-hue by ebaauw a year ago
In v0.13.57.
Not sure you’ve yet recreated the conditions where a double press would occur. There should be a debug message that the button press was suppressed because the event stream is active.
If this workaround works, I’ll include it in the next published release,