I am trying to migrate my 500 series zooz controller to the newer 700 series. I am trying to find a way to do this without re-pairing 50+ devices. I read zwavejs2mqtt can backup the nvme and use that to migrate. However, the SDK version on the 500 series stick is not new enough to support this feature. Zooz says I have the latest version and there is not a newer version that has this minimum SDK version.
I looked at using the simplicity studio - controller shift icon is greyed out on the 500 series, but not on 700 series so that was a no-go.
The NVM backup also does not work on this software for the 500 series stick- presumably for the same reasons it does not on the zwavejs2mqtt software.
Has anyone found an easy way to migrate? If it comes to a re-pair of all devices, I’m just going to stay with the 500 series.
FW 2.3 with SDK 6.4. I believe I have read you need SDK 6.6 for the NVM backup
The backup option is not listed in zwavejs2mqtt.
When I click the backup button in simplicity studio, a zip file is downloaded (I was recalling this incorrectly in original post). Using this file and loading the 700 series stick I tried NVM restore, but nothing seems to happen. No devices show as paired after I restart the program and plug/unplug the device. I can see all 51 devices and them communicating in simplicity on the 500 series stick so I do think the backup file should be valid.
Is there some kind of conversion that needs to be done on that backup before uploading to the 700 series stick?
Is there a way to manually pair in simplicity, but use the existing “pair data” from the 500 series stick? I would not mind manually migrating within the app, but I’m not going all over the house trying to figure out what the always different magic combination of buttons for exclusion is
Then you’re out of luck. Z-Wave JS does not support NVM backups from SDK 6.4. Similar to the Nortek and Aeotec Gen5 1.0 sticks it’s not possible. Strange that you have such an old version though for the Zooz.
The PC Controller software does not support 500 backup to 700 restore at all. This process requires converting between two different NVM formats. PC-Controller does not do any conversion, so you can only restore to the same exact stick. The NVM format for early versions of the SDK is undocumented, so Z-Wave JS cannot convert it.
The only other option is to use the “Controller Shift” functionality. You can do this with two copies of PC-Controller. However, I’ve only heard of one or two reports of doing this. It can also leave your network in an unusual state where the controller is not Node 1. That should work, but it’s rare. You’re probably on your own with this method. I think Aeotec might have a tech document buried somewhere on their site.
I did the Shift from a 500 series to 700 series on my system. The 700 stick/controller is now node 39… Everything seems to be working otherwise. Is the controller not being node 1 an issue or is it just “unique”? That was a LOT easier than reconfiguring the entire network…
Perfect. Thank you. The “Shift” from 500 to 700 worked really well (had both plugged into my laptop). From what I have seen so far, everything is working perfectly.
I spoke too soon. Home Assistant isn’t getting updates from devices. Things work great when instigated from HA. When turned on or off from the switch itself, HA does not show the change. I do see entries in the logs.
2023-07-09T18:16:40.356Z DRIVER « [Node 038] [REQ] [ApplicationUpdateRequest]
payload: 0x26080411085e556c9f22
2023-07-09T18:16:40.359Z CNTRLR « [Node 038] Received updated node info
2023-07-09T18:16:44.605Z DRIVER « [Node 038] [REQ] [ApplicationUpdateRequest]
payload: 0x26080411085e556c9f22
2023-07-09T18:16:44.608Z CNTRLR « [Node 038] Received updated node info
I am trying to migrate all my devices from my Nortek HUZBZB-1 500 Series stick over to the new Zooz 800 Series stick. Does anyone know how I can get the Shift button to be not greyed out in the PC Controller?
I don’t know if you already got this answered, but take a look at the comments on the video - the author gives alternatives for the two most common issues and this is one of them.
