I have a basic rule that turns on the light at Sunset and turns off at 11:00 pm.
Normally, the rule runs fine. This morning the light was still on, and this is how the rule fired:
2024-05-31 11:00:00.259 PM evt: certain time , wait over --> restricted
2024-05-31 07:45:00.605 PM Wait Until Time of Day is 11:00 PM
2024-05-31 07:45:00.343 PM act: Turn on Curio Cabinet
2024-05-31 07:45:00.336 PM evt: Sunset
What is evt: certain time , wait over --> restricted?
Thanks,
Please post a screenshot of your rule. Based on the logs, it appears that rule has a Restriction option set, that prevented the light from being turned off.
1 Like
Known issue with Basic rules since 2.3.9.141
It impacts rules with no restrictions and also if the pending actions restriction is enabled.
Its a know issue since public release 2.3.9.141. Need to roll back the platform to 2.3.9.139 or earlier, or see instructions in this post:
You can roll back using the diagnostic tool:
.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.
2 Likes
Fix for this coming in next release.
7 Likes
derek1
June 4, 2024, 12:13pm
6
So in the meantime if we toggle to "Restrict only the trigger ..." will that solve? Theoretically if the trigger is restricted, the pending actions are irrelevant for 90% of my rules.