LIFX is quite a complex system to integrate into Hubitat so it's not as simple as just installing a single driver
There are several components
- The LIFX Master App - this is where you discover devices
- The LIFX Discovery device - this does the grunt work of scanning your network for LIFX devices
- Various LIFX device handlers
- LIFX Color
- LIFXPlus Color (does not currently include support for Infrared/Night Vision)
- LIFX White
- LIFX Day and Dusk
- LIFX Tile - dummy driver, only supports on/off
- LIFX Multizone - for Beam and Strip, currently only supports on/off
On the Apps Code page, press the New App button
Paste the code for LIFXMasterApp.groovy and press the Save button (or type Ctrl-S)
On the Devices Code page, press the New Driver button
Paste the code for LIFXDiscovery.groovy and save
Repeat this process for each of the device handlers you want to install. It's probably best to add all of them
On the Apps page press the Add User App button then click on LIFX Master in the list of available apps.
####IMPORTANT: don't forget to press the Done button to make sure the the LIFX Master app sticks around.
First of all, make sure that all your LIFX devices are powered on, obviously discovery won't find any device that doesn't have power.
Again IMPORTANT if you didn't press the Done button when you created the LIFX Master app then do it now.
Open the LIFX Master app and press the Discover devices button. You may notice the LIFX Discovery device in your list of devices, but this should disappear at the end of the scan.
It's recommended that when updating the LIFX code that you delete the app instance. However, this will delete all your existing LIFX devices. As an alternative the first action you should take is to click the Clear caches button.
The LIFX Lan Protocol uses UDP messages, it seems that sometimes these can be missed or lost, so the discovery process makes 5 passes over your local network to try to mitigate this. So far this seems good enough on my network.
Further to this, when a command is sent to change a LIFX setting it requests an acknowledgement and the sequence number is tracked with the LAN Protocol packet. When a subsequent command or query is sent it checks to see whether the acknowledgement was received. If it wasn't received the packet is sent one more time. The reason for this is that UDP messages are not guaranteed to arrive, so it's pretty much a small safety net. You can expect that this will happen at least when the device is next polled (under a minute).
If you find that some devices aren't discovered
- try the Discover new only new devices button
- make sure that the missing devices still have power - someone may have turned off a switch :)
- try altering some of the options as described below.
With recent improvements I've found that the default settings should be more than enough to discover all your devices in two passes, but your mileage may vary.
My first recommendation would be increasing the value of Time between commands (milliseconds).
Try increasing it by 10 at a time.
You can also increase Maximum number of passes to give discovery a better chance of reaching all the devices in your network.
I've found that all my devices are found in the first pass at least 95% of the time.
Let me know if you see any errors in the log, and I'll do my best to fix the issue as soon as possible
I have assumed that you will be running a Class C network (also known as /24), ie that your subnet mask is 255.255.255.0, which limits you to a total of 254 IP addresses.
Note that this uses the IP address as the device network id - if you change the id you may break things. If you don't assign fixed IP addresses to your LIFX devices then you may be able to use this to avoid having to scan for new devices.