Issue on 2.2.8.133 setting Group device with Scene

After the latest update I am seeing the below error when trying to set a Group device using a Scene. This is consistent for multiple Groups (after removing one it errors on the next) and persists post reboot,

errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (com.hubitat.app.DeviceWrapper, java.lang.String, java.lang.Integer, java.lang.Integer, null) values: [Office Floor Lamp, setCT, 2700, 10, null] Possible solutions: wait(), any(), trim(), grep(), split(), next() on line 547 (appButtonHandler)

Please show the Scene in question, and next time please use a screenshot to show a log entry like this. What this error thrown by the Scene?

Also, please show the Group involved. The handling of ColorTemperature changed in this release, and this is somehow caught up in that. But, I need more information to see what's going on.

I also had issues with several scenes, they had zigbee color bulbs, a wifi color strip, two zigbee switches.
they are not activating. even when activated manually, hubitat keeps claiming "not set"
after downgrading all was well again.

I'm also seeing a similar issue with a Scene, the Scene activates an led light strip and a light switch. The led strip turns on but the light switch doesn't. I have 3 different scenes for those devices depending on the mode and they all give the same error.

Same problem with scenes here. The scenes with my kitchen lights, which are Hue white bulbs via a Hue bridge, are the ones that error. When this scene is activated, the "reading lamp," which is an RGB bulb, changes correctly, but the kitchen does not.

Here's one of the scenes:

And here's the error:

This scene, which sets the color of a strip light I use for a backlight on the TV, works just fine. Don't know if it's the difference in RGB vs white bulbs?

This line 547 bug has been found and fixed. Fix in next hotfix release coming soon...

1 Like

Still getting an error, but the color change does work.

Scene:

Error:

Did you update to 2.2.8.135?

Yes. This error was after the update. Sorry... should have been more specific.

Well that's bizarre, because that line of code was changed. The error shows an attempt to call a method with 5 parameters, but there is no such call. That was the bug.

Evidently, something went wrong with this build wrt to this change. I can reproduce the error.

2 Likes

Technology. Gotta love it. :wink:

Updated to 2.2.8.136 and no more errors. Thanks!

2 Likes