LIFX Beta looking for (courageous) testers

It works perfectly! I was trying to do this exact same thing earlier but it did not work, now it does!!!

Glad it works. If you want an instant reponse, just pass transition: 0 via a light.turn_on service call (or similar).

Thanks so much for the help so far, by any chance have you had issues trying to do scene transitions with LIFXZ strips? It seems like they like to frequently disconnect and then forget the change they were issues.

LIFX Z strips have only a tiny amount of memory, so this is as expected. They are supposed to power on in the same state they were in when last soft powered off but they do not have power loss recovery, i.e. if they lose power, they will turn on to the last state they were when they last received a soft power off request.

One thing I’ve never tried that could work is to issue a power on request with the transition, i.e. add power: true to the lifx.set_state service call that changes/sets the state on the Z strip, even if the strip is already on. That may cause the Z strip to remember this state and return to it if the power cycles.

If not, you’ll could store the state in a helper and then trigger an automation to fire when the strip transitions from “unavailable” to restore that state to the strip. Essentially using Home Assistant to do power loss recovery for you. Though, obviousliy it’ll be somewhat delayed.

Instead of one color though I am trying to do a transition from one color to the next one over at least 1000 seconds of time

The strip is not going to continue a transition if it power cycles and if it goes unavailable, it may actually be rebooting. My advice is to break down your transition into multiple 60 second transitions so the strip will resume transitioning at most 59 seconds after becoming available again.

This is how I recreated the LIFX Cloud dependent Dawn to Dusk functionality locallyi using Photons Interactor initially and these days just natively with Home Assistant. Essentially, I send a lifx.set_state every 5 minutes to transition to the next kelvin value and just subtract 300 seconds from the transition time.

Hopefully that very short explanation makes sense. It’s all about sending more transitions more often that all end at the same time so that if anything interrupts the transition, it’ll get a new one within a minute or two, instead of 15+.

Thanks, do you have that code to break it up with home assistant by any chance?

It’s just an automation that uses a helper to store the remaining transition time. Just trigger it every 5 minutes and reduce the timer by 300 seconds each loop .

1 Like