[RELEASE] Z-Wave Firmware Updater

mac0s9user · August 23, 2020, 3:10am

And thanks for the welcome @672southmain. Sorry I missed that snippet of code. Sleep training my kid which means I get very little

Civilanchor · August 25, 2020, 9:06pm

So for the DZ6HD's do we use the original? I could never get that to work with the original haha, was hoping this updated version would be better

672southmain · August 25, 2020, 9:08pm

I don’t have that device, so I can’t answer. What type of update file (file extension type?) do you have? That is the determining factor.

Civilanchor · August 25, 2020, 9:13pm

I Was using Leviton-DZ6HD_01_20.hex from https://raw.githubusercontent.com/djdizzyd/hubitat/master/Drivers/Z-Wave-Firmware-Updater/Leviton-DZ6HD_01_20.hex, but looks like that's gone now actually

672southmain · August 25, 2020, 9:19pm

If you can find a copy of that file, .hex work best on the original (first version).

Civilanchor · August 25, 2020, 9:21pm

Though not in the case of this particular DZ6HD I guess, but thanks

byarnell05 · August 26, 2020, 6:19pm

Anyone else still having issues with the "please wake up your sleepy device" error? I've been trying to update an Inovelli lzw-31-sn and a lzw42 and both of them fail at the same error. I tried to capture logs and what not when I tried updating the lzw42 but this is all I get in the logs.

dev:2 2020-08-26 11:08:03.244 am debuglocked by:

On the device page the current states are as follows:
Current States
firmwareUpdateProgress : Please wake up your sleepy device
lockedBy : None
currentFirmwareVersion : null
firmwareUploadPercent : null
firmwareTarget : null
manufacturerId : null

I have to be doing something wrong because it looks like its doing nothing. I have tried loading the file locally and using http://192.xxx.yyy.zzz:8080/local/LZW42_2_30.hex and I've tried using the direct link from inovelli http://files.inovelli.com/firmware/LZW42/Beta/LZW42_2.30.hex both fail with the same output.

I read that it may be related to being connected directly to the hub and because this is a brand new C7 device I removed all devices and only had 1 device connected and the hub was only 3-4 feet away and it still failed with the same issue.

Any help would be greatly appreciated.

672southmain · August 26, 2020, 6:45pm

Which version of the updater are you using? See my post above:

byarnell05 · August 26, 2020, 7:03pm

I have used both versions of the updater and they both fail the same.

672southmain · August 26, 2020, 7:05pm

Ok, is the device paired securely? I don’t believe that the Firmware Updater works with a securely-paired device.

byarnell05 · August 26, 2020, 8:09pm

I included/excluded the switch multiple times changing the security settings and no matter what I tried it always came up as "none" and it always failed update. The bulb on the other hand always pairs as S0 and like the switch, always fails.

byarnell05 · August 27, 2020, 6:04pm

When checking the security setting of the devices are we wanting them to state "none" or something else?

eaton.blumenstein · August 27, 2020, 6:48pm

So I am getting an error..

java.lang.NullPointerException: Cannot invoke method and() on null object on line 461 (firmwareStore)

I saw that there was some issues with Dropbox.. but I am downloading it right from Index of /firmware and no luck. I am also using a local HTTP server and it gives that error and then the " Padding hex bytes...

edit: I even have the old version of the updater and the original file that I had that was a version behind. but no luck. this is the same switch's that I had before (i never got to the last one)

Any idea?

eaton.blumenstein · August 27, 2020, 8:05pm

ended up using this version

github.com

djdizzyd/hubitat/blob/master/Drivers/Z-Wave-Firmware-Updater/zwaveBinaryUpdater.groovy

// v1.00
import groovy.transform.Field

metadata {
    definition (name: "Z-Wave Firmware Updater",namespace: "djdizzyd", author: "Bryan Copeland") {
        attribute "currentFirmwareVersion", "string"
        attribute "firmwareUpdateProgress", "string"
        attribute "firmwareUploadPercent", "string"
        attribute "manufacturerId", "string"
        attribute "firmwareId", "string"
        attribute "firmwareTarget", "number"
        attribute "firmwareFragmentSize", "number"
        attribute "lockedBy", "string"

        command "clearLock"
        command "getVersionReport"
        command "abortProcess"
        command "updateFirmware", [[name:"binaryFirmwareUrl", type: "STRING", description:"Firmware URL"],[name:"firmwareTarget", type: "ENUM", description: "Firmware Target", constraints: ["0","1","2","3","4","5"]]]
    }
    preferences {

This file has been truncated. show original

that seemed to work for me. humm.. is that the most recent version. not sure if I got an older version from the top?

672southmain · August 27, 2020, 8:25pm

See my earlier post that explains the difference. Yes, you got the “new” version, which handles some types of firmware files that the “older” one cannot. However, the “new” version has some bugs with some types of files that the “older” one handles correctly. Again, see my earlier post above:

byarnell05 · August 28, 2020, 12:28am

Well I "figured out" my issue I was having. I'm not sure if I screwed something up when I upgraded my hub to the newest firmware 2.2.3.135 but I ended up restoring back to 2.2.3.119 and updating firmware on my lzw31-sn worked flawlessly. I wasn't aware of the 2 part update when you update to .135 so I didn't do the second part of the update until a little while after doing the initial hub update, maybe that is why I was having issues? I will have to test that once i'm ready to upgrade back to .135.

thejessman · August 28, 2020, 6:11pm

I've updated most of my switches to new firmware, but several I am trying to do and it keeps coming back with the "wake your sleeps device" issue. How can I resolve this? I've tried doing the air gap, but it won't do that way even. Any other ways to update the firmware on mine? They are Inovelli LZW-31SN.

mraz.camren · August 28, 2020, 6:19pm

Which Hubitat hub are you using? Is the switch connected via S2 authentication? Have you tried the below process?

thejessman · August 28, 2020, 6:37pm

I'm using the C7. The particular switch is NOT using S2. I've tried the air gap multiple times. Even tried another suggestion of throwing the breaker instead of air gapping.

thejessman · August 28, 2020, 6:50pm

I just tried pulling a version report on other switches and it won't come back with a version on them either. What's going on with my hub? It sounds like maybe it's a problem with my hub since other switches aren't pulling versions either.