so if any of the garage doors or mudroom door opens/closes this rule starts.
What I want to do , is keep the lights on inside the garage if the garage door is kept open., or for 15 min if the mudroom door is opened (and then closed)
if the garage tilt sensors show "open" I want to lights to stay on until every door is closed, if while the garage doors are kept open, I want to mudroom door to not interfear with the lights, and for them to stay on.
I think this rule is working, but its been a bit "wonky" like sometimes the lights will just turn off when I walk into the garage for a min or so.
possibly, perhaps I am over thinking it, I am going in and out of the mudroom and that trips it up, perhaps I never thought of the wait for condition..
question is, when I go in and out of the mudroom, does this rule start all over. I guess it would not matter if it was waiting for the ultimate condition of the doors all being closed?
I like dylan.c's recommendation. The only thing I'd suggest is to make the Trigger ANY opened. The first Wait is already subscribe to ALL contact sensors closed so triggering on the door closing is redundant and you'll get an additional triggering of the rule. If you go with Trigger ANY opened then Wait for expression or Wait for event will work. If you leave it as ANY changed then id suggest Wait for expression to handle the double subscription better.
sorry, my confusion here is the terminology that you guys are showing me, does not match exactly to what Rule Machine lets me select? I am not sure how do I set "elapsed time"
of the two shown above, I am not sure what one is the correct one, and also, and I supposed to make a "Timeout" or just a next line that is like this?
You could add a 15 minute duration to the Wait for Expression (not timeout) and get the same result in one action as the suggested Wait for Expression and Wait for Event together.
Note that duration defines how long the expression needs to be met or true before moving to the next action. Timeout defines how long for the Wait remains in the false state before moving to the next action.
For example: Wait for Expression: Tile East contact closed --> duration: 0:15:00
The contact must remained closed for 15 minutes for this action to be met and move to the next action
Wait for Expression: Tile East contact closed --> timeout: 0:15:00
The action will be met and move to the next action when the contact is closed or it's been waiting 15 minutes for the contact to be closed.
Likely different names for the same thing... I'm still running 2.3.4 and mine says "Wait for Conditions." Your "Wait for Expression" should be the same.