I have a rule that I want to trigger either at a certain time or when a presence sensor remains departed for 15 minutes. This used to work consistently but I think in the last 2.3.x release or two (I'm on .139 currently) it broke. Now it seems to be treating this as an AND vs. an OR. When I got up this morning and walked downstairs at 7:42 I noticed they weren't open and opened about a minute later. They should've opened at 7:30am. @bravenel - is there something wrong in this rule or did behavior change?
You have two triggers so it triggered twice.
Except that it didn’t actually open at 7:30. The open action wasn’t triggered until 7:43. You can see this in the log - the only action line is 7:43
Oh, I see. That looks like a bug. I will investigate it.
2 Likes
I did a bit of testing and the combo that seems to make this fail is if the presence trigger fires and waits before the time trigger. So in my case, we depart and wait 15 minutes and then sometime prior to the 15 minutes elapsing, 7:30am rolls around but the rule is still waiting for the 15 minutes to elapse and so it does nothing.
This seems sort of reasonable but I think it used to fire a second time and ignore the wait? I'd certainly prefer that behavior but I don't know if the new behavior is WAI or not; if it is, I imagine I can work around it with a single rule that is fired by two different rules with a single trigger per.
I was able to reproduce this using the following test rule and the logs follow:
I'm looking into this...
Thanks Bruce. If you need any other information please let me know.
