Hi, i have this rule which keeps sticking at the wait for events. its almost like it doesnt see the door sensor closing. See top line of logs, when my DOOR SENSOR FRONT DOOR closes and remains this way for 0:05:06, (the KITCHEN OPEN UPSTAIRS and V AWAY HEATING SWITCH UPSTAIRS contact sensors have remained closed all day.) the rule doesnt move on. Please note i added the 1 second waits in for another reason so ignore them as i'll strip them out. Any ideas please, would a wait for expression be more suitable? Appreciated in advance...Stu
That depends: do you want to wait for an event (which actually requires an event, generelly a new/changed state), or do you just want to wait for something to be/become true, possibly for some amount of time? The latter will include times when the condition is already true, as it's looking at the state, not waiting for an event (though if the state is currently false, an event will indeed be what changes that).
As for the rest of your rule, I'm not sure. Are you saying all of the "Wait for events" events happened and the rule still didn't move on? I don't see that from the logs, so if the above is the explanation, that could do it.
Thanks Bert. So basically 2 of my contacts have been closed all day, upon my front door contact closing and remaining this way for 00:05:06 i would expect this line to become true and for the rule to move on. However, when the front door closes for the required period. The rule doesn't move on "sometimes".
I have this same rule set up for 4 other rooms with no issues (different door contacts), however it is hit and miss in this case.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.





