Generally speaking, that shouldn't be necessary. If it is then I'll definitely mention it.
@rob, please include the link to the Raw Code for your drivers and apps in the header. This way we could just do an Import and paste the location. Easy Peazy.
Edit: See example here:
1 Like
I had intended to start a new thread somewhere with those once it goes to beta with the links. Perhaps I should do it this weekend. I'd also like to add App Watchdog support so you'd be notified when anything was updated.
1 Like
Thanks for fixing the DD driver. Any chance of adding a transition time value for color temperature? The current one says "set color time", but I think it really means level.
I wish I could, but the parameters are fixed by the capability as far as I know.
The defaultTransition should apply to colour temperature. Or you can use SetState. I suppose I could add more preference settings for different transitions, but I'm a little reluctant to do that.
I see. I am not seeing defaultTransition being applied to color temperature on the D&D bulbs. Only level.
So far it's not exactly a harmonious combination with the Circadian Rhythm app due to the status updates. The CR app adjusts the CT as soon as it receives notice the bulbs are on, which in this case doesn't happen for many seconds. I think the Circadian app might need some modification to accommodate.
Okay, I'll take a look
1 Like
Yay!
My buttons work like this:
Button 1 Push = Toggle on/off
Button 2 Double-tap = Fade to 4500K and 100% brightness (This is my "bright lights" setting)
Button 2 Long-push = Fade to 2500K and 60% brightness (This is my "comfortable/TV lights" setting)
This works really well, and the only tweak I've made was to add a command at the end of my "off" trigger to set the lights to 2500K and 10% brightness (without power:on in the setState map). This way anytime I turn the lights on it first dims on to that level low easy-on-the-eyes setting and then dims from there to whichever of the two settings I requested with the button (bright or comfy)
EDIT: LOL! I just realized that by adding that extra setting after triggering off, I completely negated the whole toggle off and back on to the previous setting behavior I wanted! 
@rob Thank you SO MUCH. Your work is amazing. Please let me know if I can help out in any way in the future.
1 Like
I've rolled back that dumb act of mine. 
2 Likes
I'm hoping I've fixed the transition issue now
Links:
1 Like
Any further updates will have to wait for tomorrow 
Oh, and you may need to save your preferences for each device for default transitions to work. You should see a new state variable called transitionTime that contains the value you chose.
Thanks, it was missing the https at the beginning for some reason - I've fixed it now
The one reported in LIFX Local Control
It was working fine for me, or at least I thought it was. I was directly using the preferences setting for defaultTransition in some commands, but that seemed to stop working, so I'm now saving the value in the device's state.
Gotcha. Thanks.
Hmm... Now it's not utilizing the transition
time value for color temperature or level. Same behavior in the Color driver.
I'm able to manually change the values within the driver code and get it to work, but setting them via the preferences doesn't stick.
Do you see the transitionTime variable in the state? Note, not colorTransitionTime
If you don't try changing the value in preferences then saving again.
Both are there. The transitionTime variable changes with setting the preferences, and the colortransitionTime doesn't change. Unfortunately the reported state is not reflected in the bulb, which appears to stay at the default 0.0 time.
It doesn't use the default transition time for SetLevel in any driver because it's using the one from the SetLevel command. But it's definitely using it for SetColorTemperature on the LIFX Color driver for me, but not, as you say, for the Day and Dusk driver.
This is very puzzling
