Z-Wave Future....

[rafale77]

Yeah there where I switched to the command line tool. Do you already have devices on that stick? @poltoS says it is because the upgrade process is interrupted by RF signals. I thought it was due to some EEPROM start location issues but I did find it painful in recent versions to upgrade and had to retry dozens of times to get it through. It looks like the upload of the firmware started but gets interrupted by something.

[parkerc]

@rafale77 said in UZB/RaZberry Firmwares - Update:

Do you already have devices on that stick?

No, currently it’s blank, I reset it before I started down the whole upgrade path. What it is near is loads of other HA devices, 2 x Veras (a 3 and a Plus) and there’s also a hue hub and numerous other things .

Could that have an effect ?

[rafale77]

Hmm possibly. But I don't know for sure. The recommendation was even to temporarily change region so as to prevent any noise from interrupting the upgrade process. I don't know why they don't have a better way to not be impacted by the RF signals during the upgrade on these newer firmwares.

[hunnypuppy]

A kinda basic question, I'm currently on UZB1 firmware 5.34
What is the advantage of going through this process to get to 5.39

The only I notice is that it seems to have something called Zniffer feature to trap packets. What exactly does this enable? I can see packets in Zniffer using Z-Way (when using as a secondary controller but only between the secondary controller and device, not between devices and primary controller) and Zniffer ART seems to indicate that it needs different hardware. So where can this Zniffer additional 5.39 feature be used or is there any other advantage to upgrading the firmware?

[hunnypuppy]

I'll answer my own question for others benefit. I was able to successfully upgrade UZB from firmware 5.34 to 5.39 using Z-Way server and the all token to first downgrade and then upgrade following this path.

5.34 → 5.33 → 5.27 → 5.36 → 5.39

My bootloader version is 40196 and I did not upgrade the bootloader along the way, I started and ended with the same bootloader.

I did a ResetAPI followed by a ControllerReset after each firmware downgrade/upgrade to ensure that I had a clean start. I also disabled all zwave device (unplugged/removed batteries) to ensure that any stray packets didn't interfere with the process. Be sure to backup your configuration/network before updating the firmware.

After upgrading to 5.39 I'm now able to use the promiscuous mode in Z-Way zniffer to capture packets on the network (although it misses some packets)

I did get a note from support, so those with firmware under 5.24 may want to pay heed to this.

there is a batch of sticks with "dead-end" firmware and a slightly modified board topology. But given the fact that such sticks are usually impossible to upgrade above version 5.24, then you most likely have a good stick for which this operation will be possible.