So it seems the issue is within adaptive lighting integration. Doesn’t matter how the light is turned on, it kicks in late rather then immediately after light is turned on. Not sure if it was caused by the integration update or home assistant update. @dbrunt any idea?
I am no expert nor am I currently even using AL since I use a Circadian Routine in Node Red but I believe it might depend partly on the device and the integration since I seem to recall reading that some Zigbee devices are first sent an On and then followed by the brightness level. With everything in HA in constant flux and improvement I’m not going to begin to try and figure it all out!
If a light is turned on outside of AL, AL is just monitoring its state change and then adjusts after the fact so there will be a delay. Whether that delay is perceptible or not depends on countless factors. My office lights Sengled Zigbee) come on at the brightness they were last turned off. Circadian then kicks in and sets the current color/brightness. It’s always been noticeable if the difference is large.
It seems that for some reason the integration needs a second to react to light on event. Not sure why it changed. It would work instantly before. Not sure how not works but it would be beneficial to subscribe to an event and react immediately when the light is turned on.
It definitely does. I am new to HA but I’ve been through probably 15 drivers with my bulbs previous to this last change and every single time the experience has been different.
I have TP link bulbs that you can program to have circadian built in from the native app. Because all my connections were cloud based, the lights were doing this on their own with simple on/off commands. Whereas when I switched to HA with a local connection bypassing the circadian setting in the cloud, HA would just turn on whatever was last. When I added the AL layer on top of it it worked great as long as I was only using HA. While I was migrating 300 devices, I still had TP link connections straddled in Alexa and Hubitat that were using cloud connections so if any automations were still being ran from my old hub or if I would use Alexa to turn on the lights, they would come on in their native circadian, but then HA would detect the light on and then adjust it. It definitely wasn’t ideal but for me it was only temporary while I had multiple connections/configs for bulbs.
I’ve been enjoying the AL a lot. I looked back at webcore and so much of my custom work was just simulating this behavior. HA and AL do this effortlessly.
Thanks. I did it similarly by using adaptive lighting service call.
Here is the blueprint
Hi everyone,
I’m new to AL and I have a bit of a hard time understanding this :
When only_once is set to false my bulbs only adapt with the “regular” transition time when I switch them on. They do not adapt at the initial_transition time, which means when I switch on a light at nighttime it will light up at 100% and then dim over 30s.
When I set only_once to true it works as expected but then my lights are not adapted throughout the day…
Anyone has an idea as to what may cause this? Or maybe this is expected behaviour?
the ‘only once’ option off and my lights work perfectly, setting to the correct brightness and colour temp at any time of the day.
What method are you using to turn the light on?
Thanks for trying to help me!
I turn them on using a “regular” light switch. When they are off they are unreachable for HA. Would this function work only when turning them on digitally?
So the light switch is cutting power to a smart bulb?
That would be the problem since the bulb can only receive the Adaptive Lighting settings once it reconnects to wifi and gets the days from HA
Yes that’s sadly the case.
So to get this working I have no choice but to buy smart switches or an Alexa echo dot for all of my bulbs? Any cheap switches I could buy for less used rooms like toilets?
Not smart switches, just leave the regular light switch on and control the smart bulb with another device. I use Xiaomi wireless buttons. They are really cheap but you will need a ZigBee transceiver like a Conbee 2 or similar.
Thanks a lot for your recommendations! My wife hates you 
In France the Xiaomi buttons cost the same as hue dimmer switches (18 vs 20€) so I just bought 4 hue dimmers for high use rooms and 4 Xiaomi motion sensors (which are way cheaper than hue sensors) for less used rooms and corridors
Ikea Dimmer switches work very nice as well.
I use these ones where I want local control at the wall switch location:
Philips Hue Dimmer Switch, White, Dimmer Switches - Amazon Canada
You remove the regular switch and wire power to the light permanently on. The included plate covers the box and provides a magnetic mount to hold the removeable battery powered switch.
Sorry, I really should have also recommended the IKEA 5 button remotes. I have a few of those and love them. Having 5 buttons means you can set them up to control a few things from the one location. Thery are pretty cheap too.
If I adjust a light’s brightness in HA, I find it very slowly (over a minute) returns back to the AL setting. Take back control is enabled, so I assumed that would mean manual changes would stop AL. Anyone else having the same issue? Is there a workaround?
Has the light that was changed been marked as “manually controlled”?
NM, I fired up a test and if I adjust the color_temp of a light, manual_control: gets set with the entity_id I changed. Not so if I just adjust the brightness though…
I’ve found the issue. I was changing a light (light.living_room_main) in HA Lovelace, but AL was configured to look at the hue group the light belonged to (light.living_room).
I hadn’t realised as there is only one light in that group.