Rule Machine - rule stops after wait for event with timeout

[Alan_F]

@bravenel

Sorry this is split across two threads, but I thought I'd follow up back here on the thread I originally started:

This happened again with my alternate syntax as I posted on the other thread:

@Alan_F

After both 'wait for event' and 'wait for expression' had failures, I tried this, using 'time since event exceeds' instead of timeout:

I haven't had a failure with this syntax yet, but since it was intermittent I can't be sure that this solved it. (My rule doesn't use a private boolean, but does use a required expression)

These may all be unrelated issues, but it seems odd that several people are having intermittent failures when using 'Wait for' actions.

So now that syntax has failed also. I just had back-to-back success and failure of the rule. Here are the logs. If there is anything else I can provide other than the logs, let me know.

I grabbed the screen shot starting with the required expression going true at 13:18:37.

• At 13:27:03.347 the rule triggers. You can see the front door opened just before that
• At 13:27:03.589 it begins a wait for the front door to close or for 5 minutes to pass since the door opened
• At 13:28:16.383 the front door closes (logged by the device)
• At 13:28:16.450 the rule logs "Wait Event: Front Door contact closed"
• the rule then finishes its actions

Success!

THEN

• At 13:31:12.493 the rule triggers
• At 13:31:12.722 it begins the wait for event or time since event
• At 13:34:52.647 the front door closed (logged by the device)
• Nothing was logged by the rule or device since that time. The rule should have logged exactly what it did the first time.

FAILURE!

This is frustrating.