#Zigbee levelcontrol binding changing color of light group (and I don't want it to)

1 messages · Page 1 of 1 (latest)

stark geyser
#

I have set up a zigbee group and added some lightbulbs to this group. I then bound this group to a Niko zigbee switch by binding the OnOff and levelcontrol bindings. This basically works, I can turn the group on and off, and long pressing the switch will dim or brighten the bulbs.
The issue is that it also changes the color of the bulbs, I think to a preset color. The zigbee logs mention the following when long pressing the switch:
{'options_mask': <OptionsMask.Execute_if_off_present|Couple_color_temp_to_level_present|252: 255>, 'options_override': <Options.Execute_if_off|Couple_color_temp_to_level|252: 255>}
I don't know what the above log means, but it does seem to say something about setting the color temp.
Does anybody know how you can assign a zigbee (or zigpy) command to the levelcontrol binding so that it keeps its current color when dimming the lights?

amber granite
#

If you bind the device to the group, the device at that point is communicating directly with the group members: ZHA has no way to control what's being sent

#

The Couple_color_temp_to_level bit in the options mask says the command being sent by the remote is explicitly tying the brightness of the bulb to the color temperature, so the dimmer you make the bulb, the warmer it gets

stark geyser
stark geyser
indigo echo
#

"execute if off" is a flag that tells the bulb to apply the brightness/color change even if the bulb is currently off, so that the next time it gets turned on it will already be at the set brightness/color.

#

the only thing binding does is tell one device to communicate directly with another device. what it sends is completely up to the device.

#

(as far as the bulb not getting cooler when brightening - the exact behaviour of the "couple color temp to level" is manufacturer specific, it depends on the firmware in the bulb)