-
-
Notifications
You must be signed in to change notification settings - Fork 91
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
Hue Dimmer Switch gets pressed without human interaction #1101
Comments
Why? Did the Hue bridge crash and reboot?
Most likely because the Hue bridge reports a new value for You might also want to double-check the clock on the Hue bridge vs the server running Homebridge.
That message doesn’t come from Homebridge Hue. It could indicate an issue with your network / DNS server. |
Thanks for your super fast response!
The hue bridge did a firmware update at that time, therefore I assumed that it rebooted because of that.
Will do the clock check and and debug mode tomorrow. I hope I can emulate the behavior by just unplugging the Hue bridge for a minute or two.
Okay, thanks for clarifying. Will deal with that later. |
Clock of homebridge server and Hue bridge match. Unfortunately a restart (pull power plug) of the Hue bridge doesn't lead to the "ghost" pressing. I tired it two times. Leaving the Hue bridge powerless for at least a minute. The behavior in the logs is the same (get sensors fails, EHOSTUNREACH and then ECONNREFUSED before get sensors works again) and then it cycles through a lot of my devices, like this: But but it's not "cycling" through the dimmer switches (and magically presses each one of them), like at the two occasions I experienced it before. I checked again and confirmed that the Hue bridge did a firmware update last night at the time. So my assumption is, that I can only replicate, or observe this behavior again, when the Hue bridge will do the next firmware update. Is it safe and reasonable to leave the homebridge debug mode on until that will happen again? Even if the next firmware update of the Hue bridge will be in weeks or months? Then I would just wait and see what is happening in the logs then. |
Any updates? I think my bridge updated to 1952043030 (API version 1.52.0) this week. |
Thanks for the reminder, I missed that. The behavior occurred after the update! Please find attached the log for two dimmer switches that gets magically pressed a couple of minutes after the hue bridge updated (Bridge came back online at [6/18/2022, 1:53:16 PM]) If I understand the logs correctly homebridge-hue recalls an actual button press (sensor buttonevent) of the past?! (For "Saugbert Schalter" 2022-06-16 and for "Alarmanlage Schalter" 2022-03-29) This dimmer switch is called "Saugbert Schalter": Log Messages
And this dimmer switch is called "Alarmanlage Schalter": Log Messages
|
The Hue bridge sends on the event stream an event, which Homebridge Hue cannot distinguish from a real button press. What does the log look like, after the first successful GET /sensors since the reboot? I would suspect that reports Do you also see state change events for other sensor types? Note that there's over 8.5 minutes between the two button events. I really don't understand what triggers the Hue bridge to send these events. Normally the Hue bridge configures the Hue dimmer switch to wakeup every 5 minutes to report its battery state. Did the bridge reboot in between these events? This looks to be a weird bug in the Hue bridge. I'm not sure I could even create a viable workaround (like trying to recognise a firmware update and ignoring the first state event after that, or simply ignoring any x002 or x003 event without a previous x000 or x001). They would probably do more harm than good. I will definitely not try before Homebridge Hue2. |
These are all buttonevents in the log file of homebridge (which unfortunately only reaches back a couple of hours): Log Messages
I attached the whole log file. I'm not sure I can completely follow you on your next thoughts. (Where can I read out the API? Via the HUE hub ip address?)
|
|
I tried it for two of the affected dimmer switches. Since state returns "null" and "none", I just tried with get /sensors/
|
Weird. I take it, the state is populated after you press a button for real? I'll try and pair an old Hue dimmer to my Hue bridge, but i'll probably only get to it, when I'll start working on Homebridge Hue2. |
Issue
Hey,
I encountered a strange behavior in my setup for the second time now. After homebridge-hue lost connection to the Hue bridge (v2, latest update), in the case of today, because of a scheduled Hue bridge update, all of my dimmer switches get pressed once "magically" over the next minutes after homebridge-hue reconnected to the Hue bridge. When this first appeared a couple of weeks ago it freaked me out a bit, because I thought somebody hacked my system. I changed all passwords and checked if any system was breached. I found nothing. I disconnected the Hue bridge from the hue.com online service, so that also all hue components are only online via Homekit. It didn't help. The problem reoccurred tonight.
To be a bit more precise what you can also see in the logs:
I would appreciate any feedback on what can cause that issue. If my setup is wrong, or if it's a bug.
And thanks again for you amazing work!
Best regards,
Adrian
Log Messages
Debug Files
The text was updated successfully, but these errors were encountered: