forum

It is a head scratcher...

the controller information shows:
ZWaveChip: ZW0500 (13.12.2018)
APIVersion: 05.23 (13.12.2018)
APIVersionMajor: 5 (13.12.2018)
APIVersionMinor: 23 (13.12.2018)
manufacturerId: 277 (13.12.2018)
vendor: Z-Wave.Me (13.12.2018)
manufacturerProductType: 1024 (13.12.2018)
manufacturerProductId: 1 (13.12.2018)
bootloaderCRC: 29304 (13.12.2018)
firmwareCRC: 52559 (13.12.2018)


But the url link shows

{"data":[{"id":"139","baseid":"","enabled":"enabled","type":"bootloader","file":"bin","vendorID":"277","bootloaderCRC":null,"appVersionMajor":"5","appVersionMinor":"23","targetBootloaderCRC":"40196","targetAppVersionMajor":null,"targetAppVersionMinor":null,"fileURL":"UPD_bootloader_UZB500_from__05_17_to_9D04.bin","released":"2017-07-05","comment":"Update bootloader for 5.23 to 40196","position":"1","version":"5.23"}]}

Did anyone find the solution to this? I'm trying to update from 5.25 to the the latest version (using the v3.0.0 software on Ubuntu) - according to the firmware update screen it says update bootloader from 5.25 to 40196 but then when I click on Upgrade Bootloader it gives me an error

I finally figured it out, use Ubuntu 16.04 and not 18.10 since z-way-server requires CURL3 (18.10 ships with CURL4). There was also a step to do a to allow z-way-server access to the device after EACH firmware update.

I have this exact problem. I have tried using Ubuntu made sure it worked with Curl3.

I even tried with the Razberry Pi image. However it fails everytime.

I have 05.27 and it needs to install 40196 bootloader but it fails with same error as rafale77.

The download url is the same: UPD_bootloader_UZB500_from__05_17_to_9D04.bin

I also made sure of chmoding the device.

I get the error "Unable to update data. /ZWave.zway/ZMEBootloaderUpgrade" and the log shows failed checksum.

Anyone has a solution?

We are checking it. Looks a bug on our side

Still fighting this. I PMd you again. Please let me know if you find something.
I tried again with the permission changed on ubuntu and also with 3.0.4beta on windows. and manually uploading the downloaded file. Same result as reported above: checksum error.

Also curious why so many different firmware versions are forcing the same boot loader upgrade?
we now how report of 5.23, 5.25 and 5.27.
Why can I not upgrade to 5.27 with my current bootloader then?

Still the same log output

[2020-02-10 22:32:04.945] [zway] Adding job: Start reflashing bootloader of Z-Wave.Me firmware for 5th generation Z-Wave chip
[2020-02-10 22:32:04.963] [D] [zway] SENDING: ( 01 04 00 F4 06 09 )
[2020-02-10 22:32:04.964] [D] [zway] RECEIVED ACK
[2020-02-10 22:32:06.189] [D] [zway] RECEIVED: ( 01 04 01 F4 01 0F )
[2020-02-10 22:32:06.189] [D] [zway] SENT ACK
[2020-02-10 22:32:06.189] [zway] Job 0xf4 (Start reflashing bootloader of Z-Wave.Me firmware for 5th generation Z-Wave chip): Wrong checksum
[2020-02-10 22:32:06.189] [D] [zway] Job 0xf4 (Start reflashing bootloader of Z-Wave.Me firmware for 5th generation Z-Wave chip): fail
[2020-02-10 22:32:06.189] [zway] Removing job: Start reflashing bootloader of Z-Wave.Me firmware for 5th generation Z-Wave chip
[2020-02-10 22:32:11.581] [D] [zway] Job 0x3a: deleted from queue
[2020-02-10 22:32:11.801] [D] [zway] Job 0x3b: deleted from queue

Update: I used the UZB updater from here: https://z-wave.me/support/uzbrazberry-firmwares/
And managed to finally update my firmware to 5.36.

What is odd is that there is no release note for 5.36 but there is one for 5.37 which is not available from the map?

I use Z-way beta 3.0.4 for Windows for updating my firmware. I did some firmware and bootloader updates. I came to SDK 6.51.09 (FW 5.07). Now it says it is the newest firmware, but I see there is far more recent firmware. I think this has to do with the same issue as this topic. Should I manually upload the firmware using the button, or should I remain on this version?