-
|
Hi all, |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 6 replies
-
|
AFAIK the best way to do this is to do an NVM backup of your controller, plug in the new one and do a NVM restore on it. To be sure wait for @AlCalzone @blhoward2 or @kpine to confirm this |
Beta Was this translation helpful? Give feedback.
-
|
The NVM backup way requires the old controller to be built using SDK 6.61 or newer. The alternative Controller shift isn't supported atm. I might try and figure out the memory format of older SDKs at some point though, since I also have an older Razberry in production |
Beta Was this translation helpful? Give feedback.
-
|
If you plan to go from a Razberry to another Razberry, I would contact Zwave.me support (either directly or in their own forums) and see if they support this kind of controller replacement, either through some tools or with their software. They use custom firmware for their devices, so they may have better accessibility. |
Beta Was this translation helpful? Give feedback.
-
|
The RaZerry 2016 controller reports FW 5.37 with SDK 6.2.0 - so NVM backup might not work as expected. But I'll ask in the Z-Wave.me forum and share their answer. |
Beta Was this translation helpful? Give feedback.
-
|
That's more than likely protocol v6.2 which is SDK 6.81.1 and that supports NVM backups. If the driver logs show that it supports SmartStart, then probably (?) supports NVM conversions as well. See issue zwave-js/node-zwave-js#5160, feel free to add a startup log showing the controller interview if you can. |
Beta Was this translation helpful? Give feedback.
-
|
You can use Z-Way for sure:
But Z-Wave JS may work as well. |
Beta Was this translation helpful? Give feedback.
-
|
If I remember correctly, the 2016 Razberry runs an old SDK, not 6.81 |
Beta Was this translation helpful? Give feedback.
-
|
Yes, but the firmware is upgrade-able. If OP has FW 5.37:
OP will have to confirm though. |
Beta Was this translation helpful? Give feedback.
-
|
I'll have to download their Zway software and update the firmware then it seems. |
Beta Was this translation helpful? Give feedback.
-
|
Using Z-Way 3.2.3 an update from NVM backup from JS UI works with this version. Next step is to change boards and try
|
Beta Was this translation helpful? Give feedback.
-
|
Did replace the board and used Z-Way software to update firmware / boot loader to the latest versions, which now is: Afterwards killed Z-Way, restarted JS UI and restored NVM which **worked 👍 ** although Product and Product Code get overwritten by the old values. Well, out of curiosity I restarted Z-Way server to see about Product Code and found there is another firmware to upgrade to 7.28. Which did overwrite the wrong Product and Product Code to their intended values. The overall process might not be quick but 2-3 coffees and 2 hours of time allow to replace a controller without re-training nodes. |
Beta Was this translation helpful? Give feedback.
Did replace the board and used Z-Way software to update firmware / boot loader to the latest versions, which now is:
Hardware Vendor: RaZberry by Z-Wave.Me Vendors Product ID: 1025 / 257 Z-Wave Chip: ZW0700 Firmware Library Type: Static Controller SDK Version: 7.17.00 Serial API Version: 07.21Afterwards killed Z-Way, restarted JS UI and restored NVM which **worked 👍 ** although Product and Product Code get overwritten by the old values.
Well, out of curiosity I restarted Z-Way server to see about Product Code and found there is another firmware to upgrade to 7.28. Which did overwrite the wrong Product and Product Code to their intended values.
Z-Wave Shield for Raspberry Pi | RaZberry 7 Pro