I have been trying to update the firmware on my Inovelli dimmer red series (LZW31-SN) using the OTA driver, original and binary. It always gets stuck on (downloading firmware). I have tried this on multiple switches with the same results. I have even moved the hub to within a couple of feet from the switches. Any suggestions? Currently on C-5 Hub, Inovelli firmware beta 1.52, trying to upgrade to 1.56
1 Like
Do you have a C-7 hub? If so, you could try the built-in firmware updater app instead of the community driver (still might not work, but might). Otherwise, do the logs show anything in particular that might help? I've had pretty good luck updating the dimmers with the driver (binary since you also need to do the target 1 firmware for some updates), but the switches were sometimes problematic. In that case, using a secondary controller or just un-pairing and using that controller as primary to do the update would work--and tends to be a bit faster in my experience anyway, aside from whatever pain may be caused on the Hubitat side from having to re-pair the device. (Z-Wave PC Controller and a Z-Wave USB stick like one from Zooz, HomeSeer, Aeon, ZwaveMe, or others are popular options--Inovelli has instructions on their site.) Just something to consider if nothing else works.
Another thing that came to my mind after writing this, given where it says it's getting stuck: what URL are you using for the firmware? If it's hosted on the same up you're updating on, use port 8080 instead of the default (80 or unspecified). So http://myhubip:8080/firmwareFile instead of http://myhubip/firmwareFile.
I have a C-5 Hub
The URL I am using is from Inovelli. • https://files.inovelli.com/firmware/LZW31-SN/Beta/1.52/LZW31-SN_1.52.otz
I haven't tried a Z-Wave USB stick yet, because this has always worked for me without issue
Ah, yeah, direct URL from them should work too. I suppose you could try uploading it to File Manager on the hub to see if that works better (but be sure to add port 8080 as above). Otherwise, I'd again suggest seeing if the logs provide any clues.
Got it figured out. I had a small ( . ) in front of the URL
Should work, at 33% upload.
Thanks for taking the time to help
2 Likes
