forum

Ok, I realized the versions didn't matter and the proper way to utilize the beta versions was to add the link below to the IDE's board manager. I was able to upgrade to 3.0.12 and burn the bootloader and with this version I'm not able to flash either chip via OTA.

My HA controller says this: zwave_error: Z-Wave error 1503 - Failed to start the update: Invalid hardware version! (ZW1503)

https://z-uno.z-wave.me/files/z-uno2/pa ... index.json

Questions:

1) Does OTA work at all on the 3.0.12?
2) Can I get this Uno back to 3.0.10?

Hi,

I can only say that OTA update with 3.0.12 is working fine without problems using Z-Way...

It doesn't help you, but looks like not a problem with Z-Uno FW, maybe...

Michael

Things did not get better with 3.0.12b and Zwave JS. With 3.0.10 at least I was having some successful runs when doing OTA, but with 3.0.12b none. I keep getting the following error message:
2024-03-21 15:55:40.541 INFO Z-WAVE: Failed to start the update: Invalid hardware version! (ZW1503) updateFirmware undefined

anyone facing the same issue?

Furthermore, there is something fishy about parameter 20. When Zuno2G starts, it is set to 218. I set it to 0 then to 1 before starting the OTA process.
If I re-read parameter 20, it is set back to 0. This behaviour wasn't there in 3.0.10.

aleconakad wrote: ↑

21 Mar 2024 17:59

Things did not get better with 3.0.12b and Zwave JS. With 3.0.10 at least I was having some successful runs when doing OTA, but with 3.0.12b none. I keep getting the following error message:
2024-03-21 15:55:40.541 INFO Z-WAVE: Failed to start the update: Invalid hardware version! (ZW1503) updateFirmware undefined

anyone facing the same issue?

Hello.
It’s hard to answer about Zwave JS. I think it’s worth asking the Zwave JS developers what this error means.

Furthermore, there is something fishy about parameter 20. When Zuno2G starts, it is set to 218. I set it to 0 then to 1 before starting the OTA process.
If I re-read parameter 20, it is set back to 0. This behaviour wasn't there in 3.0.10.

On the 7th generation, at least for now, you can ignore this parameter.