With the introduction of built-in LIFX drivers in Hubitat release 2.3.0 - some questions have come to mind, which I felt were worthy of a separate thread, rather than piling on to the existing community app/driver thread
I don't immediately see any visible difference between the Color and Strip drivers - is there any at this point? If not, I assume further Strip enhancements are in the pipeline, for multizone support?
Maybe I'm missing something - haven't taken the leap to install the built-in app and discover my bulbs/strips using the built-in drivers. But I added a manual/virtual device, to poke around the exposed capabilities/commands... And I don't see anything in the device page when using the LIFX Strip driver that is multizone-specific... E.g. it looks just like a basic Color bulb
The biggest difference is the multi-zone color support.. It will create a component child for each color zone that the strip supports..
I should note the original z-tv strip hasnāt been tested and I donāt think will work properly for zones as this driver was written for extended color zones..
Just not finished yet.. More to come.. I also posted a sample driver in the community.
If you send any set commands (color, hue, CT, etc) from the parent device it changes the whole strip that color.. If you want to control individual color zones itās through the child devices.. I went this route to make it easy to use scenes.
Yep - I took a similar approach when adding individual zone control in Rob's drivers - we also had a (bulky) command on the parent device where you could set multiple zones in one command (but scenes makes sense for this use case)
I also have 2 x Lifx Mini devices that are not discovered. Is there any way to debug? My other devices all detected fine including one other Lifx Mini (which is detected as Lifx CT).
The 2 missing devices work fine using the prior Hubitat Lifx integration and I also have them in Home Assistant and in the Lifx app.
Try rebooting the bulbs.. Torn on/off the power .. Wait a few seconds then click refresh on the discovery.. I have seen a bulb once and a while stop listening for discovery packets and this fixed them..
I gave that a go but no dice. The two missing devices are actually different models to all the others, shows up as "LIFX Mini C" in the LIFX app whereas the mini that does connect fine to the integration shows up as "LIFX Mini DD". The Mini C is the color mini (2 of these don't seem to detect), the Mini DD is the white only (this one detects fine).
Just starting with my test rig that has 3 color downlights and a switch. Discovered lights OK, but for the switch I get "Desk Switch (No driver installed for null). I assume I am missing something in my setup? The switch is configured with the first two buttons each controlling a downlight via the web.
This is a fresh install with the latest release.
Just about to buy some bulbsā¦. Quick question is there support for the āgroupsā and āscenesā that you set up in the LIFX app ? Iām assuming perhaps these are commands / memberships that the bulbs themselves learn to get an instantaneous response, rather than individually controlling each bulb ?
As others have documented, the "clean" version of their bulb works great with the (built-in) LIFX Color driver. Is there a mechanism to turn on the clean mode via a color temperature selection, or is that ultimately something awaiting possible future development or a community driver? [That said, is the HEV mode even available via their LAN protocol?]
