I have a group of 7 lights which i control through a motion sensor or button trigger. However, a lot of the time not every light on the group turns on when the trigger is activated. Sometimes 5 will go on, sometimes 3, sometimes 6etc. Same with turning off. Is there some way to make RM or some other app verify the lights are in the right state or some better way to accomplish this or troubleshoot?
May need to add a couple of repeaters to the mix, but you could try putting in 1 second delay and reissue the command
Thanks I'll try the delay. I have repeaters nearby so i don't think that's the problem but I'll try the delay suggestion.
Are all of these zigbee devices? Even if only some of them are zigbee, you should turn zigbee group messaging on.
Yep they're all zigbee and i had the messaging on as well.
First thing I would do is disable on/off optimization and see if that fixes your problem
Leave zigbee messaging on and turn off on/off optimization?
Yep.
On/Off Optimization is a feature that, when it is enabled, will not send an off command to a light that the hub believes is already off. Likewise, it will not send an on command to a light that the hub believes is already on.
Disabling On/Off Optimization will make the hub send the on/off commands regardless of the current state the hub believes the lights to be.
On/Off optimization is really nice when you have large groups (20 plus lights), but with only 7 lights, I wouldn't worry too much about disabling it. If it fixes your problem, I would leave it disabled. If this is the case, maybe try to figure out if your hub always has the status of the lights correctly updated, if not, why?
What does the rest of your Zigbee mesh look like? Do you have any non-bulb devices, like Zigbee smart plugs? Additionally, what specific Zigbee bulbs do you have? Asking because many bulbs are known to be problematic when mixed with non-bulb devices on the same network.
Additionally, how are you "controlling" the lights? Is it just an "On" command, or are you setting level and color/CT at the same time? There are some issues with doing the latter two things in quick succession that I'm not sure have been resolved yet, and in that case, adding a small delay (do-able in Rule Machine; not so easy with Simple Automation Rules) may be all you need until that's addressed.