I just successfully migrated from a Razberry Zwave 500 Controller to a Zwave 800 Zooz ZST39 Stick using backup/restore. And it worked absolutely fine and fast.
Source: RaZberry2 Zwave 500 Controller on latest firmware ( OH 5.0.2 on Rasperry 4, openhabian, OH-Zwave Binding)
Destination: A brand new Zooz ZST39 Zwave 800 Controller
This ist what I did:
- Stopped OH Service
- Startet latest Zwave JS UI in Docker
(I interviewed all devices at an earlier stage, not sure if it’s needed for this process) - Take a NVM backup of the old Razberry2 controller
- Shutdown to remove Razberry and connect Zooz Stick
- Startup RPi4 and stop OH Service to start Zwave JS UI again (Adjust path of Controller)
- Obviously no devices will be displayed anymore at this stage.
- Update Zooz Stick to latest firmware (1.6)
- Take NVM Backup of Zooz Stick (Just to be save)
- Restore NVM backup of old controller (Razberry2) to ZooZ Stick
- After less than a minute it was finished an all devices where back. (I was so relieved
) - Rebuild the routes in Zwave JS UI to be sure they are optimized with the new controllers range
- stop Zwave JS UI
- Start OH Service and navigate to the controllers thing which now may be offline if your device path changed (like in my example)
- modify the controller thing to the new device path if needed and give it some time to initialize. (I disabled and re-enabled the thing because it stayed offline for some seconds. But maybe it’s not needed)
- After some seconds, it should be back online as should all Zwave nodes.
I’m so happy this worked. Because of the Razberry2 controller I would have had no other choice than exclude/re-include 46 devices.
I hope this helps others who are afraid of possible controller bricks when using backup/restore