Replies: 2 comments 7 replies
-
|
@jtbandes did you manage to solve it since then? If not, I think I can help you 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
Nope, I haven’t solved it yet! I just turned off adaptation and made a shortcut to reapply the settings :( Please let me know if you have any suggestions! |
Beta Was this translation helpful? Give feedback.
-
|
@marazmarci Did you have some suggestions about how to solve this? |
Beta Was this translation helpful? Give feedback.
-
|
I tried very hard to implement some workarounds with an automation, partly successfully, but it's very hacky, and unstable. I think it shouldn't be this hard to solve this, but as far as I understand, there are known issues, which likely affect this, and I expect that I can provide you a clean and stable solution whenever some of these issues are fixed: |
Beta Was this translation helpful? Give feedback.
-
|
Hi @jtbandes, wondering if you have made any progress on this. I have a similar issue where Inovelli blue switches are bound to a Zigbee group with smart light bulbs. The Inovelli switch operates in Smart Bulb Mode (SMB) and interacts with the bulbs directly. My issue is similar where upon turning on lights using the switch, lights will be set to whatever value it was previously at. Adaptive Lighting then kicks in and adapts the light. This can cause a sudden lighting change eg first time using the switch in the morning. I believe the issue is due to the Zigbee binding, as the command to turn on lights is sent before Adaptive Lighting can see the change from Home Assistant. The flow of data would look like:
I hope someone with more knowledge is able to chime in here. A workaround or solution would be greatly appreciated. |
Beta Was this translation helpful? Give feedback.
-
|
I haven't made any progress, though to be honest haven't really tried anything else since I first posted this. I saw there were some recent updates to this component, so it's possible things have improved although I haven't checked. From your description it sounds like your setup actually works better than mine – "Adaptive Lighting then kicks in and adapts the light" – this was not happening for me for many of the lights. So I would be interested to know how you configured things! I think I would be able to live with a brief flash of the wrong color when the lights first turn on in the morning. Perhaps it can be smoothed out by using a transition instead of an immediate change. My workaround has been the following automation which maps a double-click of the config button to apply the adaptive lighting on demand. I have simply gotten used to doing this double-click dance when I turn on the lights and they are at the wrong temperature. alias: Reapply Adaptive Lighting
description: ""
mode: single
trigger:
- device_id: ...
domain: zha
platform: device
type: remote_button_double_press
subtype: Config
# ...and more for other device_ids
condition: []
action:
- service: adaptive_lighting.apply
metadata: {}
data:
adapt_color: true
adapt_brightness: false
entity_id: |
{{
{
device_id('light.room_1_switch_light'): 'switch.adaptive_lighting_room_1',
...more for other adaptive lighting configurations/rooms...
}[trigger.event.data.device_id]
}} |
Beta Was this translation helpful? Give feedback.
-
|
The following is what I have to get the lights working. I hope it works for you as well. Zigbee settings
Adaptive Light settings Automation |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. Why do you trigger adaptation from an automation but also And am I understanding correctly that you don't have any auto adaptation throughout the day, only when the lights are turned on? |
Beta Was this translation helpful? Give feedback.
-
|
I found that triggering adaption from automation was more predictable than waiting for adaptive lighting to automatically adapt on first on. Less weirdness and abrupt changes.
The lights will adapt throughout the day, as the last step in the automation ensures manual control is off. |
Beta Was this translation helpful? Give feedback.
-
I have several zigbee bulbs and am experiencing some unexpected behavior with Adaptive Lighting. I have seen issues where some bulbs randomly turn on to a low brightness value after I manually turned them off (similar to #85). I have also seen problems where adaptive lighting does not seem to adapt unless I manually trigger it by reloading the configuration or toggling off/on the "Adaptive Lighting: X" switch. I realize that it is likely due to some configuration issues, so I'm hoping someone can help me figure out what I need to change. Any advice would be appreciated 🙏
Goals: I would like to use adaptive lighting for color temperature and maybe brightness (my bulbs are only white-adjustable, not full RGB). I want it to work regardless of the lights' on/off state — that is, if the lights are off, then when I turn them on I expect them to be at the current adapted color temp, not whatever temp they were at prior to turning them off. If the color temp is manually overridden for a room then I would like Adaptive Lighting to pause until the lights are turned off/on again (I believe this is what it is supposed to do by default). Also, ideally, I would like to be able to adjust the brightness of the lights manually but still have adaptation continue for the color temp.
Devices: I have Philips Hue bulbs and Inovelli light switches. For each room I made a zigbee group with the bulbs, and I use zigbee bindings so the switch sends on/off/dim signals directly to the bulb group. This is a requirement because I want the switches to continue working even if HA goes offline.
I have been using the zigbee groups as the target lights in Adaptive Lighting, but I've also generally experienced some problems with group messages getting delayed or dropped when sending too many of them. The discussion in this thread and this thread seem to suggest using HA groups for performance. However, the adaptive lighting readme explicitly states "create a group in your Zigbee software (not a regular Home Assistant group) and add that single group to the Adaptive Lighting configuration", so I went with that suggestion.
To focus on one problem first, I have a room named
T Officewhere turning the lights off and on via the switch does not trigger adaptation. Instead I have to toggle theAdaptive Lighting: T Officeswitch off and on, which causes them to adapt immediately.Here is a debug log when I turned the lights off then back on via my physical light switch. In the log you can see that AL detects the state change of
light.silicon_labs_ezsp_t_office_group(the zigbee group). But then it saysT Office: Ignoring 'off' → 'on' event for 'light.silicon_labs_ezsp_t_office_group' ... because 'light.turn_on' was not called by HA and 'detect_non_ha_changes' is False.And here is my current configuration — apologies for any errors as I had to type this out manually, I couldn't find a way to export the YAML values:
Here is another log when I tried the following steps:
detect_non_ha_changes: trueThis time, the lights came on to the correct color temperature, but only to a very dim level. They had been at full brightness before I turned them off.
Thanks in advance if anyone is able to provide guidance here. I would love to be able to use this component, but currently it seems to just cause frustration for users when the lights don't behave correctly.
Beta Was this translation helpful? Give feedback.
All reactions