Thank you for taking the time to make this video. I was migrating from a 2019 Aeotec 500 series zwave stick on older firmware. Home Assistant's NVM backup/restore through Z-Wave JS only allows restoration to an identical firmware stick with my firmware version and isn't compatible with 800 series sticks anyway (at this time). Without your video, I wouldn't have been able to migrate easily. I ran into one issue where my old controller did not display the "Add/Remove Virtual" button. I worked around this by adding up to virtual device 231 on the new controller, then removing all of those except node 231, then when I shifted it, the old controller became node 232. That then allowed me to add the new controller as node 1 when I shifted back to it. After remapping my USB path in Home Assistant, it's working great so far! Thanks again!

@AdDd45

7 ай бұрын

This is exactly what I needed, thank you !

@PhillipInc

6 ай бұрын

I should've read the comments first and that would've saved me a few minutes. Had to do this as well, if the older controller's serial api is ControllerStaticLib, you cannot add/remove virtual nodes.

@TheStarkj

4 ай бұрын

This Comment should be Pinned. Exactly what I needed.

Worked for me too, but I needed to unplug and plug my sticks back in and restart the software in between two steps. You saved me SO much time moving from the Zooz 700 to 800 series - didn't have to exclude and reinclude everything, not to mention all of the automations and stuff in Home Assistant still were linked to the proper devices and entities! Amazing. Thanks again!

Are we testing how well youtube slow down video/audio works? I must have watched the section after minute 2:22 or so like 20 times...

Bricked my first ZST39 by trying to do a NVM restore to it from a 700 series... this worked great for my second one. Now have a ZST39 working great in Homeassistant. Thanks!

Thanks, This made the process so much faster, I think you save me a week of time. As a note to anyone doing this take the backup serious, I did have to restore twice because it did not perform the shift properly, and on that note, reset your new controller before starting the shift, it might have old config in there from a test performed and cause issues.

Excellent walkthrough. Smart use of the virtual nodes to get the new controller back to node ID 1. All previous guides I've seen for this recommended including/excluding controllers back and forth over and over again until the new controller landed on node ID 1. This is a much easier, cleaner, and smarter approach. Kudos!

@notthefirstryan

7 ай бұрын

Finally got around to migrating my ZST10-700 to my ZAC93 using this method. I had lots of issues with serial communication that required plugging/unplugging my controllers from my Windows PC to get them talking right again. It took several tries and some frustration but in the end I successfully migrated and am up and running with my ZAC93 and Home Assistant Yellow now. Thanks for this video!

Well done thank you! Worked great. Important to follow all his steps in order to make sure node 1 at end.

Holy crap. Surely someone can come up with an easier method. Watching this made my head spin. I very much appreciate the video but I sure wish it was much slower and really explained all of the steps. I'm very tech savvy but not an IT professional. With all of the stories about bricking the controllers, I am so hesitant to try this and miss a step and then have no idea how to recover.

@cornellrwilliams

6 ай бұрын

I apologize about speeding through the steps. The parts where I sped up were things that I demonstrated earlier in the video. Would a written out guide be more helpful? Nothing in this video will cause you to brick your device. As long as you perform a backup as suggested in the beginning of the video you will be able to restore your controller to its original state.

I used this tutorial to swap my old Nortek 500 to a Zooz 700. My old Nortek doesn't support NVM backups and was never able to update the firmware to allow it but thanks your tutorial I was able to do it without having to repair everything! THANK YOU! I will get a 800 series controller eventually and will follow the same process.

@cornellrwilliams

4 ай бұрын

Version 9.9.0 of Z-Wave JS UI fixes the backup and restore so if you do get an 800 series controller you will not have to use this guide.

@AnisKadri

4 ай бұрын

@@cornellrwilliams good to know. There is still a warning on the smartesthouse's website about not using NVM backups but I am glad it's fixed.

@ChrisMajestic

3 ай бұрын

@@cornellrwilliams wait. are you saying that the process outlined in the video is no longer necessary to go from the Nortek 500 to the Zooz 800 if you're running the latest version of JS UI?

@cornellrwilliams

3 ай бұрын

@ChrisMajestic if your controller has ZDK 6.61 or higher and Z-Wave JS UI is version 9.9 or higher you can migrate from one device to another using the NVM BACKUP

@ChrisMajestic

3 ай бұрын

@@cornellrwilliams I’m not sure how to find the zdk version of the husbzb-1 but I’ll look it up

Thanks for this. I had the issue where I couldn't add the virtual nodes to the old controller. As you suggested to another poster, I just added them to the new controller to device 231, that made the old one 232 which made the new one 1 when I got back to it.

@tomb5372

11 ай бұрын

Thanks for sharing. I actually ran into this very same issue and didn't see that response. But I did see your comment and it had all the information I needed. Worked like a charm :) Minus the tool crashing on me and having to restore the backup to the stick and try again...

I had to basically unplug and reconnect to the sticks between everystep, not sure if it's a firmware bug or Si studio issue, but if I didn't they would do something weird instead of what was expected. SiliconLabs really need to make much better tooling for there hardware here, I love Z-Wave but if SiLabs don't sort there software support out then Matter will completely laps them.

@jhk768234dfg

2 ай бұрын

This was my experience as well. Multiple, multiple, M U L T I P L E backups and restores done to facilitate this. It may have had something to do with how close my two Z-Sticks were to eachother as they were plugged into the USB hub on my keyboard and basically touching. Still better than disassociating and re-associating all of my devices.

Thank you for putting this together. Unfortunately, after dealing with getting everything installed (and fighting documentation that didn't match the app), and trying to start the zwave pc controller tool, the app told me that it was windows only. So, if you only have Linux or Mac, you're out of luck.

@cornellrwilliams

Ай бұрын

Z-Wave JS UI v9.9.0 supports migrating to and from the ZST39. The only requirement is that your old controller needs to have firmware 6.61 and up and your ZST39 needs to have firmware version 7.19.3 and newer.

@JoeRocklin

Ай бұрын

@@cornellrwilliams yeah, I was just reading about that. But my current 500 series controller needs to be updated to a newer firmware to meet those requirements. And that also needs windows.

thank you for this detailed video, question though if I were to do this on a separate machine (say personal laptop instead of my HomeAssistant server) would I still need to adjust the node numbers or could I just transfer over the paired devices and replug the new 800 controller back to my HA instance and use it ?

@cornellrwilliams

5 ай бұрын

Right now the easiest method to migrate is to backup and restore the NVM by using Z-Wave JS UI. If that gives you an error message then you can try my guide. The Z-Wave PC Controller software only runs on Windows. The reason you need to adjust the node numbers is because of associations. When you include a device into the network an association gets set up on that device that tells it to report information to the NODE ID of the controller which is 1. If you didn't make the new controller node I'd 1 you wouldn't get any updates from your devices. For example a motion sensor wouldn't report anything. So you (2) options to fix this issue. You can either make the new controller node I'd 1 or redo your associations for all of your devices. At first both methods required the same amount of work so it was just easier to make the new controller node I'd 1.

Dang I thought I had a solution to go from my HomeSeer Smartstick+ (500 controller) to the ZST39, but looks like the old controller doesn't give me the shift option. Good video though!

@cornellrwilliams

4 ай бұрын

Is the classic learn mode option available? Also Z-Wave JS UI v9.9 supports NVM backup and restore to the ZST39. Using this guide is only useful if you can't perform the NVM Backup and restore.

@julianking6603

4 ай бұрын

@@cornellrwilliams I guess I'm not 100% sure. Zooz said the interface restore wouldn't work. I tried from within Homeseer and didn't have any luck. I didn't try the NVM backup.

@cornellrwilliams

4 ай бұрын

You are correct you can't backup and restore using the PC CONTROLLER SOFTWARE. I recommend you try using Z-Wave JS UI. I think it's the only software that is able to backup and restore to and from the ZST39. You can download the standalone .exe file from the github page and run it. It will create config files in the same location of the file. This makes it easy to delete when you are done. If you get an error that means your backup can't be restored to the new controller.

Excellent video! I do have questions connecting the zwave controllers to the software. Are you running the zwave controller software on the machine with HA running or can I connect to the old and new zwave controller via zwave inclusion using another computer with the software installed? I am asking because my HA is a VM with usb passthrough.

@cornellrwilliams

6 ай бұрын

The software only works on Windows so you will have to connect both of your controllers to a Windows machine.

@mikieikie

6 ай бұрын

so after I do that I just plug in my new controller back into my HA machine (with correct passthrough)? that's it? i am assuming the zwave controllers have memory which allows this? i apologize in advance. my knowledge is limited in this arena.@@cornellrwilliams

@cornellrwilliams

6 ай бұрын

Yes you are correct the controller has memory

Wow! How did you figure this all out? My second ZST39 is bricked and an NVM restore. How can I bring it back to life?

I have the huzbzb that others are having troubles with and I'm trying to move to a zooz 700. i was able to get to the point where I've added 231 virtual nodes to the zooz, switched back to the huzbz so it gets number 232, but no matter how many times I've tried I can't get it to shift back to the zooz. When I do the inclusion the zooz stops the inclusion, gets its new number, but never gets the updated network values. The huzbz (old controller) shows the zooz as a secondary controller but I can't switch back to the zooz since it never learns the new network values. Note that like other I needed to use the add button rather than shift button on the huzbzb due to the shift button being disabled. is there any way for me to follow up after adding the zooz controller back and force it to retrieve the network device list?

Sounds extremely promising! Thanks. A couple of questions though: - will this work to migrate from any Zwave dongle? - I'm migrating from another Linux box to HAOS... Will this software work on Linux? - if not, can I just temporarily connect both the old and new Z dongles to a Win 11 box and then transfer it to the HAOS? Thanks for your help. If this works, it will save me a ton of acrobatics on 12ft ladders

@cornellrwilliams

5 ай бұрын

There's no need to use this guide. The latest version of Z-Wave JS UI fixes the NVM backup and restore. I would try that first.

Thanks for this, very helpful and seemed to work. However in home assistant still shows the new controller as Aeotec 500 series controller. Not sure if that means it will not leverage features properly. Any hints by anyone on how to get home assistant to recognize the controller as what it is?

@cornellrwilliams

2 ай бұрын

Are you sure you are connected to the correct controller? Also try clearing your browser cache.

@MarkusBreindl

2 ай бұрын

@@cornellrwilliams Yeah i am sure, but it resolved itself overnight, so maybe it was some cache related thing. thanks anyways for the guide!

What is the importance of setting the new stick to node id 1?

@cornellrwilliams

Жыл бұрын

By default the controller is always node id #1 in the network. When you add a device to the network an association is created. This association tells the device what node id to report information to which would be the node id of the primary controller. Let's say I add a new controller with node id #5. Because associations are only created automatically during inclusion and manually by the user, all your devices would try to report info to NODE #1 instead of NODE #5. So when you do something like turn a light on manually or your motion detector detects motion you wont see an update in home assistant. At this point you have two choices. You can manually delete the old associations and add new associations that match the node id of the new controller or you can make your new controller node id #1. Both processes require the same amount of work but most people prefer to go with node id #1 for sanity reasons.

@AnisKadri

4 ай бұрын

...never mind. Figured out a way. - Create virtual nodes up to 231 on new controller and delete every virtual node up to that point. - Repeat the controller swap. Virtual node 231 is real node (for some reason) on old controller. Now old controller is ID 232. - Swap again. New controller is ID 1. - Mark node 231 as failed on new controller and remove failed.

The new Z-Wave JS release fixes the NVM backup and restore issue. I have tested this and was able to successfully migrate from the ZST10-700 Series Controller to the ZST39 800 Series Controller. Must upgrade to the following versions for this work. zwave-js-ui: 9.9.0 zwave-js: 12.4.4

@geoffhart

5 ай бұрын

Are you implying we don't need to following this video to migrate? Just use the Home Assistant GUI "NVM backup" on the old one, the "restore" on the new one? Would that work going from the Nortek HUSBZB-1 to the ZST39 800?

@cornellrwilliams

5 ай бұрын

The developers didn't list any specific hardware that this works on but I am pretty sure it will work on that device. I have tested it on the Zooz 700 and 800. If you get a warning then don't restore the backup.

@geoffhart

5 ай бұрын

@@cornellrwilliams OK, fair enough. But just to be clear: we don't do the steps in your nice video (sry) - instead we just do an ZwaveJS UI NVM backup of the old stick in HA, unplug that stick, plug in the new one, and then do an NVM restore? It will pickup the network keys and already paired devices?

@cornellrwilliams

5 ай бұрын

@geoffhart yes you are correct. The whole reason I made the video was because the backup and restore was broken now that it's fixed it's no longer needed.

@geoffhart

5 ай бұрын

@@cornellrwilliams Unfortunately, when I try the NVM backup of the HUSBZB-1, I get an error about "Error while calling api backupNVMRaw: Unknown NVM size - cannot backup! (ZW0207)", so I will try the steps in your video :D

jeus fucking christ... i have litteraly spendt 20+ hours trying to figure out how to do this and have given up multiple times, and now its done in 5minutes

Got stuck migrating my Nortek HUSBZB 500 series to Zooz 800. Add and Remove Virtual Node are not available options (not just grayed out...aren't even there). It looks like the software doesn't see the stick as a bridge. Is there any way around this? I was thinking, I could just get another 800 series stick and at that point in the instructions, move to that one to get the first 800 stick as Node 1.

@cornellrwilliams

Жыл бұрын

You have to click on the device to view the options for that device. Hopefully it's that simple. Once you include the 800 controller and make it the primary try adding the virtual nodes then till you get to 231 then reinclude the 500 series as node 232 then reinclude the 800 as node id 1. See if this works.

@matt1131

Жыл бұрын

@cornellwilliams9718 I was able to change the firmware and make it a bridge. will try this all again later today

@matt1131

Жыл бұрын

​ @cornellwilliams9718 got it working! However, the device info is still showing the old stick manufacturer, etc. Is that normal?

@cornellrwilliams

Жыл бұрын

I don't think so I've never had that issue. Maybe restart the application?

@matt1131

Жыл бұрын

Reboot fixed that.

This guy goes so fast… caution: I nuked my entire Zwave network using this.

After the Shift step, my NEW controller page shows all the end nodes but not the old controller with ID 1. So I now have no way to mark it as failed. Anyone having the same situation and how to deal with it?

@cornellrwilliams

8 ай бұрын

Trying hitting nyhe update button right below the reset button and see if it shows up then. Also see if it will let you set the new controller as the sis? If it works then you can just skip that step.

I appreciate the guide, but for some reason my ZST10 700 stick, shift is greyed out. It is also saying [S2] Gateway instead of [S2] Pc Controller like my 800 controller says

@cornellrwilliams

Жыл бұрын

Is the SELECT LEARN MODE button greyed out as well?

@flyingsubs

Жыл бұрын

@@cornellrwilliams no, but now I think I bricked my 800 stick trying to do a restore. Don't do what I did. FML

Using Aotec gen5 (ZW0500) on left for me it does not show the Add Virtual... still poking around... I was able to backup the one on the right... The backup never worked for the one on the left due to old firmware (which I have since then updated to one that does allow backups though too late now...) Stuck trying to do the part at minute 2:22 :-)

@cornellrwilliams

8 ай бұрын

If you can't add the virtual nodes to the old controller add them on the new controller till you get to node 231. Then include the old controller as node 232. Then erase the new controller and make the old controller the primary controller. Now when you include the new controller it will get included as node 1.

@mianesva

8 ай бұрын

@@cornellrwilliams thanks Cornell. Will try that... I was looking to see how to make the old controller a "bridge" because that is what enables those Virtual buttons...

@mianesva

8 ай бұрын

So I got it working, but somehow all the virtuals ended up non virtuals and to remove them I have to set them failed and remove failed, but one at a time is taking forever... I would take me less time to reset everything and just set the 18 devices from scratch. oh well. Live and learn...

Are there problems with NVM backup and restore on the ZST39? I would like to migrate from what appears to be a failing ZST39 to a new, replacement. Can I just Backup NVM from the old ZST39 and restore it onto the new ZST39? Thanks for any help you can give me!

@cornellrwilliams

Жыл бұрын

As long as both ZST39 have the same fw the you can backup and restore. Also as long as your lights still come on on the ZST39 then it is not bricked. I would need more specific information to tell what the problem is.

@MrCWoodhouse

Жыл бұрын

@@cornellrwilliams Wow. The first ZST39 was at 7.18.3 and the second was at 7.19.3. Do you think that is what bricked the 2nd zst39? I opened the case and tried grounding the reset terminal as I powered up, but no response.

@cornellrwilliams

Жыл бұрын

I think the firmware difference is the reason your device is bricked but I'm not expert. My ZST39 is also bricked and I also have a case open. 😂 The only thing I did differently from you was try to migrate my 700 series to my 800 series.

Tried to do this but shift button is greyed out for ZST10 700 stick

@cornellrwilliams

Жыл бұрын

The options you see are dependent on what is selected in the node list. If the controller is not selected then the controller options at the bottom will be greyed out.

@VACInc

11 ай бұрын

@@cornellrwilliams I am trying to do the same (but for the ZST10 500 stick) and am also seeing it greyed out even when the controller is selected. I noticed that it doesn't show that the node is "RealPrimary" under Network Role, only SUC, SIS, NodeIdServerPresent...

@cornellrwilliams

11 ай бұрын

@VACInc is the learn mode option greyed out as well? If you not use that. Maybe you need to upgrade the firmware of the stick first. Also AFAIK the real primary doesn't matter. If you look in the PC CONTROLLER documentation there is a list that outlines the difference between each controller role. Even though it's not listed as the real primary it does all of the same things.

@ludwigbear

10 ай бұрын

@@VACInc I am having the same issue with Shift being greyed out with the Nortek HUZBZB-1 stick. My stick also doesn't show RealPrimary under Network Role and only shows SUC, SUS, NodeIdServerPresent. Did you every solve your issue? Thanks

@cornellrwilliams

10 ай бұрын

@ludwigbear is your firmware up to date? Also you don't need to use shift to migrate. If you put your primary controller in add mode and your secondary controller in learn mode it will work the same as performing as shift. It just won't say realPrimary. From there you do the rest of the steps as normal. As long as your controller has the SUC SIS roles then it will perform the exact same as the real primary even if it doesn't say it.

I get no key prompt migrating to 800 series from 500. And it fails to revert back to 500 series citing security issue.

Nice video! I am trying to migrate ZW0700 Z-Wave 7.18 -> ZW0800 Z-Wave 7.18 but am having issues when shifting the old ZST-700 stick. I am not getting the prompt with all the control classes "Preparing inclusion" and i also dont get the popup for the pin. Any idea what im missing here?

@cornellrwilliams

Жыл бұрын

To confirm you press shift on the old controller and then press the add button on the new controller? If that doesn't work you can also click learn then select NWI on the old controller then click add on the new controller. Also sometimes the prompt is slow to show up so you just have to wait. I would also try unplugging and reconnecting your sticks and restarting your PC to see if that works. Try switching the USB ports your devices are connected to. Try using a USB extension cable to see if that helps.

@DavidMendello

Жыл бұрын

@@cornellrwilliams thanks for the quick reply! I was able to get it working. I updated the program and restarted. It seems like whenever it doesn't do those prompts I just unplug the sticks and restart the program and that seemed to work. I ran into a problem in the process of getting the zst800 stick to have node1 id. So I'm going to reattempt in a few. The one issue I ran into when restoring the zst700 stick though was some of the devices aren't reachable. HA is saying "This entity entity_name does not have a unique ID, therefore it's settings cannot be managed from the UI". It appears to only impact the zooz double switch and zooz on/off switches. I think that might be related to me renaming things during initial device setup. Odd that it would show as an issue now though. Will post an update in a few when I reattempt

@davemendello9282

Жыл бұрын

I think I got it semi working. I have around 50 devices that have IDs randomly between 1-100... So whenever I tried to re-add zst800 to the network to get ID1, it would get a random ID that wasn't 1. I ended up removing virtual node with ID1 and leaving the remaining virtual nodes until after I re-added zst800. But now im stuck in a weird issue because after the zst-800 stick is re-added as id1, it has all the virtual nodes still present but without the virtual node checkbox, so I cant easily determine which node is virtual and which one isn't.

@cornellrwilliams

Жыл бұрын

So in the Node Information View section you should see a hexadecimal value next to the words Property 1, 2, and 3. After comparing these values to all of my other devices on my network it looks like all of the virtual nodes will have the following set of hex values. ibb.co/t41WbDF. If you click the NODE INFO button this will reinterview the device. If the device is a virtual node it will fail as expected. Doing these two things should be enough to find and remove all of the virtual nodes however I recommend you backup your controller before you do anything to be safe.

@DavidMendello

Жыл бұрын

@@cornellrwilliams I'll look into that. I have a solid backup of the zst700 so maybe I'll try again tomorrow. I tried plugging in the zst800 stick into HA, changed the driver path zwavejs and was able to see all my devices + all the virtual devices (virtual devices all red with spinning indicating node failure obviously). But I think having the 200+ virtual nodes failing broke things in zwavejs because it looked like it was trying to discover all of them so no remove node operation worked. I also wasn't able to control any of my real devices either (unclear why I wasn't able to control any of my devices)

While you're method might work, why not just do a restore after backing up? That's the whole concept of backup->restore - your old controller died or you want to upgrade so copy the NVM out of the old and and push it into the new one. The problem is that if the 500 series is old enough, the backup utility has all sorts of bugs and doesn't actually work. If it's really old, it doesn't support backup at all. 700->800 should always work as the 700 series started out supporting backup/restore. 500 series is a crap shoot. If the network is small (under a dozen node) I would still recommend excluding everything and starting fresh. Be sure to add the Always-On nodes FIRST, then any battery powered nodes last. And run a network heal after joining all the nodes.

@cornellrwilliams

8 ай бұрын

The backup and restore currently does not work between the 700 and 800. I upgraded the firmware on both sticks and tried to migrate between the two and bricked my device and had to do a warranty repair. Others reported the same issue. I was using 7.18.3 on my 700 and 7.19.3 on my 800.