Has anyone else noticed any issues after the February 5th release of new firmware for the v2 Phillips Hue bridge? Mine just auto-updated on the 12th, and now SmartThings can no longer controls any of my bulbs.
That said, the integration isn’t completely broken—SmartThings can still see status updates and correctly reports on the bulbs’ status (e.g. on/off, light level, color, etc.), but it cannot control them any longer.
What’s particularly bizarre is that other Hue integrations are working—e.g. Amazon Alexa can still control the bulbs. It’s just SmartThings that can’t. I’ve tried rebooting both my SmartThings hub and the Phillips Hue hub, but to no avail. Not sure how/where to troubleshoot from here. Didn’t see anything in the Live Logging that seemed relevant.
I’ve had to rotate every now and again as every few months random bulbs need to be told twice to turn off or on. I live a very densely populated urban area, so once in a while I take a look at a diagnostic analysis of the 2.4 Ghz spectrum and try to find the least noisiest channel.
Phillips has been doing a lot of tinkering with their LAN integration for the last few months trying to get it to work better with Mesh Wi-Fi routers.
My guess is superLAN connect is somehow getting confused by some of these changes until you reboot the router. But I’m just guessing. There are reports on some other home automation boards of some similar issues also corrected by router reboots.