[EDIT: Important note. Updating the firmware may change the frequency of your dongle. See Updating Razberry firmware - how to allow serialupdater tool to access device for the solution. ]
I finally got around to updating my Razberry z-way bootloader and firmware:
stop openhab:
sudo systemctl stop openhab2.service
Download and install ZWay
wget -q -O - razberry.z-wave.me/install | sudo bash
Start zway:
sudo /etc/init.d/z-way-server start
Go to the web interface for your zway installation:
[IP]:8083
Then backup your z-way controller. Of note, this is also where you can remove failed nodes, and other similar tasks.
http://[IP]:8083/expert/#/network/control
The quick way to get to z-way firmware info:
to see your config, go to your server IP address:8083/expert/#/network/controller
or to upgrade, go to [IP]:8083/expert/#/uzb
Based on my controller info page, I was on version 5.04. I then went to the floating map:
https://service.z-wave.me/expertui/uzb-stats/versions-graph.html
And eventually deduced (by clicking on the nodes and sorting through the mess) that the files (and order to be installed) that I needed were:
1) first needed to update the bootloader
https://service.z-wave.me/expertui/uzb/bootloader_Razberry_from_05_04_to_8aaa_2MB.bin
2)
https://service.z-wave.me/expertui/uzb/UPD_FIRMWARE_Razberry500_from_05_04_to_05_07.bin
3)
labeled as 5.07-5.23 (discrepancy in the label and the filename versions)
https://service.z-wave.me/expertui/uzb/UPD_FIRMWARE_Razberry_from__05_07__to__05_17.bin
[note, in hindsight, there was an alternate route from 5.04 to 5.16, but also 5.16 had a text description labeling it 5.22]
4)
labeled as 5.23-5.32 (discrepancy in the label and the filename versions)
https://service.z-wave.me/expertui/uzb/UPD_FIRMWARE_Razberry_STATIC_2ch_ZME_05_17_04000002_ZME_05_20_04000002.bin
5)
labeled as 5.32-5.36 (discrepancy in the label and the filename versions)
https://service.z-wave.me/expertui/uzb/UPD_FIRMWARE_Razberry_STATIC_2ch_ZME_05_20_04000002_ZME_05_24_04000002.bin
I was able to successfully upload all of these firmwares. (via http://[IP]:8083/expert/#/uzb )
It’s a bit disconcerting that the file names and text descriptions have different version numbers.
It appears that despite appearing to have used ‘upgrading’ language, the version didn’t change after uploading all these files and having the display say upgrading. You then need to go into Network>Controller Info, and press the upgrade firmware button again, and then select some of the uploaded firmware files. I only had to do this additional step once, then the rest had to be re-uploaded and they seemed to have been applied correctly.
Before the update, the firmware info per my z-way web interface was:
Role in Network
Node Id: 1
Home Id: 0xc3b69503
Primary Role: Yes
Primary Capability: Yes
SUC/SIS in network: 1 (SIS)
Hardware
Vendor: RaZberry by Z-Wave.Me
Vendors Product ID: 1024 / 2
Z-Wave Chip: ZW0500
Firmware
Library Type: Static Controller
SDK Version: 6.51.06
Serial API Version: 05.04
Capabillities:
UUID: e95d15fcd29664737755476e6b2bd311
Subvendor: 0x0000
Nodes limit: Unlimited
Capabillities: SlM
Software Information
Version number: v3.0.4
Compile-ID: 36b67fd3f95539b8bb512f6b48f5faac9f16d38a
Compile-Date: 2020-01-20 13:33:17 +0300
UI
UI version 1.5.1
Built date 20-01-2020 13:12:50
After the upgrade, I get the below information, with a successfully upgraded firmware
Role in Network
Node Id: 1
Home Id: 0xc3b69503
Primary Role: Yes
Primary Capability: Yes
SUC/SIS in network: 1 (SIS)
Hardware
Vendor: RaZberry by Z-Wave.Me
Vendors Product ID: 1024 / 2
Z-Wave Chip: ZW0500
Firmware
Library Type: Static Controller
SDK Version: 6.81.01
Serial API Version: 05.36
Capabillities:
UUID: 45a79b7daa869cc0ff3a42a94fdb5bc4
Subvendor: 0x0000
Nodes limit: Unlimited
Capabillities: SlM
Software Information
Version number: v3.0.4
Compile-ID: 36b67fd3f95539b8bb512f6b48f5faac9f16d38a
Compile-Date: 2020-01-20 13:33:17 +0300
UI
UI version 1.5.1
Built date 20-01-2020 13:12:50
I was eventually able to get the reported firmware version to be what I expected based on the text labels in the floating map. Given this, I think the file names are named incorrectly. I did need to re-upload a couple of the files to get the version to update in the controller info page.
I call this a success, from 5.04 to 5.36.
Grumbling:
Now, I will try restore my full openhab system from backup (had amanda set up, but haven't had to figure out how to restore it yet), but perhaps I will first try a new raspberry pi3b card. This upgrade adventure brought to you by low voltages at the pi and a frozen rainbow screen of death (despite mutliple different very capable supplies). I was able to eventually re-install on a fresh memory card, but kept getting low voltages warnings, and I'm hoping that I can continue with my old memory cards on a new board. At the very least, I was able to sort out how to upgrade zway at a time of low risk, given that I was playing with a fresh openhab install anyway. I was tempted to move to a more robust mini-pc, but then I'd have to migrate my zwave controller (designed for RPi GPIO pins) settings.
For anyone considering the RaZberry hat vs a USB adapter, this is a big advantage for USB adapters as they are much more portable.
Cheers.