Z-Wave JS UI does this all automatically.
2 Likes
You need to re-configure Z-Wave JS UI with the correct USB path so it recognizes the 500-series controller. If youâre using the by-id path, those will not be the same. Then you need to restore the NVM backup.
Note NVM backup and restore to/from a Gen 5 requires the Gen 5 to be at firmware version 1.2.
1 Like
This worked, had to change the usb path. Somehow still lost all zwave devices in the network, even after restoring the back-up. There are not that many devices, like 5. Guess easiest fix is just to re add them?
Did you do a Backup and Restore under the NVM Management function? This is not the same as the regular Backup.
1 Like
I feel dumb now. Let me try and fix this.
@freshcoast I got an error while trying to restore the NVM backup to the 5 series stick. It said the file is too large?
Is your Gen 5 on firmware v1.2?
Yes it is. Just tried it again and now itâs restoring so thatâs good. No clue why I got the size error the first try.
All nodes are back. I would be nowhere without you guys. Thanks! Going to explore the gen 5 stick now and see if my nodes will be more stable.
1 Like
Mine were instantly better then after a bit of fine tuning on routes (which I could finally do without stalling the networkâŚ) Anyway, two days later I e-wasted my 700 stick. (nobody needed to inherit that nightmare)
The 500 stick I moved to is still my daily driver for a ~100 node network. Hope it works well for you too.
1 Like
So far my nodes are still not looking great. Whatâs a good place to read up or any tips on how to fix this? Iâm just clueless why nodes are âunknownâ and unresponsive. That combined with my limited knowledge, makes this challenging.
You have a new coordinator - it didnât miraculously fix everything. 
Now time to get healthy.
Who knows the why without looking at your zwave log. Generally start out with reinterviewing them. If they continue to fail interview (unknown like that) repair the route to the device then⌠reinterview it again, if it continues to fail watch the interview in the debug log while its happening and see if you can see where its failing -fix that route. Repeat as necessary. For the dead one - ping it - see if it comes back, repair its route, then reinterview it.
1 Like
Thanks thatâs a starting point!
Im a total noob on zwave but i still cant understaind why such a big issue is taking this long to solve, does anybody have more insight?
The problem is with the manufacturer of the basic chipset that is used for the 700 series based ZWave transmitters (SiliconLabs).
No idea what their problem is, but for three years they still havenât fixed the problem. No clue whether itâs the hardware design of the chipset itself or a firmware issue, but again, in the latest release notes they still mention this as an issue.