I have a rule that has a wait for event with a 2 second delay at the beginning of a rule. I do this as a way to halt double triggers. This is a rule to set a presence device showing activity in the house. A switch turned on, motion in an area that would only be triggered by a human, etc...
Most of the time it works but since I have moved it to a different hub it has occasionally stopped on the wait and never times out. The rule sits there until another trigger occurs. You can see in the screenshot below the area circled and labeled "didn't work". It set a 2 second wait at 9:12:41 and did not start again until 10:00:20 about 45 minutes later when another trigger occurred. Earlier in the rule circled and labeled worked, you can see it wait and continue on as it should.
Maybe it's something with the rule. Its a new C7 hub that I just brought online. The rule originally was running on one of my C5s, and I never saw this. Since I moved the rule from a C5 to a C7 I rewrote the rule from scratch as it originally was a legacy rule. So this is a fairly old rule that has been working for some time. I did re-write however so maybe there is an issue, but that part is pretty straight forward. It's the very first line of the rule, wait 2 seconds to make sure there is not another trigger.
So it's on a new hub, and a new RM. Has anyone else seen anything like this?