Hey all — hoping someone else has run into this. C-8 Pro, platform 2.5.1.183. Hue bulbs paired directly to HE, no Hue Hub.
After my Hue bulbs updated to firmware 1.163.1, some of them (models LCA007 and LCB002) started throwing device announce errors. Reset and re-paired them, and pairing itself goes smoothly — but shortly after, they drop off the network.
A few other Hue models on the same hub and firmware batch (LCD007, LTO004) are totally unaffected, and nothing else changed — same driver, same spots they'd been sitting stable in for ages. So it really feels tied to these two models' firmware specifically.
Anyone seen this or have tips for stabilizing them?
Update — I found a clearer symptom that might help diagnose this.
While the Hue bulbs are briefly connected to the HE (before they drop), they do respond to commands. I changed color temp from 4,000K to 2,700K and it took effect immediately. But after about 10-15 seconds, it reverted back to 4,000K on its own — no command from me — and then a few moments after that, the bulb fell off the network.
That sequence (command works → silently reverts to a prior state → disconnects) makes me think this isn't really a Zigbee routing/signal issue at all — it looks more like the bulb itself is crashing and rebooting internally, which would explain both the state revert (reloading a cached/default state) and the network drop (a real device restart, not just a lost connection).
Hue support has been no help at all. If anyone's seen a firmware-crash pattern like this before, or has thoughts on how to confirm it (logs to check, etc.) — or any other help to offer — I'd appreciate it.
Update #2 — I think I've narrowed it down a little further. I tested brightness-only changes, color changes, and simple on/off commands separately (not just color temp). I got the same result every time: the bulb accepts the command, holds the new state for about 10-15 seconds, then reverts back on its own, and disconnects from the network shortly after. So it's not tied to any specific command type — any state change triggers the same fixed-interval revert-then-drop cycle.
Good-day @S_Chango, I've been struggling in the previous week or so with my Philips Hue bulb (hdwr LCA005) on a C-8 hub. The symptom has been multiple disconnections and it's ultimately no longer controllable with Hubitat app. Hubitat software upgrades may be implicated here since it's gotten progressively worse, but the final blow was irreversibly updating the bulb with the latest Philips hue firmware (ver 1.163.1). Since then I've been totally unable to communicate with the bulb regardless of reboots and rolling back to earlier Hubitat versions.
My plan is to acquire a Hue bridge, which is really the only legit way to control Hue bulbs. Hopefully implementing Matter rather than Zigbee will function. IMHO, it's been a gift that Hubitat has controlled Hue bulbs directly for years until now.
Good luck in making Hue bulbs work directly with Hubitat. I've thrown in the towel.
I’m sorry to hear you’ve had so much difficulty. My system has been rock solid for years with Hue bulbs and Inovelli Blue switches bound to my HE and directly. And those that haven’t received this latest Hue firmware update still are. No Hue hub at any point, and no intention to ever get one, because for me it’s paramount that the bulbs be directly bound to the switches. The problem I’m experiencing seems to be tied to this specific latest firmware update and those specific bulbs.
Next time they drop try joining them in strict Zigbee 3.0 mode. Short of that I'll need the exact bulb part number and the firmware that it's running, then I might be able to figure out what's going on with wire shark
Thanks Mike. The bulbs drop 30-60 seconds after joining but then reenter pairing mode, as after a firmware crash. I’ll try joining the bulbs in strict Zigbee 3.0 mode as soon as I’m back near the HE and will report back.
And I would appreciate it if you could try to figure out what’s going on with wire shark. The two affected types of bulb have model numbers 9290024687 and 9290034793. And the Hue firmware that they’re running — and which precipitated the problems — is version 1.163.1.
Unfortunately, Mike, it does not appear that joining the bulbs in Zigbee 3.0 mode is making a difference. Anything you could do to try to suss out the situation would be very appreciated.
Can you go to the driver's device Info tab for one of these devices and paste the value of Firmware MT thats located in the Device Data section at the bottom as well as the model value?