Not everything works perfectly all the time, obviously. A briefly dropped signal can throw a wrench into many a rule and keep you from seeing it executed completely. So I'm just curious how other people approach redundancies.
For example, I've got a nightly routine that turns off all the lights and other devices throughout the house once my wife and i are both in bed. But I've got a "backup" that runs again at midnight to turn off anything that might still be on if it somehow got skipped earlier. And, for some more finicky devices, I've got another rule within their native app to do the same thing again.
So I'm just wondering what other people's approaches might be. Do you just deal with the occasional bulb that's still on when you wake up the next morning? Do you limit redundancies to additional Hubitat rules? Do you just have a rule repeat until you can confirm a certain status? Just curious how you all might be approaching the idea.
I think my approach has been to just replace the problematic devices. They just aren't worth the frustration. Some more 'critical' items, like locking the doors and closing the garage door, I do include a check in the rule to make sure whatever was supposed to happen did.
I face the same issue, where a random device does not turn off. I have discovered that this happens only in rules where a lot of devices are turned off (my "Goodnight" RM). It is not any particular device that stays on and is somewhat random. (it NEVER happens when I turn on lots of devices). I've spent lots of time studying logs and never found the problem. This happens in my setup maybe once every two weeks.
I started to use Bruce Ravenel's "All Off" app which adds metering and retries and so far, I haven't had a device stay on yet,
I have a similar issue with my Christmas lights. I command a lot to off at the same time so I attribute it to network traffic. I put my Off action inside a While loop like this:
While (Light 1, Light 2, Light 3, Light... any is on) Repeat 10 times every 0:00:06
Off: Light 1, Light 2, Light 3, Light... (Command only switches that are on)
END-REP
Overkill? No doubt. 2 or 3 repeats is probably enough but it's not too taxing to the hub so I left it like this. I haven't found any of my lights on after doing this.
Room Lighting is handy for stuff like this. It will retry the on command three times if the device status doesn't update.
Metering is a must have for commanding a lot of Z-Wave devices. It helps to spread out the commands so that they aren't stepping on each other. Groups and Scenes is handy if this is needed as it's an option you can enable. IIRC, Room Lighting has this baked in.
I tend to steer clear of "optimization" options. It tells the hub to only send the "on" command if the device state shows as "off." You may find that a device is showing as "on" but is physically off that will never be commanded to "on" with that option.
I have a similar problem with my End of Day (EoD) Rule. I've created Groups for different Zones within my house Living Area, Sleeping Area, and Outside. My EoD rule is normally triggered by an Alexa command "Goodnight" but also at midnight, this rule also changes the Mode to Night:
