I cannot connect to my Hue lights anymore. Red exclamation mark on all my lights. I’m connected through Hue Bridge. Hue app version 4.0.4
I’ve restarted my Hue app, restarted Homey.
Removed a light. Cannot add this light again because there are no new lights.
Through Philips Hue app (not Homey), everything is working.
What can I do?
Edit: completely removed the Hue app. Restarted Homey. Re-installed the app: I cannot add any devices, no devices found.
Yes, both ip-addresses for the Homey and Hue Bridge are fixed by my dhcp-server.
I got it working again by removing the Hue app, powering off for 10 minutes (Homey and Hue Bridge). Then I could re-add my lights. Off source with different id’s so I need to rebuild the flows…
Yesterday evening all (5x) the Hue lights were unavailable again. I’ve tried resetting (power off) the Hue Bridge for a few minutes but that didn’t help: Available: No (Searching for Hue Bridge…). Restarted the Homey: didn’t fix it either.
Could be that this started after installing the latest version of the app v4.0.4 on 17 apr.
I’m having issues. As you mentioned it now, it could have been started from the latest version v4.0.4 of the app. I have made a support ticket as well.
That’s what I did. They are working on it. Well, I guess not during the holidays.
For now I removed the app, removed my Hue lights from the Hue Bridge. Installed this app: Hue ZigBee
After some work, everything running and working. Hopefully this app is stable. I’ll see the coming days.
I think this issue is revolved for me: Athom support saw in my logs that I was blocking www.meethue.com. Which I did with Pi-Hole (adblocker). Apparently the app needs to connect to meethue.com once in a while.
Can’t speak for others but you may check your dns or internet connection.
Haha, you are right. If it is blocked, it went nuts, doing checks every 30 seconds or so. I didn’t measure it when it was not blocked. A lot according to your data.
Yesterday i had the same, later i realised the app had been updated.
This time i did nothing and it fixed itself after a few hours.
I did send an email to support.