I have a couple simple automation rules that turn lights on or off to follow another physical light switch.
This has happened once or twice a month for a few months but is getting much more common.
For example I have two lights in my office. There's a floor lamp that follows the state of the ceiling light. Sometimes I turn the ceiling light on but the floor lamp doesn't switch on. Sometimes it doesn't switch off. Usually turning it off and on a couple times gets the automation to kick in.
All the physical switches that are being mirrored are zwave plus. The other devices are a mix of zigbee and wifi devices.
Hub load seems fine. I'm not sure how to troubleshoot this since it's so extremely random. It might be days before it happens again. And when it happens I usually am in a hurry and don't have time to log into the hub to look.
When this has happened to me in the past, I would turn on logging to the rule and the device. This helps pinpoint the source of the issue - is it the rule that doesn’t run? The command that isn’t sent? The command not received by the device?
I just turned logging on for those rules. I thought about it but wasn't sure if it was like the debug logging that turns itself back off.
I also turned off enable optimization in those rules. I did a little googling on that, maybe the lights I'm controlling aren't properly reporting their status.
That’s the most likely culprit in my experience. Another would be if the trigger light isn’t reporting properly. Probably the least likely thing is that the SA rule isn’t firing properly considering the intermittent nature.
I don't know how I never really paid attention to that optimize setting. I always just left it on and never bothered to google what it does.
I have another rule that just occured to me that occasionally doesn't fire. Turn on basement lights when door is unlocked by keypad. I turned off optimization on that one too and will pay closer attention.
