I would like to move to a new Zwave stick but i would like to do that on a device by device basis. So exclude a sensor on the primary stick, factory reset it and add it to the new stick.
I can add the new stick as a Thing, configured it on the right usb port and made it secondary. So far, so good.
How do I add sensors to the stick? Scanning is done via the primary and if i add a sensor directly to the aeotec stick, how can i than get it in openhab?
Do the zsticks use the same chip? What is the end goal? It would be news to me that one OH instance on one server could support two zsticks, especially if they are the same chip. EDIT: and how many devices?
the ultimate goal is to migrate all 30-40 zwave nodes to the new Aeotec gen5+ stick. I like to make a fresh start with this new stick and therefor also do a factory reset as well before i include them in the new stick. The current stick is also an Aeotec
OK. If both Aeotec zsticks have the action button. The easiest is to go around with the old stick exclude the device, factory reset (some devices automatically reset to factory when excluded), then include with the new stick. That way if the device needs to be “open” to access the “action” button you can do it all the same time. I don’t understand the one at a time requirement since only one zstick can be connected at one time AFAIK. I would just go around the house until finished.
I’d be remiss if I didn’t mention using Simplicity studio (or older Aeotec tool) option to simply copy the old nvm data from the old stick to the new stick. Since both are gen5 so it should not be a problem. Then read the device manual to find the default settings and apply them when you add the new stick to OH
The steps you describe is exactly what I’m doing, but at the end, when the sensor is added to the new stick, it needs to be added to OH as well. That’s where things go wrong. How do I add the sensor, which is added to the stick itself, to OH?
Some background;
To keep things straight in ZW the controller has a unique 4-byte 64-bit identifier. You can see this in the userdata/zwave folder on the XMLs. This is separate from the OH Thing UID. The suggestion to copy the zstick nvm would transfer the old controller identifier to the new stick, so OH shouldn’t know the difference.
As to what you are doing now;
The device data should be on the new stick and when that stick is plugged in and the old one removed it should pick up the new devices and show the devices that have not been transferred as offline. What you could try is to remove the new controller from OH, note the UID of the old controller and then manually readd the new controller with the same UID (this may help) but as primary. (It has been a while, so I might be forgetting something else). I’d activate the debug on the binding when adding the new controller, so if it doesn’t work, we can figure out what I missed. The devices on the new zstick should show up in the userdata/zwave with a different 4-byte id. Powered devices should appear quickly, but battery devices will need to be woken.
