Has the LifX integration broken in Platform update 2.5?
I noticed the day after updating to 2.5 (C8-Pro) that my automations weren't working, and when I go to the devices the status is at the last known state before the update and will not respond.
Not sure how to to troubleshoot this but interested to here if others have the same problem (or not!)
Thanks.
Can you turn on/off the lifx bulb from the device page?
Nope. If I turn on debug logging for either of the two bulbs, I get unhandled command error.
@bcopeland Could this be related to the issue I discussed with you on that one lifx bulb?
FWIW, all my LIFX bulbs have no issue. So whatever has happened, it isn't affecting all LIFX installations.
Actually, on reviewing it is a single bulb. 1 is working, 1 is not. The bulb that suddenly does not work in Hubitat does work in the LifX app, and is definitely still connected to my network (static IP also).
Make sure there's nothing funky going on with your LAN. Reboot your router and then your bulb.
LIFX discovery and local control requires mDNS to be working on your LAN. Routers are known to occasionally stop forwarding multicast between wired and wireless segments of the LAN. In contrast to local control, cloud control (via the LIFX app) doesn't require mDNS/multicast to be working. Strictly speaking, multicast is only required for device discovery; after discovery control is done using singlecast UDP. However, device discovery occurs after every reboot - and a platform update involves a reboot.
I have approximately a dozen LIFX bulbs controlled locally by Hubitat; I have encountered router mDNS issues in the past, although not after I switched to a Unifi network.
Thanks - As far as I can see, nothing funny going on with the LAN and have tried all obvious (and less obvious) with the network. As per my last comment (originally I thought both were down), one bulb works with hubitat and one doesn't - failure of mDNS/Multicast would affect both, would it not? Also my Homekit devices work with the Hubitat Homekit integration. Really odd it affects one bulb only (which works via the app).
The integration has been running well with no issues for years with, genuinely, not a single issue ever - The only change is the upgrade to 2.5.
It sounds like rlithgow1 may have seen a 'funny' with a bulb also. At a quieter time when I won't get lynched by the family I'll try a downgrade and see if that resolves it. Otherwise, open to any ideas...
I'm having the same issue as OP... All but 1 bulb works in hubitat but that same bulb works in the Lifx app. I removed it from hubitat and it found it and re adds it but still won't work in Hubitat. I notified @bcopeland about it.
Possibly a different firmware on the 1 bulb? Although if I know you, they are all the same firmware, and you have a spreadsheet to prove it.
all the same
Not much of a value add here now, but I have about 25 LIFX bulbs. All seem to be responding as before I upgraded.
No. Not necessarily. Depends on when the each bulb was last discovered.
Hopefully @bcopeland can correct this if needed, but AFAIK, the LIFX integration has not been changed in a very long time.
The only recent change was tracking the ACK packets to re-transmit lost commands.. That was in the last release..
I'm still having that same issue. Lifx app works fine, even after removal Hubitat finds it re add it but cannot control it or get status from it. Feel free to dig into my logs...
Issued ON command from device page
.. Ok Not what I was thinking the problem was..
Going to pull logs..
I'm not seeing anything in the logs.. Will probably need to put something in..
PM me if you need me to do anything...
Have a second bulb I just noticed doing the same thing. Controllable by the lifx app but not Hubitat.
Download the Hubitat app
