Unable to add device driver for Inovelli RGBW bulb LZW42

Trying to add a device driver from here. Any help to resolve this please

https://raw.githubusercontent.com/InovelliUSA/Hubitat/master/Drivers/inovelli-bulb-multi-color-lzw42.src/inovelli-bulb-multi-color-lzw42.groovy

However I am getting this error.
"unable to resolve class hubitat.zwave.commands.versionv2.VersionReport @ line 455, column 17."

At line 455 the code is:
void zwaveEvent(hubitat.zwave.commands.versionv2.VersionReport cmd) {

@ericm

What hub firmware are you on (Settings > Hub Details)? The current version is 2.1.9. I tried the above code and it worked for me.

A while back, Hubitat bumped up the supported command class versions on some Z-Wave command classes. I can't remember if this (VersionReport) was one of them, but if so--and if you're on an old hub firmware version--it would explain the problem. If you are and want to keep that hub firmware for some reason, there are some minor edits you may be able to do to the code (force it down to a lower command class version) if my guess is correct and if the code (or your needs) doesn't specifically need anything from the specified version.

4 Likes

How old is your hubitat firmware?

I can tell you right now ... none of my drivers will work on your version of hubitat.. time to update dude

I am running 2.1.7

I was running v2.1.9 but the hub got locked up and when I tried rebooting it got totally hung up during the reboot at 10% initialization. The way I got up and functioning again was to downgrade to 2.1.17 and restore an old backup. I can attempt to upgrade again and see if it stays stable.

1 Like

That's definitely the issue here--release 2.1.8 is the one I'm thinking of that made these changes (early January...seems like longer ago than that!).

If you want to use this driver or update your hub, my suggestion would be: download a local backup if your hub just in case if you haven't recently (Settings > Backup and Restore; this won't include the firmware but would be good to have regardless), then try the update process again. You should be able to downgrade again if it fails, though in that case I'd also recommend contacting Support--I'm sure they'd be interested in figuring out the cause. If you want to stay on 2.1.7, then a cursory glance at the driver reveals a couple things that might not work for you (firmware version report, possibly association reports--neither of which you would necessarily need), but Bryan could probably say more on that (he is maintaining his own version of a driver for this device now, too, but the Inovelli-provided driver you're using and linked to above has significant improvements/contributions from him).

2 Likes

Thanks for the help :blush:

It should be good .. been running that version for a long time now

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.