I have a Z-wave.me UZB stick that I have been running for 4+ years and not thought much about until recently when I wanted to do a backup of the stick. I got the z-wave.me Zway software to do a backup, and as I understand it, it contains all data to be able to replace the stick in case of failure.
However, this software is also able to update the firmware and with the old openzwave it wouldn’t be any use since it used such old zwave version but are there any benefits to update the firmware of the stick now with ZwaveJS? I run the zwavejs2mqtt addon (with mqtt disabled) and all is working good at the moment.
Can this take advantage of the newer SDK versions a firmware update would bring? I currently am running on SDK 6.51.09 (version 5.07 on the stick)
Is there any risk of losing all the data on the stick? I have some 30+ nodes on there.
It’s probably a question better suited for the Z-Wave.me forums ( https://forum.z-wave.me/ )
but with that said, I’ve updated my RaZberry a few times with no lost data/nodes and I think they share the same chip/design/firmware overall just different packaging.
Then again - if it works, don’t fix it
Additionally, if you look at the changelog of the firmware updates, a lot of it is just additional functionality for Z-Way, something you wouldn’t use unless you decide to skip OpenZwave / ZWaveJS for an Z-Way >> MQTT integration with HA.
The new firmware on UZB supports new SDK versions of Z-wave, would this not help run my network better?
Can Z-wave JS take advantage of the new SDK version of Z-wave?
Regards
Matte
UPDATE:
I updated the firmware to the latest 5.39 (SDK: 6.82.01) and it went without issue with all data intact.
Z-wave JS does not seems to take advantage of the new version as I cannot see any different data from the interviewing process on the controller.
I am sorry but I can´t remember the steps I did 1 year ago but I don´t remember any problems with the steps on the website. You have to flash the firmware in the correct order to be able to advance.
I managed to update both bootloader and firmware last night, installing z-way from the z-way website, and connecting the uzb stick to my computer. Going through expert interface:
and there’s an option to update both the bootloader and firmware (where its necessary) - needed to apply one bootloader updates, and a couple of firmware updates and I now appear to be up to date.
In order to ensure that this was successful, home assistant pi was shutdown from the interface so that there were no issues with pulling out the controller, and on re-starting, issues which I’ve been plagued with over the last week, about my z-wave network were resolved. I was expecting to continue with the nightmare, but all was working and back to being responsive again
So I was able to follow the same steps to get my UZB up to 5.07, but that’s it. It’s still on SDK version 6.51.09, but I need to get to SDK 6.61 or higher in order to do a backup and restore to my new Zooz ZAC93 LR 800.
It seems that I had to change the Acces Token to ‘all’ in order to see additional firmware updates. Once I applied to the latest, I was able to perform an NVM backup and restore.
I’m running UZB (5.27 firmware) on RPi 5 via the latest version of HASS. I had issues trying to bump the version via:
ZWave integration UI;
ZWaveMe addon UI;
Natively, via ZWaveMe Updater on Raspbian.
All failed with a generic error (“Can’t install firmware update” or similar). I’m unsure whether it was due to me selecting the wrong newer version (the ZWaveMe version selection UI is quite confusing) or something else entirely. I run MBP as a primary machine and do not have access to a PC (I was briefly considering Linux/Windows VM, though).
I’d very much appreciate any suggestions on how to update UZB. Thanks in advance!
I always use ZWay to update firmware and that generally works, but takes two or three tries to get it through. After it goes through, ZWay will jam the controller, needing a power reset, then it will show the controller with latest firmware on it.
You don’t lose your Zwave devices doing this. Just install ZWay on a spare Raspberry Pi 3 or higher, remove your USB Stick from your current HA instance (After shutting it down) and put your USB stick into the pi running Zway. I have done this with both the USB Stick and the Razberry 7 board and got the latest firmware. It’s a bit flakey with notification of completion, but it does work.
Once the firmware is updated, put it back in your HA instance and everything should work as before.
Currently the UZB USB Stick appears to be 5.39 with SiLabs SDK 6.82.01 I don’t think there will be anything more after that as I believe the UZB is a 500 series chip, like the RaZberry 2.
Honestly, if you are not experiencing issues, I would not update the firmware on the UZB or any other Z-Wave controller. It is only recommended to update if you have issues.
First time poster with a UZB1 currently running 5.34
Is there any advantage to upgrading to 5.39?
I noticed it’s rather convoluted to get to 5.34 → 5.33 → 5.27 → 5.36 → 5.39
Is there any risk in this process through Z-Way Expert UI and what are we getting for 5.39 vs 5.34. The logs seem to mention something about zniffer but the UZB1 doesn’t work with Zniffer ART and the built in Zniffer in Z-Way Expert UI seems to work with 5.34. What am I missing here? TIA
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.
Is there a source where I can download new firmwares?
I’ve got a UZB Stick running firmware 5.2 (which isnt mentionend anywhere) with zwave-js and I could not find a source for a matching firmware. Any ideas?
Ive got several zwave TRVs which do funny things so I thought updating the firmware on the stick could help.
