Yeah, that link gives me a “no text channels” error on Discord. So not as explicit as you would think.
Literally the section labelled Fix.
And that didn’t work for me. The control button does not register in the Z2M logs. It did before I upgraded Z2M.
EDIT - Multi-taps also don’t register. Nothing on the Z2M logs. Again, it worked before the upgrade.
Sorry I didn’t read your other post. I didn’t use anything with the control button unfortunately. I was focused on the main toggle. I’d look at the other topic posted unfortunately.
FYI, looks like a fix was merged in for the next zigbee2mqtt release that will restore the group behavior that allows the switch to be in the zigbee group. There may be no need to revise your groups as suggested earlier in this thread once the next release (2.1?) is posted
2 Likes
Great to hear, thanks for the update!
I ended up not going too far down the road of re configuring hoping for a fix sometime soon. I have just removed the switch’s from the groups and am dealing with the out of sync states for now. Looks like I will wait a little longer before thinking about building any automations to re-sync…
Thanks for the heads up. Definitely possible it’s unrelated, but I’ve noticed some intermittent performance reduction after removing the switches from the groups. After this rolls out, I might put the switches back into the group, remove the added binding, and see how it goes.
Just updated to z2m 2.1. Group behavior works the same as it did in 1.42.
However, I did try the fix mentioned by clintm and that works too (removed switch from the group and bound endpoint 1 and 2 of the inovelli to the group). The HA/switch/group state are all in sync when doing it that way. I dont have access to the discord discussion clintm referenced, but perhaps this is the correct way to do it if you just have a switch bound to bulbs.
The 2.1 update did fix it for me so I just went back to including the switches in the groups with no issues since I made the change yesterday.