My HASS server is 192.168.1.15 and the wifi subnet net 192.168.2.0/24 so the broadcast address is 192.168.2.255
Unfortunately I don’t get any new entities, so it appears it is not seeing the lifx. I do however get the below in the log:
16-09-24 21:27:42 homeassistant.loader: Loaded light.lifx from homeassistant.components.light.lifx
HI Brian,
Definitely using the correct broadcast address ( I am an network engineer so would be worried if I got that wrong : ) )
Where my setup is different, is I have my HASS server on a different L3 segment than my lifx bulbs. Unfortunately it is going to be difficult for me to change this out to have the LIFX and server on the same subnet for testing.
Just to confirm, once we add the new platform, does the new entity get created, eg light.lifx1 ?
The lifx are definately working via the lifx app, as I can control them via iphone, but HASS just doesnt see/create the entity.
Ran some further testing, essentially the issue is not within HASS, but within my firewall. They dont support directed broadcasts, I could see HASS sending out the broadcasts, but my firewall was dropping them. In testing, pointed HASS directly to a single bulb and the entitity turned up.
Looks like I may need to redesign my home network to put HASS on the same broadcast domain as my LIFX bulbs
Thanks for this . . . the component page instructions are actually very vague on details of when/if the other configuration variables should be used, and offer no examples of the other two configuration variables either. I couldn’t get my LIFX bulbs to be recognized until I added teh broadcast configuration using the value you posted . . .