Recommendation on NVM backup of ZST39 with older firmware. #7533
Unanswered
billmoseley
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Update 1/6: Darn, I completely forgot that I posted a similar question a few weeks ago. Apologies for the somewhat duplicate.
I'm running a Zooz ZST39 LR with older firmware (FW: v1.1 and SDK: v7.18.1), but that version is too old for NVM backup in zwave-js-ui. (See: NVM Backup/Restore requires a firmware based on Z-Wave SDK 7.19.0 or higher).
I asked Zooz support about upgrading so that I can then create an NVM backup. They responded that I should not upgrade unless experiencing problems. Of course, if I'm having problems then I'd probably really want to have that NVM backup....
What would you recommend for backup and/or upgrading the ZST39 LR?
I'm only Mac, so should I use Simplicity Studio and try and backup the ZST39 NVM using that?
Great. Now I'm getting anxious....
If my ZST39 controller failed (and I don't have an NVM backup) then what is required to get back to where I was? Would I have to manually remove all the devices from zwave-js-ui, and then manually add them back in?
That would be a nightmare since I'd have to open up almost every wall switch to get the QRs off the devices. (Note to self: save those QRs from now on....)
And then I assume all the devices IDs in Home Assistant would change and some (many) entity names would change and dashboards, scripts, automations would all need to be hunted down and updated.
Almost all of my devices were added before I was using zwave-js-ui, so I don't have my devices pre-provisioned. Showing my lack of knowledge here, but is there any way to populate the Provisioning Entires from my existing network?
Thanks,
Beta Was this translation helpful? Give feedback.
All reactions