Earlier today, I tried to temporarily move my HAOS installation from a power hungry PC with a ZWA2, to a less hungry Raspberry Pi 4 with a ZST39 stick. This was in part to test if I had redundant hardware.
I flashed the latest HAOS to an SSD, and booted it on the Pi4. I first wanted to make sure that the ZST39 Z-wave stick was recognized. So, I create a new config in HA, and clicked “add a z-wave device”. I was prompted to use the default or custom add-on. I selected the default. This caused the installation of the Z-wave JS add-on. I verified that the stick was recognized and worked.
I then restored my HAOS backup on the Pi4. All seemed to go well.
I knew I would have to change the Z-Wave JS UI configuration to point to the Zooz ZST39 stick. I did so. However, the add-on complained that it couldn’t lock the device port.
I then noticed that both the Z-wave JS and Z-wave JS UI add-ons were simultaneously installed. The original PC installation only had Z-Wave JS UI, not Z-wave JS. And the backup only contained Z-wave JS UI.
So, the restore process did not fully overwrite the existing HAOS configuration. Instead, it partially merged it - leaving the existing Z-wave JS add-on in place, and adding the Z-wave JS UI during the restore. This certainly surprised me. Is this intentional behavior ? It sounds like a bug to me.