I've read in another thread that a rule cannot resume on it's own accord. So what would be the best way after the doorbell reports "active", to pause for 5 minutes before resuming, without having to have a separate rule?
-Thanks
What happened to using a solution like this for that rule?
1 Like
That doesn't work all the time for some reason. It often gets stuck with a "Required Expression False" message and won't run again.
There's no reason that should happen (unless you interrupted the rule with Done or Update Rule). What do Logs say when you experience this? That is the only way to know since the rule itself looks good.
It is also helpful if you can link to previous discussions like this -- or just continue the discussion there -- instead of treating future related issues as existing in a void, as the context is helpful for others trying to help. Please do so going forward. Thanks!
3 Likes
Okay. I was thinking this concerned pausing not delaying. I think you're right I must have interrupted the rule when using the Booleans and delay. I just tried it several times and it's working as expected.
-Thanks
Something to consider. I started using the conditional action instead of required expression. If the hub happens to shut down and not come back on before the delay is over the private boolean can get stuck as false and disable your rule until you manually reset it. In my rule below, whenever the hub restarts the private boolean will get set back to true.
Thanks, that is good to know! That's probably why my rule would get hung occasionally because I rebooted the Hubitat when it was "waiting".
FYI, that alone won't cause any problems -- only if the hub is off when the scheduled job to change this back was supposed to run.
This is what causes the issue. A simple reboot probably will not cause issues, but it can. For a short delay of three minutes if you happen to reboot towards the end of the delay the hub may not come back up in time. So I have found this method to be less problematic.
1 Like
