My Aeotec ZW090 is starting to act like it’s failing. Hard to say for sure but it seems like occasionally the signals just aren’t being broadcast to the nodes. I’ve updated firmware made a backup and got that backup to load onto a newer Z-Stick 10 Pro (ZWA060). But so far multiple attempts to get it working in OH 5.0.1 have been unsuccessful. The searches for solutions I’ve come up with indicate I need to be using the Z-Wave JS binding but from what I understand that would mean I’d have to basically rebuild the whole z-wave network from scratch since the controller would be using a different network.
I’d have to exclude each node from the old controller and then include that node on the new network. Doable but 46 nodes on my network right now, I’d rather not go through that if there’s a better/easier path. Or if I’m missing some step(s) in moving the network from the old z-stick to the new.
If there’s a way to setup the z-wave js binding to be the controller on an already defined network I suppose that would be just as good.
I did pull a backup of the old stick using Aeotec’s back up tool. Then I did a factory reset, firmware update and restored. The old stick worked after that process so I’m fairly sure the backups I’m doing are correct. Then I used the Z-Wave JS UI tool to backup the old stick and restored that to the new stick. Tool said the backup was converted to be compatible but I couldn’t get it working.
Any ideas where I might have gone wrong and could fix things or am I destined to rebuild from scratch?
No, the network lives on the controller, not in the binding. You might have to redo the secure inclusions if you can’t transfer the key to zwave-js, but you don’t have to reinclude all your devices.
On the other hand, you’ll have to switch to the zwave-js or MQTT binding on the OH side which might require changes to your Items.
Since you got the backup to load on the new z-stick your network should already be there. However, dependng on what the problem is with the zwave binding, I’m not sure moving to the zwave-js binding is likely to fix it.
Note that all the zwave stuff is done by the zwave-js software if you move to that. So any inclusion, exclusion, and other similar operations will be done through that software, not OH. But again, the zwave network is independent from the zwave binding or zwave-js and lives on the controller. So moving the controller does not require reinclusion of the devices. However, what ever problem you are facing may require that.
Is it known that a backup from a ZW090 can be restored to a ZWA060?
Aeotec tech support sent me a list of steps that are supposed to work.
Backup old stick with their tool
Factory reset the old stick
Firmware update old stick
Restore old stick
That should get the old stick firmware to a state that the JS UI tool can work with.
Backup in JS UI
Restore that backup to new stick
Adjust com port settings to match new stick
Ran through all that but the new stick wouldn’t come online. The keys in the stick should be copied during the backup and restore steps right? I did see an old thing from a previous zstick I had, thought it had been deleted long ago but I guess I missed it. That thing got deleted, went through a whole stop service, clear cache, start service and the old stick is working just fine.
Maybe a second run at backup and restore to new stick might change the behavior.
That should also get the stick firmware to where it will work with the zwave binding too.
No, the secure inclusion key is not on the controller. That would have to be transferred separately. In OH the controller Thing will have the secure inclusion key. Though IIRC it doesn’t show in MainUI (it just shows *****) so you may have to pull it from the JSONDB manually. But it’s definitely not part of the backup/restore.
If the Thing is gone, it might be in the JSONDB backups.
As to the key(s); If you did not include any devices securely it doesn’t matter. If you did, in OH it used the S0, so that will need to match on the ZUI settings page. The other S* can be anything.
As to ZUI I have never used that for controller migration. I wrote this some time ago, but they are more complex, but they did work for me. Maybe you will find something useful. Transitioning a network from 500 chip.pdf (235.8 KB).
Lastly a ZUI driver log on the start-up of the new controller might provide clues and should be included in the zwave-js github issue. (not really a OH issue). If you are trying the transitioned stick in OH, put the OH ZW binding in debug and use the log viewer.
