Clone Z wave js integration

Configuration Z-Wave
1

Hey Community,

I am running home assistant for a couple of years now and it became a more and more indispensable part of our home over the years. That made me thinking. What is needed, if my current setup just broke because of a solar flare or an EMP or something? I decided to buy the same material of my current setup again: a deconz conbee II zigbee stick, an Aeotec AEOEZW090-C zwave stick and an odroid n2+. My question now is: What data do I have to backup / copy, if I wanted to clone my z wave js integration from one z wave usb stick to another? Will it suffice to just copy the integration and the configuration data of home assistant or is there data stored on the z wave usb stick?

Thanks for your advice!

R.

2
3

The only way to back up the zwave stick is pull it put, stick it in a windows pc and use the aeotec tool…

4

There are multiple levels to consider for your Z-Wave installation.

  1. Controller NVM. This contains the information about the network, like the network home ID, node IDs and routes. Losing this data is catastrophic. However, it would be very rare for this kind of loss to happen.
  2. Driver cache. These are jsonl files stored in the filesystem, the driver reads and writes to these. They are meant to be persistent. Losing them will temporarily cause trouble, but they can be rebuilt.
  3. Application configuration. If you’re using zwavejs2mqtt, there’s a settings file. If you’re using Add-ons, these are the add-on configurations. The critical part of this level are the security keys. If these are lost, it will be impossible to communicate with securely included nodes.
  4. HA device and entity data created by the Z-Wave JS integration. This contains all of your custom device and entity naming, and internally maps the entities to the driver values. Losing these means losing all of your customization, which may be painful to restore. Aside from the naming, these are just rebuilt based on the driver information.

The Controller NVM can be backed up by zwavejs2mqtt, or the Silicon Labs PC Controller software. zwavejs2mqtt is the way to go here. With it you can also restore the backup to controllers of different generations (500 to 700 and vice-versa). That is not true with the PC Controller software (500 to 500 or 700 to 700 only). Losing this data is catastrophic, however rare.

The driver cache is easy to backup via normal file backup means. If using an add-on, this data will be part of the add-on backup data.

The application data is either part of zwavej2mqtt’s settings file, or your docker configuration, or the add-on configuration. Backing that up depends on how you’ve installed. If using an add-on, this data will be part of the add-on backup data. Most important here is probably those security keys.

The HA integration data is stored in HA’s /config/.storage directory, it can be backed up with normal means. However restoring it may be problematic. It’s an “all or nothing” restore. You can’t restore just the Z-Wave JS integration data, for example, without some difficult manual editing.

2 Likes
5

Thanks for your input. My goal is to have hardware redundancy because of the risk of hardware defects. So I would like to elaborate No 1. from freshcoast´s message:

While the other points are clear to me and could be achieved by cloning the eMMC or SD card, when and how is it necessary to backup the AEON Z Wave USB stick? Should that be done every time, a new node has been added or removed from the Z Wave network? Or does it suffice to do it once, after the Z Wave network has been setup. What about the configuration information in the Z Wave JS addon (network_key, s0_legacy_key, s2_access_control_key, s2_authenticatd_key, s2_unauthenticated_key): Is that the data stored on the stick or is there more data?

Thanks again for your help and enjoy your weekend! :slight_smile:

R