I updated yesterday to the latest version (2.3.1.128) yesterday afternoon. Last night, one evening routine didn't work, but I figured there was some random issue/one time thing. After the evening miss, Night modes didn't activate causing motion lighting in the middle of the night. Now, Morning and Day modes aren't activating and rules are throwing errors. It seems to be mostly limited to rules that contain a private boolean written into it somewhere (whether it sets one or gets set by another rule). Everything was working great up to yesterday afternoon. Has anyone else experienced this? Any recommended fixes?
This one (below) actually ran correctly and then threw the error. The others have just thrown errors and not worked.
The one below was a test I set up to set a private boolean true from another test rule. It threw an error as well, so the issue can be re-created.
I just want to confirm, are these errors all coming from instances of rule machine? From the log snippets and your reference to private booleans, it sounds like yes?
“Routine” is a descriptive term for an automation, but unlike on the smartthings platform, Hubitat has no feature called routines.
That's correct. They are all rule machine rules.
The routine label is from me. I made rules based on our routines in the morning, evening, etc. Didn't mean to label the rules as that....just thinking of our routines as they were happening this morning.
No worries, there’s many terms that can be used for automations, and Hubitat has multiple built-in apps for creating them. So it’s helpful to confirm which app appears to be the source of the errors in the log.
Tagging @bravenel, who may have some follow-up questions.
For giggles, if you click on those rules, then click DONE does the error go away?
1 Like
I had opened them earlier to see their status after they didn't run, so I wanted to say no....but....I just opened both my test rules I created (one to set the boolean of the other) and they appear to have run successfully now.
Sets the boolean of an existing rule:
Existing Rule:
The error on line 8590 is known, and fixed in the next release. It will go away if you turn off Event Logging, as it is an error thrown by the logging itself.
2 Likes
I've gone through and opened each rule, then clicked done. Hopefully that will resolve the issues. Anything else you could suggest I try, or wait and see if that works? I don't really know what happened, but there was about 16 hours where it all went crazy starting immediately after the update yesterday.
