Recommendation on NVM backup of ZST39 with older firmware.

[billmoseley]

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,

[AlCalzone]

The problem with those older SDKs is that the NVM has a different size, which is unfortunately reported as being 0 bytes. This requires a workaround when creating the backup, which is not implemented in Z-Wave JS. You can try making a backup with PC Controller and see if https://zwave-js.github.io/nvmtool/ is able to parse the binary file. If yes, it should be possible to restore it.

[billmoseley]

Thanks.

This Thursday I should have a second ZST39 LR delivered that I can test with. I already have zwave-js-ui running in a container on a spare machine, and I have Simplicity Studio installed on my Macbook. (Although, so far it doesn't really seem that "simple.") I think it needs to have the ZST39 connected first to get started. I haven't seen any links to PC Commander in SS interface yet, but maybe need to connect the device first?

I'm a bit frustrated by my lack of understanding of how things fit together, which is why I'm setting up a little sandbox to play with. The Silicon Labs documents seems a bit overwhelming for what I'm trying to do.

My primary goal is to learn more. My "other" primary goal is to make sure I'm not screwed if the controller fails.

[AlCalzone]

Although, so far it doesn't really seem that "simple."

Haha. Nothing about it is, really.

I haven't seen any links to PC Commander in SS interface yet, but maybe need to connect the device first?

PC Controller is an application that should show up under the "tools", although I'm not sure if it even runs on a Mac. Historically the Silabs tools have been Windows only.

[billmoseley]

Apparently, still is:

KInd of doubt it's actually a Linux or macOS technical issue.

[billmoseley]

My new ZST39 LR arrived for testing. Of course, it has FW: v1.40 and SDK: v7.22.0 -- so I can do NVM backup inside of zwave-js-ui. Where my "production" controller is FW: v1.1 SDK: v7.18.1 so I cannot do an NVM backup.

But, good news. I was able to do an NVM backup of my "production" controller using Simplicity Studio (with the tool "PC Controller") on a Windows machine.

PC Controller's NVM Backup creates a ZIP file with one of the files being: "ControllerNVMBackup.hex" That file can be converted to a .bin file which can then be read by Online NVM Editor.

Question:

If I restored my "production" NVM backup onto my new ZST39 LR would I then be able to:

1. "Shutdown Zwave API"
2. Swap ZST 39 LRs (replace my old one with the new one that I just restored the NVM on)
3. Re-enable (I assume on the same General Actions screen)

And should all just work? The same NVM on two controllers makes them interchangeable?

Or likewise, restore the NVM to the new controller, copy the three cache file to a new docker image running zwave-js-ui and (magically) see all my devices. I guess I'd want to power down my "production" controller when doing that.

[Update: No, that last part cannot be correct. There's a lot more config than just the cache files.]

And is this mostly correct?

• The NVM keeps the associations between the physical devices and the NodeID.
• The cache files provides more details about the last values, device configuration, and device meta data.
• The devices are mapped into Home Assistant by the homeId and nodeId (which is why NVM backup is critical)

In my core.device_registry file for a specific device there's "identifies" which is my <homeId>-<nodeId> (not sure what the rest is yet). Is that how zwave-js maps a physical device to a device in Home Assistant?

Or is there another layer?

        "identifiers": [
          [
            "zwave_js",
            "3524181575-28-99:18770:12855"
          ],
          [
            "zwave_js",
            "3524181575-28"
          ]
        ],

Thanks