You can just start the ZWave binding and it will (eventually) rediscover all devices by itself. You do not need to reinstall everything “from scratch”.
To speed things along, it is useful to copy this folder over. This folder contains the information the binding downloads from the devices, so copying the data over will speed things up as the binding won’t need to download it again. This is especially useful for battery devices as they may only wake up every hour, or every day, so this process can take a long time.
One other point - don’t forget to copy over the security key in the controller thing from your OH2 system
I probably should have mentioned that first step earlier, so apologies for that but I had kind of assumed that was a given that the controller needs to be created… I should remember - nothing is a given
Just want to add, if it helps: when I migrated from OH2 to OH3 I just moved the userdata/zwave folder to the new instance, and after I added the controller everything was discovered and added flawlessly. So I guess that’s to be considered when you do an upgrade.
I am using a Z-wave binding based off a 2.5.11-Snapshot from November 28 modified to read the humidity of my RTC thermostats. The only file that is modified is the ZwaveNode.java.
Will the 2.5.11 snapshots work (in general) with OH3 or is there a 3.0 Zwave binding that need to be used? I could not see anything obvious on github.
Glad to have found this thread. I’d like to play with OH3 on a separate piece of hardware without permanently bringing down my OH2 instance. Does the z-wave node number assignment stay with the transceiver? That is, will node3 in the OH2 system still be the same device with the same ‘node3’ designation in the OH3 system if I just move the USB dongle?