19:36:37.218 - The LIFX discovery service will use '480ab050' as source identifier 19:36:26.973 - Updating network information 19:36:11.963 - Updating network information I have tried the manual approach - using the divice id (mac address) as printed on the globe, and the statically assigned IP address. 19:27:06.617 - Updating network information 19:26:51.600 - Updating network information 19:26:37.141 - Discovery : Binding the broadcast channel on port 56700 I have activated the extra logging, and I can see openhab broadcasting the network scan. I have quite a few of the standard LIFx colour bulbs, and they have given me no trouble as far as Openhab2 is concerned (they don’t like dodgy wifi, but that was a separate problem ) The bulbs are showing up in the LIFx app, and I can ping them individually.

Just bumping this conversation up, as I am seeing the same issue as LIFx Mini colour, e27 model in Australia.

log:set info .lifxĬontinuing the discussion from Bindings for newly released LIFX Mini?:.

When you’re done you press CTRL+C and reset the logging of the LIFX Binding back to info via: Then you can monitor the logging via the log files or: You can enable debug logging of the LIFX Binding via: If you’re still having problems you could enable debug logging for the LIFX Binding to see what it is up to. So in 2.1.0 it will not automatically add discovered Minis to the Inbox. Without some updated information openHAB does not know what the capabilities of the Minis are (color, white, infrared, multiple zones). The only difference is that they return different Product IDs. The Minis should talk exactly the same protocol as the other lights.

Oh well i will continue looking into the machinations of OpenHAB to figure out how to add them I wonder what exactly has changed between the lifx mini and the others to change the bindings. The bulbs are all showing up as being offline.

Download lifx mini