I have a group of lights set up for the master bedroom. And a set of custom sliders to control the individuals or the group. When I turn them on via the individuals they turn on to the correct AL brightness and color. However when I turn them on via the group they turn on brighter and a different color.
I tried using both calling light.toggle, and I made a script to call light.turn_on or off depending on the group state. Neither work as desired. Any ideas what Iām missing?
Itās the first action_button that I havenāt got worked out.
Hereās a video of what Iām talking about. Something is intermittently interfering with only the group. It was pretty consistent last night, but this morning Iāll occasionally get a desired outcome (like the first time I hit the button at 0:01, however you may notice it paused midway up for a moment. Then later it stops at the same mid way location.
Maybe nothing to do with AL. How do I get into the logs that would show whatās going on?
Side question. Is there a better way to share a video?
I think that is what I will have to do (automating switching off manual control). I had just thought it was automatic when turning off the light.
Yes this is with the āāātake_over_controlāāā flag on. I often leave it off as I never manually change lights, but for some I do turn it on.
Thinking on the issue you reported, adaptive lighting offers the āapplyā service that will turn on lights with the correct settings. Try calling that instead of turning on the light group. Also, there is the āinterceptā setting in adaptive lighting configuration.
Is this possibly related to the slider card doing something funny with the formatting of the yaml? I just tried to switch back to the light.turn_on service call, and itās giving an error about not passing the entity. I think I had to manual troubleshoot that before to get it working (as it was working in the video - intermittent incorrect brightness/color).
ā¦ 10 minutes later ā¦
I modified my ātoggleā script to use the adaptive_lighting.apply service instead of light.turn_on. I had to use the turn on if off, and the adapt brightness and color options. That all works. Whoo hoo! Thanks @euinor!
I am getting something funny where my transition on the adaptive_lighting.apply and light.turn_off parts of my toggle script is ignored unless itās 2 seconds or more.
I think I figured out part of the issue with the color and brightness being intermittently adaptedā¦
Iād recently made a color_profiles.csv to apply a default transition to any light. I wondered if that was impacting this current issue so I changed the file name and restarted.
Now the color and brightness is adapting as intended, however at the expense of the loss of default transition value.
Since the adapts are working when I address the individual lights, but not as a group (or even if I break the group apart but call them all at once) Iām led to think that someone AL is missing itās take over when all of the lights are turned on at the same moment.
@euinor, I just noticed the setting autoreset_control_seconds on the AL configuration. Iām not sure if that could be helpful in your case, but thought it worth mentioning.
Edit: I think I have found the issue. I had an automation that would toggle the light group for the room when a button was pressed. This triggered the manual control every time the lights were switched on. Iāve changed the automation to turn on the lights individually (using the same lights as in the adaptive lighting configuration) and it seems to work now.
Funny, I had read the instructions on to use individual lights and not change groups. I must have forgotten about that when setting up the automation.
Hello @basnijholt
Thanks very much for the amazing adon.
I have Philips Hue and Iām noticing that if I activate any hue scene, the addon starts adapting immediately even though I have the option in the configuration to only adapt on bare turn_on (see screenshot below).
Dear community, is there an easy way to configure adaptive lighting to have two bright phases (evening and morning) with darker inbetween? I want the lights in my kids room to be at:
20% between sunset and 8:00 pm
5% between 8:30 pm and 6:00 am
20% between 6:00 am and sunrise
(with gradual transitions inbetween)
I would prefer not to have to manually press a sleep mode button (in case sleep mode is the solution, Iāve not used it yet). Thanks!
Yes, while Iām unfamiliar with the details of a āsleep switchā, I could automate turning that on at 8pm and off at 6am. Until now I didnāt assume there was a transition to the sleep mode, but as youāre now asking I assume there is a way to slowly transition to/from sleep mode over e.g. 15 minutes?
Has someone else noticed unwanted behaviour after upgrading HA core to 2024.3.x (from 2024.2.x)? Iām guessing there have been some changes in the light.turn_on service call.
Transition time is not honored anymore with the lights that have adaptive lighting enabled. The following service call turns the light instantly (< 2 s) on. In the previous HA core versions, the specified transition duration was used (60 s in the example).
When turning light on with the service call the adaptation now begins from the previous state. So, if the previous brightness was 100 % and the adaptive lighting sets the brightness to 10 % the brightness goes first to 100 % for a short period and then changes to 10 %. This can be really annoying in the late evening. In the previous HA core versions the adaptation started from 0 % brightness to the current brightness.
adapt_delay and initial_transition are set to the default values (0 and 1 respectively). adapt_only_on_bare_turn_on is set to true (default false). I tried to change them but it didnāt resolve the above mentioned issues.
I have not changed anything in adaptive lighting settings so this must be related to the HA core update. Has anyone come up with a solution?