Used built-in firmware updated in C7 hardware, and got Device Firmware Updater ERROR: The device was unable to receive the requested firmware data without checksum error.
Not sure if I got the wrong part of the firmware from the file, or if it's because I have the device included in non secure mode.
Is there a way to do a checksum verification on the FW file before trying to flash it?
Any way to switch to secure inclusion without digging the device out of the back of the switch box and pushing the button?
Ok, so I probably just extracted the firmware incorrectly. Any good tips on this? I followed the instructions earlier in the thread, bit don't know how to verify without just sending it to the device.
@bcopeland thanks for the great insights in this thread. I'm trying to update some old Aeotec Nano Shutters (US version), and tried to extract the binary file myself. Nevertheless, I don't get just 1 .bin file, but 3.... which one should I use? or should I update one by one in order?
Does anyone know which binary I should use? I'm afraid to brick my devices. Also, I'm actually using the built-in firmware updater... so I was wondering if these .bin files are safe to use with that one.
Ok, I just converted them to intel hex format, as I read somewhere in this thread that updating using hex files had more validation to avoid bricking the device (I don't know if that's still true, or from an older version of the updater).
I tried upgrading to all 3 versions, but after it transfers the firmware to the device, I always get a Device Firmware Updater: ERROR: Insufficient memory error message, and the device is not upgraded.
Do you know why this is?
I'm trying to upgrade 2 Aeotec Nano Shutter (US version) from firmware 2.02 to any of those 3 versions I shared above. Both of them fail in the same way. I'm using the built-in "Device Firmware Updater" app.
Looking at the logs, I see messages like this:
FirmwareMdReport(manufacturerId:134, firmwareId:909, checksum:33533, firmwareUpgradable:false, numberOfTargets:0, maxFragmentSize:20, firmwareIds:[], hardwareVersion:null)
Can this update a device using a GBL file? Zooz sent me a GBL file instead of an OTZ file like they've done in the past. This is for a Zen77. This is what I got in the log.
EDIT: I'm using the zwaveFirmwareUpdater. Should I try zwaveBinaryUpdater?
EDIT2: After searching this thread for GBL I found that yes I should be using the binary updater, but I need to know what firmwareTarget to use and presumably, I need to get that info from Zooz.
You will need the binary updater (or the app on a C-7 hub and then you don't need this at all) for a .GBL file, which I think is how all 700-series devices (like the new Zooz ZEN7x products) provide firmware updates now.
I have used the driver version on my C-5 to update several of my Aeotec devices using .gbl files. I have also used the driver version on the C-5 to update my Zooz ZEN16 MultiRelay using .otz files.
And, I have used the app version on my C-7 to update the same devices using .otz and .gbl files.
Aeotec support have stated this when I asked for the unencrypted hex update files:
Unfortunately, it is not possible for us to provide you with unencrypted .hex or .ota files.
We offer you the possibility to update your devices with a Z-Stick or other USB Z-Wave adapter and a Windows PC.
Damn - don't want to have to unlink my Z-wave gear just to update - screws everything up. I also can't seem to be able to extract the update correctly from the .exe
In general, you stick it in whatever it takes to power it--not the Hubitat.
Then, you follow its instructions to pair it with the Hubitat (put the Hubitat in "discovery" mode, then trigger the stick's "include" mode, and include it).
Once you do that, it should be added as a secondary controller to the Hubitat.
Sorry, I've not used that stick. However, I've heard plenty of discussions about sticks--poking around with a few searches should turn some ideas up. Good luck!!