I updated to 2.4.1.151 earlier today. One of my rules that triggers individual rules to close all of the curtains didn't work. I've no logs and wasn't sure whether the time I updated the software had clashed with something in the rule causing the failure. However I remembered something in a post regarding rules with waits that might need update or done clicking to implement a fix. Rather than wait to see if any other rule failed to run (resulting in a low WAF) I went through each rule with a wait and clicked update and done. I've an error for every rule I did that on as shown below. Any ideas?
2 Likes
Open that rule and hit Done. That should fix it.
Hi Bruce - apologies I think I threw you a red herring....
When my rule failed yesterday evening I remembered something I'd read about waits in rules while in beta and I went through and clicked Update and Done in every rule with a wait immediately without first checking the logs.... So straight after I did that when I checked the logs last night I thought that me doing this had generated the errors.
When I've checked again this morning and filtered the log level to 'error' I found that those errors, multiple pages of them, had actually started when the hub came up after the update to 2.4.1.151. Effectively I'd fixed and stopped those errors before I posted. The logs are free of further errors after 12 hours. Thanks.
2 Likes
Ugh - I thought it was fixed as I did already hit done on all of the rules with waits. This rule didn't work tonight:
and produced this different error in the logs:
Is that the same thing, do I just try 'done' again @bravenel or should I try something else? Thanks
That’s a different issue. I’ll look into it.
2 Likes
Will be fixed in next release...
4 Likes
