LIFX Developer Zone

Is the problem HomeKit, or LIFX

Is it just me or does anyone else have issues with HomeKit and LIFX. My HomePod always throws back “there was a problem with one of your devices” etc… and doesn’t turn on a light and then you ask again one or two more times and it works…
Any ideas how I can fix this, what the problem is? I’m on my 3rd router and the issues are the same… it’s so frustrating…
also, I don’t have any issues with my sensibo or August lock. It’s only LIFX lights …

1 Like

Which router are you using? I’m using Ubiquiti Unifi gear and my LIFX bulbs are fairly rock solid (I have about 40 of them too). There are also some HomeKit stability improvements in the new 3.50-BULB beta firmware for some of the bulbs (in particular, the Minis which have been historically flaky).

Are you using a single, or multiple, SSIDs and/or VLANs?

I have 3 SSIDs: One for my normal devices (laptops, phones, etc) which is dual-band and two more. The IOT and LIFX SSIDs are restricted to 2.4Ghz only. I don’t use VLANs (tried it, but mDNS Reflection is crappy) so they’re all on a single /24 network.

I know this is a mega delayed reply, how did you go resolving this?

Grab Discovery.app for macOS or iOS (http://www.tildesoft.com/) and you’ll be able to see if things are working from the perspective of your HomePod.

Basically your client (iOS/Mac/whatever) needs to be able to discover and connect to your HomeKit Hub (_homekit.tcp. - preference is Apple TV, HomePod, iPad according to the Apple docs) and your HomeKit Hub needs to be able to not just see the mDNS service (_hap._tcp.) but connect to UDP port 56700.

I think there’s a bit of misunderstanding when it comes to bonjour proxying or discovery in general.

Bonjour unto itself won’t provide connectivity to the service that’s being multicast via mDNS (or broadcast if your access point converts multicast to broadcast / you don’t have an active IGMP querier), it just lets the client know what services are available and IP/port they’re available on.

If you’re truly on the same broadcast domain then the only device that could potentially prevent access to your lights is your access point.

E.g., If you’ve cient/VLAN/access point isolation turned on which, unless you’re experienced with the kit you’re using, is likely to break things.

Alternatively, some of your lights might just have patch connectivity.

Your LIFX SSID should have the following characteristics for reliability sake (this gets more complicated as you add wireless extenders or other access points, especially if they’re different brands and pretty much unaware of each other):

  • 20MHz channel width
  • Limit the available channels from 1 to 11 (depending on device, you’ll have 12, 13 and 14 - turn that range off or expect issues).
  • Set your TX power to maximum.
  • Use a wireless survey/stumbling tool to determine the channel that’s in use the least. Do this from the vantage point of where you’ve installed your lights; your client might not hear a noisy neighbour that one of your lights can.

Signal strength is typically expressed in =<0dBm. The closer to 0 you are, the better (0 being no loss of signal, which is purely a reference point).

What you’ll find is probably a neighboring AP on channel 1, 6 or 11 that’s around the -80 to -90dBm mark, or if you’re really lucky, you’ll have clear air in 1, 6 or 11.

If clear, then choose that one. If not, then choose the one with the highest loss and offset it by 1.

I can explain why another time, but basically if you find channel 11 is pretty quiet then choose 10 or even 9. Ditto with 6 , choose 4, 5, 7 or 8 and if channel 1 seems decent use 2 or 3.

1 Like

I’d be interested if anyone else has worked out what the deal is with this issue.

I have nothing but trouble with HomeKit / LIFX control but ONLY when using the HomePod. I can ask Siri to control the lights from my Apple Watch, iPhone or iPad without issue. It’s only the HomePod that fails.

They are all on the same network using the same router.

Suggestions? Comments?

Cheers

It’s the HomePod. It used to be rock solid in iOS12. It’s getting a lot better with the latest iOS 13.3 update for HomePod but still not great.

I’ve had this same issue since I bought my HomePod in 2018 (LifX bulb set was bought few months before that), so that covers all the iOS versions in between, from the one it was shipped with to latest available. The issue is ONLY with LifX bulbs. I have other smart devices, like Eve Energy smart plugs, and they work 100% fine all the time, without any issues.

I’ve already tried just about everything one could imagine (IT system specialist as my profession too). I use Amplifi HD router without any additional mesh points. I’ve tried troubleshooting that too, even joined the beta-releases at one point - but it just turned out that it’s definitely not the router either (or the relatively simple WiFi-setup). Tried for example to disable all the “smart features” etc. from Amplifi config, etc. There’s so many things that point to the fact and confirm that the issue is ONLY between the communication of HomePod + LifX bulbs. If I ask Siri on my Apple Watch (right after I got the error via HomePod), which uses 2.4G WiFi as does LifX bulbs, it works 100%, always without issues. Same goes with my iMac (which utilises 5G WiFi) - and my iPhone. They never fail, every command goes through the LifX bulbs.

I’ve gone through every LifX firmware to the latest over the past year. Nothing has fixed this, or aided the issue even just a bit. This occurs totally randomly - with some outstanding luck you might even go a week without any issues, commanding the LifX bulbs via HomePod. But eventually, and sometimes multiple times per day, HomePod can not reach LifX bulbs or their status.

There’s absolutely 0 problems or issues of any other kind in my network or network setup. And as said, HomePod NEVER fails to command the other HomeKit devices I have.

I wasn’t surprised to find a thread about this, and it doesn’t surprise me that people are immediately going with the “oh but it’s your HomePod what causes this”. No, it’s not the HomePod - definitely at least alone. HomePod works just fine with all other smart devices and HomeKit, but LifX bulbs don’t seem to be playing nice with it, or being fully compatible in a HomePod+HomeKit setup.

I’d definitely return the 4 bulb set if offered a chance for a refund. Before all the tens of hours of troubleshooting over a year, cursing when trying to send a simple task and set the lights just to repeatedly getting this error… I (up to some point) thought that the concept of smart home devices isn’t apparently yet ripe for everyday use. Now I’ve come to realise that it’s just “some smart devices” - like LifX bulbs.

So since 2018: all iOS versions, all router FW-versions (+multiple factory resets and all various configurations), multiple HomePod factory resets (just trying to solve this), all LifX FW-versions with multiple resets to bulbs just trying to solve this - the conflict between HomePod and LifX bulbs (everything else works 100% fine in the network, every other HomeKit device can connect to LifX bulbs from both 2.4G and 5G WiFi), I think it’s pretty sure by now that either it’s the HW/chipset revision on these bulbs that’s terminally bugged/non-compatible, or the firmwares - it’s most likely never going to be fixed.

1 Like

I’m surprised it’s limited to your LIFX bulbs, but it’s absolutely a HomePod thing. If you check the HomePod/Siri subreddit, this is the #1 complaint about HomeKit: HomePods are just dumb.

Edited to say that I can get HomePod to act stupid like this without even needing LIFX. Just map them via Homebridge and HomePod still goes “Some lights didn’t respond”, even when they did.

You also answered your own question by saying that all other iOS devices work just fine with LIFX via HomeKit, which means the LIFX side is not the problem, it’s the HomePod side.

I love my HomePods (and they sound great), but it may be Stockholm Syndrome. :slight_smile: