basnijholt
Different behavior despite having the same configuration
Home Assistant Adaptive Lighting Issue Template
Bug Reports
Before submitting a bug report, please follow these troubleshooting steps:
Please confirm that you have completed the following steps:
- [x] I have updated to the latest Adaptive Lighting version available in HACS.
- [x] I have reviewed the Troubleshooting Section in the README.
- [x] (If using Zigbee2MQTT) I have read the Zigbee2MQTT troubleshooting guide in the README.
- [x] I have checked the V2 Roadmap and open issues to ensure my issue isn't a duplicate.
I have two Adaptive Lighting configurations for different rooms but the behavior differs.
Room 1:
{'lights': ['light.z2m_group_kantoor'], 'interval': 90.0, 'transition': 45.0, 'initial_transition': 1.0, 'min_brightness': 15, 'max_brightness': 100, 'min_color_temp': 2000, 'max_color_temp': 4500, 'prefer_rgb_color': False, 'sleep_brightness': 1, 'sleep_rgb_or_color_temp': 'color_temp', 'sleep_color_temp': 1000, 'sleep_rgb_color': [255, 56, 0], 'sleep_transition': 1.0, 'transition_until_sleep': False, 'sunrise_time': None, 'min_sunrise_time': None, 'max_sunrise_time': None, 'sunrise_offset': 0.0, 'sunset_time': None, 'min_sunset_time': None, 'max_sunset_time': None, 'sunset_offset': 0.0, 'brightness_mode': 'default', 'brightness_mode_time_dark': 900.0, 'brightness_mode_time_light': 3600.0, 'take_over_control': False, 'detect_non_ha_changes': False, 'autoreset_control_seconds': 0, 'only_once': False, 'adapt_only_on_bare_turn_on': False, 'separate_turn_on_commands': False, 'send_split_delay': 0, 'adapt_delay': 0.0, 'skip_redundant_commands': True, 'intercept': True, 'multi_light_intercept': False, 'include_config_in_attributes': True, 'name': 'Kantoor'}
Room2:
{'lights': ['light.z2m_group_slaapkamer'], 'interval': 90.0, 'transition': 45.0, 'initial_transition': 1.0, 'min_brightness': 10, 'max_brightness': 70, 'min_color_temp': 2000, 'max_color_temp': 4000, 'prefer_rgb_color': False, 'sleep_brightness': 15, 'sleep_rgb_or_color_temp': 'color_temp', 'sleep_color_temp': 1000, 'sleep_rgb_color': [255, 56, 0], 'sleep_transition': 1.0, 'transition_until_sleep': False, 'sunrise_time': None, 'min_sunrise_time': None, 'max_sunrise_time': None, 'sunrise_offset': 0.0, 'sunset_time': None, 'min_sunset_time': None, 'max_sunset_time': None, 'sunset_offset': 0.0, 'brightness_mode': 'default', 'brightness_mode_time_dark': 900.0, 'brightness_mode_time_light': 3600.0, 'take_over_control': False, 'detect_non_ha_changes': False, 'autoreset_control_seconds': 0, 'only_once': False, 'adapt_only_on_bare_turn_on': False, 'separate_turn_on_commands': False, 'send_split_delay': 0, 'adapt_delay': 0.0, 'skip_redundant_commands': True, 'intercept': True, 'multi_light_intercept': False, 'include_config_in_attributes': True, 'name': 'Slaapkamer'}
Differences:
lights: kantoor=['light.z2m_group_kantoor'], slaapkamer=['light.z2m_group_slaapkamer']
min_brightness: kantoor=15, slaapkamer=10
max_brightness: kantoor=100, slaapkamer=70
max_color_temp: kantoor=4500, slaapkamer=4000
sleep_brightness: kantoor=1, slaapkamer=15
name: kantoor=Kantoor, slaapkamer=Slaapkamer
Both are Zigbee2MQTT groups containing Hue lights. If I turn on a single light in the first group (kantoor), the other lights stay off. If I turn on a single light in the second group (slaapkamer) all other lights turn on as well.
The second group is newer then the first. I tested the behavior trough switchting the light groups in the configs and then the behavior also switches rooms so it probably is something in the AL config. But what?
I would like the behavior of the first group, if I turn on one light in the group then no other lights should turn on. I know take_over_control can achieve this, but I believe this is not the exact same.
Hi there,
Do you have any light.group defined that has both ZB groups in it?
Groetjes,
Hi @fbloemhof, It could be that you have a lingering ZB group membership on some lights from both groups. To make sure the bulbs are only part of the ZB group you want them to be, you'd have to reset/re-pair all of the affected lights and re-group them once again.
I had similar weirdness where one light's status would affect another unrelated light group. Turned out that the light in question still had a lingering registration to older ZB group. Cannot recall if you were also part of that convo?
It's a minor nuisance to re-pair all lights, but it's also a little effort that can lead to great pleasure. Groetjes,
Forgot to mention, best to go all-in here. If you are truly stuck, check for any of the lights if they are part of:
- an adaptive lighting instance or instances
- a HASS light group or groups
- a ZB group or groups
An adaptive lighting instance you might have lying around dormant somewhere might still act on the status of one of the lights that are also part of a ZB group. For example:
- bulb1 + bulb2 = group1
- AL1 has bulb2
- AL2 has goup1
Status changes of AL2 will affect bulb2 AND AL1.
Status change of AL1/bulb2 will affect group1 and AL2: HASS groups also have a (default) state behavior that will report the group as "on" if one of the members is "on". This will trigger AL2 to control the HASS group as one and on the next update it will turn on the entire light group for you.
Nesting can make this even more difficult to wade through, e.g. using light groups containing ZB groups and bulbs in AL
Groetjes,