Closed louisefindlay23 closed 5 years ago
Are you using the host
network driver for Docker?
When did this work? 0.83 seems like a typo ...
Yes, I'm using host. It must have been 0.80.3.
Try doing
lifx: lights:
That’s what mine has and it discovers them since the 81.1 update, I’ve had some issues too and had to add a delay to HomeKit starting so all the bulbs show up properly in the HomeKit side of things too
Same issue here, after upgrading from 0.80.3 and still present with 0.81.2.
Tried with/without advanced configuration => same issue.
Using docker with network=host as well.
No new ports implemented or something ? (for iptables)
@miniwalks Tried that but no change. I don't use homekit within Home Assistant and instead run my own Homebridge docker container. Is there any sort of cache for components as I had to start a new docker container recently which was when it stopped working.
LIFX will now use random UDP ports, not just 56700.
I have same issue but if I make sure the bulb is turned on during a HA restart it is detected every time. (I use docker and have set to host)
LIFX does work with Docker so I am leaning towards some funny network setup that blocks the traffic :-/
After some network captures, I agree with @amelchio the request does use a random UDP port, which is then used by the lifx lights for the response.
For test purposes, I authorized any UDP packet in, and after trying again from the integration menu they appeared and are working fine now. So it is a firewalling issue.
After re-enabling the udp filtering, lights seems to be still working from homeassistant, but they don't survive a reboot of homeassistant. Re-authorizing all UDP packets make them re-appear in seconds.
I've to search for a way to tag those packets to automatically authorize them when the response comes.
The LIFX integration will use random UDP source ports but LIFX bulbs always use port 56700 (mine do, at least).
So if you really want a firewall, you should allow outgoing packets (i.e. from HA to LIFX) to UDP port 56700, as well as replies to those packets. Home Assistant always initiates the communication so connection tracking should work.
I've tried leaving one of my lights on while restarting but it doesn't work. I just use the normal docker with host, no extra firewalls.
I ended up removing docker and importing my configuration files to the python version and it works.
Home Assistant release with the issue:
0.81.1
Last working Home Assistant release (if known):
Before 0.83 something
Operating environment (Hass.io/Docker/Windows/etc.):
Docker
Component/platform:
https://www.home-assistant.io/components/lifx/
Description of problem:
Using the Lifx integration says no devices on the network. I tried adding the lifx: in the configuration yaml and adding the broadcast and server but nothing shows up
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):