You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a scenario that doesn't seem to be covered by ControllerX, though I realize that it might be a little esoteric.
In my kitchen I have two ceiling light fittings and each one of them contains three bulbs. So I have a group called kitchen_left that contains bulbs kitchen_left_1, kitchen_left_2 and kitchen_left_3 and a similar setup for kitchen_right.
I have two IKEA E180 controllers, one at each end of the kitchen, called kitchen_left and kitchen_right.
I'm using zha as my zigbee integration.
I have very similar yaml files for each controller - ie only the names have changed. Currently I use merge mapping for the main on/off component of each controller and the script switches on or off one or both groups depending on the groups' statuses. I have assigned the left arrow (press_257_13_0) and right arrow (press_256_13_0) to toggle the appropriate group (right or left). It would be nice (and cleaner) if I could do away with the script and have the toggle button switch on both sets if they're both off and switch off both sets if either of them is on.
The thing that, frustratingly, doesn't work is that I can't get the brightness up/down buttons to behave as I'd like. Currently each brightness button only controls the group to which it is assigned. ie left does kitchen_left and right does kitchen_right.
I'd like for both sets of brightness up/down to control all lights so that the kitchen's brightness is maintained at the same level at both ends.
I tried adding all six bulbs to a group called kitchen and having all buttons behave the same but that proved disastrous. Something somewhere along the line became confused and individual bulbs would remain on when they should be off and vice-versa. And sometimes it would be like being in a 1970s disco with lights flashing on and off randomly.
I can't find it stated anywhere but zha seems to handle groups of up to four members only.
I have a scenario that doesn't seem to be covered by ControllerX, though I realize that it might be a little esoteric.
In my kitchen I have two ceiling light fittings and each one of them contains three bulbs. So I have a group called kitchen_left that contains bulbs kitchen_left_1, kitchen_left_2 and kitchen_left_3 and a similar setup for kitchen_right.
I have two IKEA E180 controllers, one at each end of the kitchen, called kitchen_left and kitchen_right.
I'm using zha as my zigbee integration.
I have very similar yaml files for each controller - ie only the names have changed. Currently I use merge mapping for the main on/off component of each controller and the script switches on or off one or both groups depending on the groups' statuses. I have assigned the left arrow (press_257_13_0) and right arrow (press_256_13_0) to toggle the appropriate group (right or left). It would be nice (and cleaner) if I could do away with the script and have the toggle button switch on both sets if they're both off and switch off both sets if either of them is on.
The thing that, frustratingly, doesn't work is that I can't get the brightness up/down buttons to behave as I'd like. Currently each brightness button only controls the group to which it is assigned. ie left does kitchen_left and right does kitchen_right.
I'd like for both sets of brightness up/down to control all lights so that the kitchen's brightness is maintained at the same level at both ends.
I tried adding all six bulbs to a group called kitchen and having all buttons behave the same but that proved disastrous. Something somewhere along the line became confused and individual bulbs would remain on when they should be off and vice-versa. And sometimes it would be like being in a 1970s disco with lights flashing on and off randomly.
I can't find it stated anywhere but zha seems to handle groups of up to four members only.
kitchen script.txt
kitchen_right.yaml.txt
kitchen_left.yaml.txt
Thanks,
Ken MacKenzie
The text was updated successfully, but these errors were encountered: