[RELEASE] Z-Wave Firmware Updater

bjcowles · April 18, 2020, 5:16am

@EAN You are correct! Apologies

EAN · April 18, 2020, 5:18am

Thank you so much for your help!

Here is the log:

dev:10602020-04-18 12:13:35.643 am debug7A03031E0201346700002800

dev:10602020-04-18 12:13:35.626 am debugFirmware Descriptor: [wFirmWareCommonSize:32741, wFirmWareBank1Size:31688, wFirmWareBank2Size:31041, wFirmWareBank3Size:28983, manufacturerId:798, firmwareId:513, checksum:24397]

dev:10602020-04-18 12:13:35.065 am infocalculating crc...

dev:10602020-04-18 12:13:34.251 am debugOTZ Headers: [compressedLength:97528, crc16compressed:20820, unCompressedCrc16:10603, scramblingKey:e0fff422903c6e0ff121ed0903cb, firmwareDescriptorChecksum:24397, fastLzLevel:1]

dev:10602020-04-18 12:13:34.225 am infogot otz compressed image reading compression header

dev:10602020-04-18 12:13:34.222 am infofirmware total bytes: 97555

dev:10602020-04-18 12:13:34.219 am infoSorted all the bytes. cleaning up some memory...

dev:10602020-04-18 12:13:34.213 am debugParser: EOF

dev:10602020-04-18 12:13:30.341 am debugParser: 16 bit shift: 0x1

dev:10602020-04-18 12:13:22.332 am debugskip: MeterReport(scale: 0, rateType: 1, scale2: 0, deltaTime: 69, previousMeterValue: [0, 0, 0, 10], meterType: 1, precision: 3, size: 4, meterValue: [0, 0, 0, 12])

dev:10602020-04-18 12:13:22.180 am debugparse:zw device: 22, command: 3202, payload: 21 64 00 00 00 0C 00 45 00 00 00 0A , isMulticast: false

dev:10602020-04-18 12:13:19.054 am debugParser: 16 bit shift: 0x0

dev:10602020-04-18 12:13:19.043 am debugpacking all the bytes...

dev:10602020-04-18 12:13:17.265 am debugfirmwareMdReport: checksum 63878 firmwareId: 513 manufacturerId: 798 maxFragmentSize: null firmwareTargets: 0

dev:10602020-04-18 12:13:17.259 am debugFirmwareMDReport: FirmwareMdReport(manufacturerId:798, firmwareId:513, checksum:63878, firmwareUpgradable:false, numberOfTargets:0, maxFragmentSize:null, firmwareIds:[])

dev:10602020-04-18 12:13:16.963 am debugparse:zw device: 22, command: 7A02, payload: 03 1E 02 01 F9 86 FF 00 00 28 , isMulticast: false

dev:10602020-04-18 12:13:16.623 am infoVersionReport- applicationVersion:1.9

dev:10602020-04-18 12:13:16.612 am infoVersionReport- zWaveProtocolVersion:6.4

dev:10602020-04-18 12:13:16.515 am debugparse:zw device: 22, command: 8612, payload: 03 06 04 01 09 01 00 , isMulticast: false

dev:10602020-04-18 12:13:16.229 am infoFirmwareUpdateMd version:4

dev:10602020-04-18 12:13:16.142 am debugparse:zw device: 22, command: 8614, payload: 7A 04 , isMulticast: false

bcopeland · April 18, 2020, 5:18am

and nothing after that?

EAN · April 18, 2020, 5:20am

it stops there until i pull the air gap.

Then i start getting this (but the firmwareUpdateProgress doesnt change) :

dev:10602020-04-18 12:19:37.647 am debugskip: MeterReport(scale: 0, rateType: 1, scale2: 0, deltaTime: 65535, previousMeterValue: [0, 0, 0, 12], meterType: 1, precision: 3, size: 4, meterValue: [0, 0, 0, 0])

dev:10602020-04-18 12:19:37.640 am debugparse:zw device: 22, command: 3202, payload: 21 64 00 00 00 00 FF FF 00 00 00 0C , isMulticast: false

dev:10602020-04-18 12:19:06.362 am debugskip: MeterReport(scale: 2, rateType: 1, scale2: 0, deltaTime: 0, previousMeterValue: [], meterType: 1, precision: 1, size: 4, meterValue: [0, 0, 3, 105])

dev:10602020-04-18 12:19:06.355 am debugparse:zw device: 22, command: 3202, payload: 21 34 00 00 03 69 00 00 , isMulticast: false

dev:10602020-04-18 12:19:04.474 am debugskip: MeterReport(scale: 2, rateType: 1, scale2: 0, deltaTime: 0, previousMeterValue: [], meterType: 1, precision: 1, size: 4, meterValue: [0, 0, 2, 230])

dev:10602020-04-18 12:19:04.353 am debugparse:zw device: 22, command: 3202, payload: 21 34 00 00 02 E6 00 00 , isMulticast: false

dev:10602020-04-18 12:19:03.331 am debugskip: SwitchBinaryReport(value:255, targetValue:0, duration:0)

dev:10602020-04-18 12:19:03.231 am debugparse:zw device: 22, command: 2503, payload: FF , isMulticast: false

dev:10602020-04-18 12:13:35.643 am debug7A03031E0201346700002800

bcopeland · April 18, 2020, 5:21am

Ok... sounds like a firmware bug with regards to firmware activation .. But I think I can work around that..

Hang on

bcopeland · April 18, 2020, 5:24am

Try this version.. I have disabled the firmware pre-activation..

github.com

djdizzyd/hubitat/blob/master/Drivers/Z-Wave-Firmware-Updater/zwaveFirmwareUpdater-badActivationFirmware.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:"firmwareUrl", type: "STRING", description:"Firmware URL"]]
    }
    preferences {

This file has been truncated. show original

Just for this issue.. I don't recommend this for devices that respond correctly.. But if it works.. I can add a workaround with a timeout to re-send without firmware pre-activation ..

EAN · April 18, 2020, 5:31am

No change, still stuck with firmwareUpdateProgress : Please wake up your sleepy device

bcopeland · April 18, 2020, 5:32am

Very strange.. I'm a bit delirious at the moment from lack of sleep.. I'll jump back on this firs thing in the morning.. It's possible I'm missing something obvious..

EAN · April 18, 2020, 5:33am

Thanks for all your help!!

bcopeland · April 18, 2020, 5:34am

Anytime.. And if I can't figure it out .. I will poke the inovelli guys for input..

techbill · April 18, 2020, 6:04am

Man. I just updated zen16 few hours ago with zwave stick. I wished I had check the forum earlier today lol!!!

At least now I know I can update firmware from HE in future.

Thanks for making it possible!

rjwgnr27_hub · April 18, 2020, 6:29am

I had the same the same behavior as EAN when I tried updating my Red Switch (LZW30-SN).

tldr; I rebooted my hub.

Long version:

First though, a big thank you! A much more appealing process than the exclusion, third party stick and tool, then re-add approach originally described at the Inovelli site.

A little side note; when I first looked at my HE page this evening, I had a notification, saying (to the effect): "zigbee network is offline". I went to settings and toggled the zigbee radio. After that, tried a few zigbee switches, and all seemed fine.

Moving on, I went to the community, and saw the updater was released. Got the '30SN firmware, and followed the update instructions. Got to the "wake sleepy device" state. At that point the switch was non-responsive. I had to pull the airgap to recover it. Repeated the process and got the same results. At that point, I noticed hub responses were slow for other things, so I rebooted the hub, and retried the update. That time, it worked.

Unfortunately, I did not grab logs of the failures. Since the hub was acting squirrely, I wonder if there was a resource (memory) issue; possibly the updater (or HE) did not handle an out-of-memory condition?

Anyway, took several tries, but got it working.

The only other thing I noticed was at the end, the progress went to "Complete device is flashing". At that point the switch started blinking blue for a bit, then went to its indicator colors. Pushed the paddles, and the switch was responding. I don't know if the "Complete device is flashing" is the expected final status, or if the driver expected to detect flashing complete, and clear that last message.

The firmware version still showed the pre-update version, until I clicked the "Get Version", at which point it showed the expected 1.16.

bfara83 · April 18, 2020, 10:54am

@bcopeland
Do you mind extracting the hex for the US version of the Aeotec Range Extender 6 (ZW117). I couldn't figure out how to do it, the Exe doesn't show any files using an Exe extractor.

bcopeland · April 18, 2020, 11:06am

For most devices yes.. Some have one more final message..

bcopeland · April 18, 2020, 11:15am

Not a problem.. Give me a second.. Need both eyes open

bcopeland · April 18, 2020, 11:29am

@bfara83

https://raw.githubusercontent.com/djdizzyd/hubitat/master/Drivers/Z-Wave-Firmware-Updater/Aeotec-ZW100-MultiSensor-6-US-V1.13.hex

Let me know when you have it .. Aeotec's legal department won't be impressed

bfara83 · April 18, 2020, 11:33am

I really appreciate the post but I needed the hex for the US version of the Range Extender 6 (ZW117) instead of the hex for the ZW100 MultiSensor 6.

bcopeland · April 18, 2020, 11:34am

Wow.. my coffee really didn't kick in.. hang on ..

bcopeland · April 18, 2020, 11:52am

@bfara83

https://raw.githubusercontent.com/djdizzyd/hubitat/master/Drivers/Z-Wave-Firmware-Updater/Aeotec-ZW117_RangeExtender_Gen6_S0_US_A_V1_05.hex

dj13990 · April 18, 2020, 11:55am

I'm having the exact same issue with the switches. I have 2 of them and both are giving me the same issue as @EAN is stating. Strang as my 1 dImmer switch updated without any issue at all.