Possible to use HA to move Z-Wave Network from Aeotec Gen5+ stick to Gen7 Stick?

Configuration Z-Wave
1

While Aeotec Labs offer a backup and restore utility for Gen5/5+ sticks, and a separate backup/restore utility for the Gen7 stick, it doesn’t seem possible to backup a Z-Wave network configuration from a Gen5/5+ stick and restore it to a Gen7 stick.

Is it possible to use HA to migrate an existing Z-Wave network controlled by a Gen5+ stick across to a Gen7 stick?

If ever I wanted to upgrade my current Gen5+ stick to a Gen7 stick, I wouldn’t really look forward to having to recreate my network from scratch again.

2

You can use zwavejs2mqtt. I’d call it “bleeding edge” functionality for now though.

Some users have problems with 700-series controllers as well. Might want to way for that to be solved before moving.

3

Wise advice. Thank you - I’ll wait. :smiley:

4

I disagree. It has been used here for 10 months. I expect the other Z-Wave options to disappear in February, which is the next version that will be released…

I agree on the 700 Series controllers though. The firmware manufacturer is trying to determine the issue.

5

TOTALLY Agree. I’m currently ON a 700 series Zooz and this issue continues to knock at least 5 random devices off my net every day. I’m currently installing an automation to identify ‘unavailable’ devices so I can easily fix them.

I’m currently waiting for my Aeotec 5 to move to a 500 stick. (AlCalzone wrote a tool that’s in experimental beta specifically to migrate from a 700 stick to a 500 stick because of the issue and I’m willing to try it because of how much of a pain it’s becoming)

So if I were on a 500 stick now, I’d follow that thread and wait until it’s resolved before moving.

1 Like
6

Conversion of NVM between 500 and 700 is brand new, I have no clue what you are talking about.

1 Like
7

I know that thread saved me. I had already moved most of my devices to the 700 series stick on my test machine. I ended up moving everything back to the 500 Series with zwavejs2mqtt.

8

May ping you on how you do that in DM Prodigy. I’m on JS2MQTT as well. Al’s tool SHOULD work for me if I understand its use correctly but never hurts to understand alternatives. Either way - I’m rolling my 75ish devices back to a 500 series stick next week.

9

I did not use the tool. I moved my handful of devices manually. No secure inclusions either.

10

The next version of Z2M will automatically convert the NVM formats during restore. If you want to test this functionality and are using Docker, you can pull the zwavejs/zwavejs2mqtt:master image and try it now.

If you’re using 6.2.0, you can still test it with a little bit of driver code. When you make a backup it will store the bin file in the store directory. In the advanced controls there’s a driver function option. This code will restore the backup. Just replace the NVM bin filename with the appropriate one.

const fs = this.require("fs-extra")
const { storeDir } = this.require('../config/app')
nvm = fs.readFileSync(storeDir + "/NVM_2021-12-06.bin")
await driver.controller.restoreNVM(nvm)

Step 1: Take a backup of the NVM (via UI) of the source controller. Save the file on your local PC.
Step 2: Stop z2m and pull out the USB stick
Step 3: Insert the target USB stick and start z2m and fix the device path in settings, if necessary (if using docker, fix the mapping)
Step 4: Restore the backup of the NVM. If using latest master, just use the UI Backup functionality and provide the file from step 1. If using 6.2.0, use the driver function option and the code above.
Step 5: Restart z2m

Note that this process did not work for one user so far, going from 500 to 700. More testers are always welcome. :wink:

11

I’m using the Add-In on a supervised install.

12

You can use the driver code then. Probably best to wait though, unless you’re interested in providing feedback to node-zwave-js.

13

ping me in DM Fresh - we can discuss the details. I just need to stabilize this.