You need to click on node ID 1 the node you currently have selected is the node id of the new controller.
Thank you @cornellrwilliams!! That was it. IDK why but I assumed that the first controller would be my new one. I was still not able to get everything transferred to the new controller. I don’t think the “Add” function worked. It seemed like it did and I did not get any errors but nothing was showing up in associations. I will have to try and tackle this some more. Hopefully I can figure this out.
Thank you again 
You have to select all of your devices in the device list except your controllers then click the node info button to reinterview the devices. Once you do this you should be able to go back to the associations page and see all of your devices in the association list.
Thank you again for walking me through this. I’m still struggling to do a full migration. I selected all of my devices and clicked the node info button, and nothing changed. I started to randomly selecting one device and clicking node info, and alas ONE of them added and I could see it in the association page. Do you know why only a few devices were able to add?
Only the devices that are successfully interviewed will be shown in the association list. Clicking the node info button is the same as interviewing the node.
Why would my devices not be interviewed properly? I have clicked them individually and clicked node info, and the log shows things happening and no errors, but never gets interviewed/shows up in the associations page.
If the device is a battery powered device it has to be woken up to be properly interviewed.
Thank you again for your assistance @cornellrwilliams!!!
I have given up doing this since I was having difficulty executing this.
To be clear and maybe why I could not get this to function, do my devices have to be on AND my old controller needs to be off? IE my devices are not connected to any other controller.
I figure this may help others who are trying to do the same thing.
I am about to travel down this road.
I have SmartThings (V2) with 99 devices.
I have HA Yellow
I have Windows PC with ZooZ Wave USB
I have downloaded and installed Z-Wave PC Software
I have added both the PC Zooz stick and Smarthings to the software
The video seems to demonstrate moving the Node ID from Smarthings to the PC Zwave…
Question…
Is the SUC/SIS controller determined by the ZWave Radio?
Why would you change the Node from “Smarthings” to “PC” rather than changing the Node from Smarthings to HA?
I guess for me I should see three controllers…
Smarthings
HA
and PC
I would actually change the device Nodes from the Smartthings ID to the HA ID - correct?
I am still waiting on my HA Z-Wave “stick” to add Z-Wave to HA - so I haven’t actually tried adding HA to the software yet. I was going to use the Zooz Z-Wave USB stick, but I decided to order an internal add-on instead.
1 Like
what did you find to your answer? Was it hard to move all your SmartThings over to HA? I’ll be doing it this week
So…
Some things I assumed but learned differently during this process.
-
You cannot add both the SmartThings Hub, Home Assistant Hub at the same time.
-
When you connect to SmartThings Hub using the USB Stick in a PC - the PC becomes the new “Hub”. Home Assistant is not in the picture - yet.
-
As you move items from SmartThings to the PC (USB Stick) - those devices are actually stored inside the USB Stick and will migrate with the stick when it’s moved. I did not know this.
-
So these instructions assume you will pull the USB stick from the PC and insert into Home Assistant HUB. In my case this was not an option, I have Home Assistant Yellow and an onboard Wave module - not a USB stick.
Ultimately I moved all 96 devices manually.
My technique… I moved all the outlets - one at a time - to HAOS then did a Wave repair. I have enough outlets to get a good backbone going.
Once I did this, I began dropping - one at a time - each wall switch, walking from closest to farthest out…
After I made sure the outlets and switches came across good, I then did all ancillary 110 device (none wall embedded switches)…
Only after all these devices were healthy in HAOS did I then attempt to do battery devices like leak sensors…
And after all that, I dismounted my door lock and placed them 3 inches from the HUB to pull in the Z-Wave Door locks…
After all of that, I walk through each device in HAOS - checked for any firmware updates, checked for any missing attributes, and did a “remap” for any potentially problematic devices…
Although painful, my Z-Wave devices have been rock solid
1 Like
Hey Cory, welcome!
So you used the SUC transfer to get the devices to the stick…
You should then put the USB stick in a powered USB hub (to avoid the potential power issues) then plug that into the yellow and configure from there. It had your network at that point and should have been able to move forward. The Yellow has onboard Zigbee - not ZWave.
But glad to hear you’re good to go in any case.
Sounds like it worked out in the end!
I followed the video and I would say 80% transferred easily of my 75 zwave devices. A lot of my inovelli devices did not and I had to exclude and include. The new stick had them on there as an unknown device at node 55 for example. I probably messed up the security somehow. I thought I followed the instructions perfectly though. My 2 locks had to re-add as well, which makes sense with that security. I don’t know what I would recommend to someone that was moving from ST to Home Assistant, because you’d have to exclude all those devices and it did save me a lot of time. ST exclusion is much slower than Zwavejs UI. My new stick is node 110 and I wish it was 1, which is a dumb thing to care about. Everything works great.
I used Smartthings for 5 years and with their changes I am now out. I have a frame TV and that’s really the only thing I use it for.
1 Like
So Z-Wave JS released an nvmedit tool a while ago. I believe you can use it to change the node id of your controller. I’ve used it a few times to keep my node ids in order.
2 Likes
Hi @cornellrwilliams — still trying to get to a reasonable migration pattern here. I was on the ZW JS forum about the issues I mentioned to you in another thread Multiple Z-Wave controllers? - #24 by glenmm working with the HA ZW controller as secondary to Smartthings. They advised me that " secondary controller support is experimental. Nodes are not interviewed by default, but not sure if they are supposed to persist the info after an interview or not. "
Z-Wave JS - Z-Wave driver written entirely in JavaScript/TypeScript seems to have a number of warnings that describe my situation.
I’m writing you to get the advice of the ZWave migration guru 
I really dread the idea of manually enrolling all these devices into the new HASS Zooz 800 controller. I want to selectively migrate devices and routines over time (not one big bang). Thinking that if I change the Zooz to be the SIS/SUC, ZWJS will think it’s the primary controller and operate normally. I won’t enroll any new devices to ST, only enroll them to HAOS. Could this work (i.e. having two controllers live that think they’re primary)?
In my setup even though it said it was interviewing all I the discovered information persisted even after a reboot of Z-Wave JS UI. I had no problem controlling my devices. What problems are you currently having migrating?
HA drops all the devices from the dashboard when Zwave JS UI or HA reboots. The ZWave integration shows Z-Wave Network Connected - 41 devices (40 not ready). I have to re-interview everything (including any sleepy devices) to get everything working again. This with a Zooz 800 in HA as secondary to Smartthings.
I got the same error but not consistently. I made my secondary controller the suc/sis/primary like you suggested and the issue went away. I can still control both my devices from both controllers and updates in the other.
1 Like