My Z-Wave network was happily running on a Z-Wave.Me UZB for many years, but I jumped at the chance to get the lovely new HA ZWA-2 device when it was released, so obviously I wanted to migrate my existing network.
As per the documentation, migrating from a 500 series adapter requires the source adapter to be on SDK 6.61+.
My UZB reported in Z-Wave JS UI that it was firmware 5.5 and SDK lower than this, so I started my (in my opinion) overly painful journey to get to 6.61+ but I’ve documented it here to hopefully reduce pain for others in a similar position. These are the steps that I followed and the commands that I ran, your mileage may vary, no warranties are implied etc etc.
The UZB is considered to be a legacy device that they stopped selling in 2021. They say that it is not possible to upgrade from firmware version 5.0 and you will need to find another path (i.e. most likely rebuild your network on a new controller)
The firmware version list is shared between the UZB and RaZberry 2 product they have, and tells us that we need to hit 5.16 to meet our SDK requirements. To additionally confuse things, they interchangeably refer to 5.5 and 5.05 as the same thing.
5.05: Fixed Bootloader upgrade response.
5.06: LED can be turned off
5.07: Updated SDK to 6.51.09 (for certification)
5.16: Updated SDK to 6.70.00.
They supply a command line tool called ZMESerialUpdater - manual and download. I’m going to asusme that you have a machine where you’ve mounted the UZB stick and can download this tool and the firmwares. I didn’t do this directly on my HA server, I put the UZB stick in another linux machine. You could probably use a Live USB boot disk to achieve this if you don’t have a suitable machine, or could probably do it directly on the HA server.
/dev/ttyACM0 is where my machine mounted the UZB stick - yours may be slightly different.
We can test the connectivity to the UZB using
sudo ./ZMESerialUpdater serialapi_uzbupdate -d /dev/ttyACM0
This will give an output of the current firmware version, SDK and other info about the stick. If this doesn’t work, recheck your device name, look at basic troubleshooting like unplugging and replugging the UZB, rebooting etc - it took me a few goes for it to behave.
This software requires firmware and bootloaders from their map which took me quite a while to get my head around - it lists the upgrade path from 5.5 to 5.16 but what I consider to be an obscure way. An individual node tells us how we get from 5.5 to 5.6, we want bootloader_UZB_from_05_05_to_7278_2MB.bin and firmware_UZB_from_05_05_to_05_06.bin.
We download this first pair using
wget https://service.z-wave.me/expertui/uzb/bootloader_UZB_from_05_05_to_7278_2MB.bin
wget https://service.z-wave.me/expertui/uzb/firmware_UZB_from_05_05_to_05_06.bin
We then flash both the bootloader and firmware at the same time using
sudo ./ZMESerialUpdater serialapi_uzbupdate -b bootloader_UZB_from_05_05_to_7278_2MB.bin -f firmware_UZB_from_05_05_to_05_06.bin -d /dev/ttyACM0
This then reported a success and the version was now 5.6!
I then proceeded to follow the map to 5.7. In retrospect, I possibly didn’t need to update the bootloader each time as the version is actually the same, but it didn’t do me any harm.
wget https://service.z-wave.me/expertui/uzb/bootloader_UZB_from_05_06_to_7278_2MB.bin
wget https://service.z-wave.me/expertui/uzb/UPD_FIRMWARE_UZB500_from_05_06_to_05_07.bin
sudo ./ZMESerialUpdater serialapi_uzbupdate -b bootloader_UZB_from_05_06_to_7278_2MB.bin -f UPD_FIRMWARE_UZB500_from_05_06_to_05_07.bin -d /dev/ttyACM0
And finally 5.16
wget https://service.z-wave.me/expertui/uzb/bootloader_UZB_from_05_07_to_7278_2MB.bin
wget https://service.z-wave.me/expertui/uzb/UPD_FIRMWARE_UZB_STATIC_2ch_ZME_05_07_04000001_ZME_05_1b_04000001.bin
sudo ./ZMESerialUpdater serialapi_uzbupdate -b bootloader_UZB_from_05_07_to_7278_2MB.bin -f UPD_FIRMWARE_UZB_STATIC_2ch_ZME_05_07_04000001_ZME_05_1b_04000001.bin -d /dev/ttyACM0
Notice the very helpful consistency with the filenames… 
Now I was able to return the stick to my HA server and follow the rest of the migration back and restore process. Hopefully this is helpful to someone else!
Just when I thought I’d found a guide on exactly what I wanted to do…