I think there may be a bug with RM3.0 with wait and cloud end points. I have a triggered rule that when I press a widget on my phone, calls a HE cloud end point, which then performs a number of actions. I suspect that the wait part of the rule is being actioned, irregardless of whether the trigger is triggered.
The issue is that I'm getting the notification "House now armed" whenever I leave the house and arm the alarm, and not just not via this rule. Normally I arm it with a remote control. I know that the rule is not running, because I am not getting the first notification "Arm alarm message received by HE". I only get the second notification when the house is alarmed, via remote control.
Here are the logs for when it last occured and NOTE that I did not press the cloud end point at all today (yet the logs are waiting for something now, as if I did press it). Something weird is going on, since I'm not pressing the cloud end point, and I'm not recieving the other messages.
Could it be that the wait is there from the previous time the rule ran? It doesn't go away on its own, it waits. There are steps you can take to cancel the wait, but without them it will just wait for the event. You can see this on the app status page under Event Subscriptions.
That's coming in Rule 4.0. There will be Wait for Events, one of which is a new one called Elapsed Time.
In the meantime, there is a sort round about way to do it. Before the wait put in a Stop Actions for This Rule with a delay. If it's still waiting when that goes off, it would end the wait.
No, there can only be a single wait outstanding at any moment, and I don't think they survive reboots, but actually haven't checked that. Perhaps they would. Just look at the Event Subscriptions for the app in question. They do not survive the rule/trigger running again.
