maxq10
November 18, 2020, 10:36am
1
I have several rules to turn lights off or change their color(s) by using the WAIT feature. Woke up this morning to find all of my lights still on that should have been turned off overnight. These have been working great for months and months, until I updated to 2.2.4 yesterday. Error in logs at the time they should have been turned off looks like this:
Anyone know what's going on here?
maxq10
November 18, 2020, 12:34pm
2
Here is an example of one of my rules that failed:
Very simple. The lights turned on properly, but when the mode changed to Night, I see the error above in my logs when they should have turned off.
maxq10
November 18, 2020, 12:54pm
3
And yes, Mode Manager seems to be working fine - modes are being changed correctly at their proper times.
bravenel:
What error? Please post.
See post 1, get out your microscope.
I have several rules to turn lights off or change their color(s) by using the WAIT feature. Woke up this morning to find all of my lights still on that should have been turned off overnight. These have been working great for months and months, until I updated to 2.2.4 yesterday. Error in logs at the time they should have been turned off looks like this:
[rm-error2]
Anyone know what's going on here?
1 Like
maxq10
November 18, 2020, 3:40pm
7
It's in my first post, a screen shot. Sorry - I have a large monitor. Here is the text of the error(s):
groovy.lang.MissingMethodException: No signature of method: ruleApp40.unsubscribe() is applicable for argument types: (com.hubitat.hub.domain.Location, java.lang.String, java.lang.String) values: [Home, mode, allHandlerW]
Possible solutions: subscribe(java.lang.Object, java.lang.String, java.lang.String), subscribe(java.lang.Object, java.lang.String, groovy.lang.MetaMethod), subscribe(java.lang.Object, java.lang.String, java.lang.String, java.util.Map), subscribe(java.lang.Object, java.lang.String, groovy.lang.MetaMethod, java.util.Map) on line 5140 (allHandlerW)
maxq10
November 18, 2020, 3:42pm
8
By the way, this was happening on 2.2.4.139. I just noticed that 2.2.4.141 is available. I'm updating as we speak.
Thanks, I did not see that it was an error message before. I know what's wrong, and will get a fix going...
Fix will be in next hot fix release... probably today.
5 Likes