There was a bug in Rule 5.1 involving triggers that use Hub Variables. When you upgrade to 2.3.0, first thing open the parent app Rule Machine and hit Done. This will update those rules. Failure to do this will result in those triggers becoming hidden in the rule, and to no longer work.
I have a rule that since the upgrade is not triggering. It is not using variables in trigger, only device custom attributes, but it is using variables within the rule. I have done the action to open parent app and clicking done. If I run actions, they are logged/executed, it just never triggers.
It is raising an exception when I run actions or edit the rule.
2021-11-27 07:44:10.158 [error]groovy.lang.MissingMethodException: No signature of method: static com.hubitat.hub.dao.GlobalVarDao2.addInUseGlobalVar() is applicable for argument types: (java.lang.Boolean, java.lang.Long) values: [true, 624]
Possible solutions: addInUseGlobalVar(java.lang.String, java.lang.Long) on line 7001 (method updated)
Can you assist?
I will investigate. It would help if you could post a screenshot of the rule here.
One more favor to ask: Please turn on Action logging, and run the actions. That way I can see which action is throwing the error. Post a screenshot of the logs.
Hi, I just tried and it didn't throw the exception when i ran the actions, only logged the action execution.
The exception is thrown when I press Done in the rule. Also, the rule is never triggered even as the trigger conditions are met.
Also, I upgraded to 126.96.36.199 earlier today.
Below the Action log and the exception from pressing Done.
** EXCEPTION FROM PRESSING DONE **
2021-11-27 22:22:01.888 errorgroovy.lang.MissingMethodException: No signature of method: static com.hubitat.hub.dao.GlobalVarDao2.addInUseGlobalVar() is applicable for argument types: (java.lang.Boolean, java.lang.Long) values: [true, 624] Possible solutions: addInUseGlobalVar(java.lang.String, java.lang.Long) on line 7011 (method updated)
Thanks. I'll dig into it.
There is another thing I need to see: I need the Settings portion of the App Status page (a screenshot, please). The App Status page is obtained using the gear icon at the top of the app setup page. Can you confirm that you are using these variables: current-time (DateTime), next-adjustment (DateTime), and last-adjustment-level(Number). Is that correct?
Correct these are local rule variables.
Quite a big table with settings, apologies for the many screenshots.
I also tried to clone the rule, and got same exception during cloning (but cloning completed) and then when pressing Done in the clone, as for the original rule.
Thanks. I know what the problem is. Fix will be in next release.
Thanks, looking forward to it!
Hi do you know when the next release is planned? In the meantime can I change something in the rule to get it to work around the issue? Thanks
Just upgraded, issue solved, thanks a lot!