This occurs totally randomly - with some outstanding luck you might even go a week without any issues, commanding the LifX bulbs via HomePod. Nothing has fixed this, or aided the issue even just a bit.
I’ve gone through every LifX firmware to the latest over the past year.
They never fail, every command goes through the LifX bulbs. Same goes with my iMac (which utilises 5G WiFi) - and my iPhone. 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. There’s so many things that point to the fact and confirm that the issue is ONLY between the communication of HomePod + LifX bulbs. Tried for example to disable all the “smart features” etc. 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). I use Amplifi HD router without any additional mesh points. I’ve already tried just about everything one could imagine (IT system specialist as my profession too). I have other smart devices, like Eve Energy smart plugs, and they work 100% fine all the time, without any issues. 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. Ditto with 6, choose 4, 5, 7 or 8 and if channel 1 seems decent use 2 or 3. I can explain why another time, but basically if you find channel 11 is pretty quiet then choose 10 or even 9. If not, then choose the one with the highest loss and offset it by 1. 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. The closer to 0 you are, the better (0 being no loss of signal, which is purely a reference point). Signal strength is typically expressed in =<0dBm. 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.
#How to disable ap isolation on technicolor router Patch#
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.Į.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.Īlternatively, some of your lights might just have patch connectivity. I think there’s a bit of misunderstanding when it comes to bonjour proxying or discovery in general.īonjour 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. 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. Grab Discovery.app for macOS or iOS ( ) and you’ll be able to see if things are working from the perspective of your HomePod.īasically your client (iOS/Mac/whatever) needs to be able to discover and connect to your HomeKit Hub ( _homekit.tcp. I know this is a mega delayed reply, how did you go resolving this?
0 kommentar(er)
