Hi folks. First off — love the Caseta system. I’ve got roughly 65 devices on my network and everything has always worked great… until now.
I’ve got two of the new outdoor smart plugs (call them plug A and plug B, respectively) that I have set to auto turn on and off when paired with the Lutron caseta motion sensor.
The A and B devices always turn on properly and almost always turn off properly. Weirdly though, roughly 2-3 times out of 50, plug A will turn off and plug B won’t.
When this scenario happens (again, it’s very infrequently, but enough to be annoying since lights remain on that should be off), it’s always plug B that doesn’t turn off.
When it happens, I can open the Lutron app and see the plug is still on and switch it off, and it turns off. It’s like the motion sensor either isn’t sending the off command or the plug isn’t responding when it’s sent the first time.
I’ve also tried changing the logic to orchestrate this from Apple HomeKit such that plug B should be turned off when plug A turns off… and while there is a delay of about 0.5 seconds for HomeKit to trigger this, it usually worked but also ran into the same problem where (seemingly randomly) plug B wouldn’t turn off and you need to do it manually.
So I’m at a complete loss as to what’s causing this. I’m going to work around the problem with some custom logic in my Crestron PRO3 to detect this error scenario and manually shut plug B off if plug A isn’t on… but this is obviously just a hack and hoping can figure out what the root cause is.
Thanks in advance for any ideas!