Additionally, you may consider finding the actual by-id address for the new port (instead of the virtual port ttyUSB0) - you should be able to find it in settings > system > hardware > all hardware.
The virtual ports can technically change if you inplug/replug a device or switch ports so connecting by-id instead allows ZWave JS to locate the device no matter what port you plug into, surviving any virtual port changes.
This referred to ZWave not zigbee. There are methods for Zigbee but they aren’t a direct translation. You can search on the forum for stick migration methods or start a new thread if you don’t find what you are looking for.
I know… and as you might probably know, Z-station houses both Z-Wave & Zigbee. (and Bluetooth, Matter & Thread). So if this person has both Zigbee and Z-wave devices, it would make sense to me he would like to migrate both. So the question is definitely related in my opinion, but just not in the way you saw this personally. Don’t get smart, be gentle.
No we don’t. And why I said so… (also I really despise compound devices personally - you’re just asking for maintenance difficulties IMHO)
And respectfully, it needs another thread this moved an Aeotec ZWave stick to the device. Moving zigbee will be an entirely different process if it’s possible (I don’t know what zigbee chip the device uses. And thats how you tell.) there are zigbee migration steps in the forum you need to start by searching on zigbee migration and the model number of your EXISTING stick.
Hello Nick,
Thank you for your instructions. I have also tried to switch from a Gen5+ stick to the Z-Station. However, I get the following error message during the restore:
“The NVM file ID must be set before serializing restoreNVM undefined”
Did you set anything special during the backup/restore?
Was “Skip compatibility check” checked during the restore?
Might be an issue in latest Z-Wave JS as others have encountered this error:
If you are using the Z-Wave JS Docker container you could downgrade to older versions of Z-Wave JS UI to see if any work, I’d try 9.20.0 then 9.18.1. If using the add-on looks like you’ll need to wait for the issue to be resolved in an future version.