Відео

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.

@@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.

So there are 2 ways you can migrate. You can perform a NVM Backup and Restore or you can perform a controller shift which is what I demonstrate in this video. The NVM backup and restore is the fastest method. It takes 2 minutes to do but there are some requirements. Your old controller needs to have fw v6.61 or newer. The ZST39 must be using fw v7.19.3 or newer, and you must be using Z-Wave JS UI v9.9.0 and newer.

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

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

It's called Z-Wave JS UI.

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.

@@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.

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.

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.

@@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.

@@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?

@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

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

Yes it will work. The way you mentioned is the exact method I used.

@@cornellrwilliams thanks! I'll give it a shot soon then

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.

Thanks for the feedback. I appreciate it. I will look into that.

I don't know much I just make what I read from others in videos

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.

I took it down because the NEW Z-Wave JS UI release allows you to backup and restore.

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?

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.

@@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?

@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.

@@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

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

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

Yes you are correct the controller has memory

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.

@@cornellrwilliams Please a written guide would be amazing, that sped up part blows my mind even though it is the same steps shown again. I'm scared to start this. I am trying to upgrade from nortek stick to new zooz stick

@therealweston I will write one and get back to you

@@cornellrwilliams Thank you so much!! Your name is being passed around over on the home assistant forum also just fyi. I think there are lots of people running into this situation but everyone is afraid to attempt the migration in hopes that they don't lose their network through an accident.

Thanks. You Will love it. All the stuff Zooz makes is really good.

In smart things you will go through the process that you would go through to add any other Z-Wave device. Put your hub into Inclusion mode then in the pc controller software click learn mode the NWI to include new controller into smart things hub.

Thanks. can I do this on a windows machine without a z-wave adapter plugged in? Connecting to smartthings over IP?

No you need a Z-Wave adapter or else this won't work. There is a smart things integration that you can add to home assistant that will let you control any device connected to your smart things hub. This is cloud based though.

Thanks. and thanks for the video. I expect it wills ave me a huge amount of time in my migration.

You download from the office GitHub page here. github.com/zwave-js/zwave-js-ui/releases

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.

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.

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.

@@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...

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...

This is exactly what I needed, thank you !

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.

This Comment should be Pinned. Exactly what I needed.

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...

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.

Is the SELECT LEARN MODE button greyed out as well?

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

All you need to do is connect the positive wire from the power supply to the C terminal then connect the positive wire on the siren to the NO terminal. Then connect the negative wire on the siren directly to the negative wire on the power supply.

@@cornellrwilliams yeah that’s exactly what I have but it seems like my relay is not getting power. I put a meter on the power and it’s getting 12V to the relay but I’m unable to switch it on and off via my zwave hub (hubitat)

@markt4567 is your device using factory settings? If so I would take a wire S1 to C on the input side and see if that turns the relay on and off. If that works then it might be a habitat issue

@@cornellrwilliams that didn’t work. What does work is having the usbc power and a power source wired directly as you described. Should I need two power sources?

@markt4567 you only need one power source for the Zen17. Then you will have another power source connected to the relay to power your load

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.

@@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...

@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.

@@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

@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.

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.

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

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

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

Reboot fixed that.

Yes you can do this but if you want the button to control the relay without going through the Controller you would need to find a button that has association groups that send basic commands. You would also need to make sure your buttons supports the Multi Channel Association command class. The basic command is what turns the device on and off. Wether or not your device supports the Multi Channel Association command class will determine whether or not you can Individually controll each relay. If your button supported it you could have one button turn relay 1 on and off then another button turn relay 2 on and off. If I doesn't support it you would only be able to turn both relays on and off. You can find out what association groups a device supports as well as figure out if it supports the Multi Channel Association command class by visiting products.z-wavealliance.org/. This is the official catalogue of all Z-Wave Certified Devices and is the first place you should look to learn about Z-Wave Product Offerings as well as learn specific information about a Z-Wave Device.

Thank you very much!

Super handy video, thanks a ton!

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.

@@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

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.

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.

@@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)

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.

@@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.

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.