Logs say "wait over --> restricted" after elapsed time

[user2827]

Hello, I am trying to make a simple rule where a button is pressed, an outlet is activated, then after X elapsed time the outlet turns off:

When I run the rule, the outlet does get activated, but then does not turn off after elapsed time. The logs seem to understand what should happen, but when it comes time to turn off the outlet, it says that it is restricted:

I don't have any restrictions, nor any other rules attached to this outlet:

Any idea what "wait over --> restricted" means? Why it would be restricted? And how to unrestrict it?

My hub version is:

Thanks.

[ogiewon]

I think this is a known issue. I think the fix is coming in the next release.

Evt: certain time , wait over --> restricted

Fix for this coming in next release.

[user2827]

I didn't realize this was a major bug. Many/most of my automations depend on elapsed time. Any idea when the next release is scheduled for? Is there a workaround? Shouldn't there be an emergency patch before release?

[ogiewon]

@user2827

Is there a workaround?

Please see the following

2.3.9.142 updated stopped some of my automations

.143 did not fix it, I think @bravenel is still working on it. To fix it for now, you can either change your restriction setting to be for the trigger only. Or you can roll back to the prior platform using the Diagnostic Tool. In the restriction settings you want it like this (just the part I have boxed out in red) [image] Unfortunately the bug fix for Basic Rules in .141 seems to have broken all pending actions if that setting is the way you have it now.

[user4980]

This is happening for me too. On a rule that has no restrictions.

app:72024-06-05 10:20:17.396 AMinfoevt: Wait time is up: 30 minutes , wait over --> restricted
app:72024-06-05 09:50:17.360 AMinfoact: Wait 30 minutes
app:72024-06-05 09:50:17.298 AMinfoevt: Toilet Room Fan switch on
app:72024-06-04 01:02:17.362 PMinfoevt: Wait time is up: 30 minutes , wait over --> restricted

[bobbyD]

@user4980

On a rule that has no restrictions.

This is a known issue. The fix has been released in the beta channel. If everything goes well, the update will be made public shortly. If you don't want to wait for the public release, I can enable the beta update on your hub to fix this issue, now.

[user2827]

Latest update 2.3.9.147 fixes it! Thank you.