Yeah, Iām getting these too. Seems like something has broken in some recent updates. Iāve also noticed (I swear it didnāt happen before) that when turning on the lights, theyāll cycle through various colours etc. before arriving at their correct setting. I just want them to turn on straight to the correct brightness and colour temp for the current time of day. Think this sounds similar to the second point @Elenkhos just made.
Did you ever figure this out? I have an Inovelli Blue Series smart switch controlling five Signify Lightify under cabinet LEDs. Adaptive Lighitng only seems to work on the under cabinet LEDs if I target and control the light group from HA. But if I use the Blue Series wall switch, it doesnāt apply Adaptive Lighting settings (at least not for color temperature). Is there a way to make Adaptive Lighting work whether I use the Inovelli Blue Series smart switch on the wall, or make a call to turn on the lights in HA?
Itās continued to be a bit of a pain in the butt, but I do have a decently well working solution now. Iām only using Z2M; when testing ZHA, I wasnāt happy with ZHA + Skyconnect performance, so I scrapped it before I got very far and went back to only relying on Z2M.
For all my lights where Adaptive Lighting is configured, Iām using this blueprint that I wrote: ha_custom/blueprints/light_switch_al_controller_z2m.yaml at main Ā· xenokira/ha_custom (github.com)
Basically, the automations created from this blueprint enable adaptive lighting when up_single
(bound lights come on) is in a switch payload and disable adaptive lighting when down_single
(off), up_double
(dim up to full), up_held
(dim up), down_double
(dim down to lowest), and down_held
(dim down) are in the switch payload. The blueprint does more too: conditionally enables AL sleep, color mode, allows for control of a āsecondaryā light via the config button, etc. Thereās also support for āDirect Controlā of the primary lights; this is for cases where the switch is not bound to the bulbs and just has HA call the light.turn_on
and light.turn_off
services. My use case was pretty narrow for the direct control option, so I havenāt tested it much (and I know dimming behavior is funky when trying to dim from the switch). I just refactored it and have found a couple small issues that I worked through, but there could be more tweaks in the shorter-term.
Note, take_over_control
should be disabled. When enabled, I see issues where sometimes AL goes to manual_control while the lights are still turning on. I think this is because the bound switch is controlling the ramping of the lights (which I have set to 500ms on the switch).
As far as the experience goes:
Tapping āupā on the switch immediately turns on the Zigbee bound lights, which I have come on at the previous brightness / temperature settings. The automation is simultaneously triggered by the up_single
event, which immediately activates Adaptive Lighting and the adjusts the lights accordingly. Itās not perfect as lights the lights immediately adjusting can feel a bitā¦awkward, but itās been pretty reliable. Whatās nice is that when it does hiccup, tapping āupā on the switch again should re-apply AL.
Iām happy to share my VZM31-SN switch params, AL settings, etc. if theyād be helpful
An I missing something, or is everybody apparently fine with running their lights 24/7? Why canāt I set a sleep brightness of 0?
I could be wrong but Iāve never thought of sleep mode being for while youāre sleeping as much as for a nightlight, or when youāre tucking in. Although perhaps some people prefer to leave some lights in the house turned on and want a specific brightness
I just turn mine off when Iām sleeping.
No, my lights only come on if the lux level in that particular room is low enough and there is motion. None of my lights stay on all night and they only come on during the day if itās dark.
Hi,
Iāve been on AL forever but Iām in the process of transitioning to SK6812ās. For daytime they seem to work fine and coming in and out of sleep mode they perform beautifully. But in sleep mode, they turn red regardless of the color temp set in AL. Looking in the dev tools, when AL sends the Color temp to 3000 command, something gets lost in translation and only the red arrives (255). In looking at the integration, it seems like white channel is not supported in sleep mode. Itās either RGB or color temp. But when I send CT, sleep mode isnāt handling it as gracefully as day mode and just turns the lights red.
Does anybody else have SK6812s with a white channel and have overcome this in sleep mode? Really wanting to understand if its something Iām doing wrong or if thereās a feature gap that Iāve never noticed till now. My current LEDs have a white channel and they allow for sleep mode CT to work properly.
I have mostly zigbee smart bulbs around the house and they all work great with adaptive lighting.
However, I have a few wifi smart bulbs that donāt seem to react the same way as the zigbee bulbs, despite the AL settings being exactly the same.
For example, I have a table lamp either side of the bed. One is zigbee (Moes) and the other is wifi
(Ewelink). When the AL night switch is on the zigbee bulb comes on at night colour, but the wifi bulb comes on white. More recently, I put 3 Govee wifi GU10 bulbs into a ceiling fixture and they donāt seem to be adapting at all
Is it just a case of finding the right settings for each lamp, or is there a known issue with adapting wifi lights versus zigbee?
*** EDIT ***
Think Iāve answered my own question after playing around with the settings
I guess thatās why AL is so configurable. Every make of light is different and how lights adapt for a given setting can vary quite a bit.
Anyway, sorted now.