From 713c20cba8c9a53e4d931487df439299caa873cf Mon Sep 17 00:00:00 2001 From: c0ffeeca7 Date: Thu, 12 Jun 2025 15:26:57 +0200 Subject: [PATCH 1/4] Add backup topic --- source/_integrations/zwave_js.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_integrations/zwave_js.markdown b/source/_integrations/zwave_js.markdown index cd82060e459d..e7cb3c4c3465 100644 --- a/source/_integrations/zwave_js.markdown +++ b/source/_integrations/zwave_js.markdown @@ -184,6 +184,10 @@ To migrate a Z-Wave network to a new controller, follow these steps: - Confirm that you connected the new controller by selecting **Submit**. 6. Follow the steps on screen. +## Backing up your Z-Wave network + +Back up your Z-Wave controller's Non-Volatile Memory (NVM). The NVM contains your network information including paired devices. It's recommended to create a backup before making any major changes to your Z-Wave network. + ## Special Z-Wave entities The Z-Wave integration provides several special entities, some of which are available for every Z-Wave device, and some of which are conditional based on the device. From 78fec23b54113fdacd82191ce78eefca48782157 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 Date: Thu, 12 Jun 2025 16:06:10 +0200 Subject: [PATCH 2/4] Add steps on creating a backup --- source/_integrations/zwave_js.markdown | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/source/_integrations/zwave_js.markdown b/source/_integrations/zwave_js.markdown index e7cb3c4c3465..b03bb3e46320 100644 --- a/source/_integrations/zwave_js.markdown +++ b/source/_integrations/zwave_js.markdown @@ -186,7 +186,19 @@ To migrate a Z-Wave network to a new controller, follow these steps: ## Backing up your Z-Wave network -Back up your Z-Wave controller's Non-Volatile Memory (NVM). The NVM contains your network information including paired devices. It's recommended to create a backup before making any major changes to your Z-Wave network. +It's recommended to create a backup before making any major changes to your Z-Wave network. For example, before migrating from one controller to another, or if you decide to switch from the Z-Wave JS add-on to the ZWaveJS UI add-on. The backup stores your Z-Wave controller's non-volatile memory (NVM). The NVM contains your network information including paired devices. It is stored in a binary file that you can download. + +### Prerequisites + +- Administrator rights in Home Assistant + +### To backup your Z-Wave network + +1. In Home Assistant, go to {% my integrations title="**Settings** > **Devices & services**" %}. +2. Select the **Z-Wave** integration. Then, select **Configure**. +3. Under **Backup and restore**, select **Download backup**. + - **Result**: The backup file is downloaded to the device from which you initiated the download. +4. Done! Store the backup file somewhere safe in case you need it later to restore your Z-Wave network. ## Special Z-Wave entities From 4114e28d682f9fa5752c5e4b28d441311cc89c09 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 Date: Thu, 12 Jun 2025 16:09:20 +0200 Subject: [PATCH 3/4] Fix use case example --- source/_integrations/zwave_js.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/zwave_js.markdown b/source/_integrations/zwave_js.markdown index b03bb3e46320..c98fbfc879d1 100644 --- a/source/_integrations/zwave_js.markdown +++ b/source/_integrations/zwave_js.markdown @@ -186,7 +186,7 @@ To migrate a Z-Wave network to a new controller, follow these steps: ## Backing up your Z-Wave network -It's recommended to create a backup before making any major changes to your Z-Wave network. For example, before migrating from one controller to another, or if you decide to switch from the Z-Wave JS add-on to the ZWaveJS UI add-on. The backup stores your Z-Wave controller's non-volatile memory (NVM). The NVM contains your network information including paired devices. It is stored in a binary file that you can download. +It's recommended to create a backup before making any major changes to your Z-Wave network. For example, before migrating from one controller to another, or before resetting your controller. The backup stores your Z-Wave controller's non-volatile memory (NVM). The NVM contains your network information including paired devices. It is stored in a binary file that you can download. ### Prerequisites From 6ec966394a8e850a9ea98dcfd2aa9fe008da0d4e Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Thu, 12 Jun 2025 21:04:30 +0200 Subject: [PATCH 4/4] Update source/_integrations/zwave_js.markdown Co-authored-by: AlCalzone --- source/_integrations/zwave_js.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/zwave_js.markdown b/source/_integrations/zwave_js.markdown index c98fbfc879d1..2f7de6f8bba9 100644 --- a/source/_integrations/zwave_js.markdown +++ b/source/_integrations/zwave_js.markdown @@ -186,7 +186,7 @@ To migrate a Z-Wave network to a new controller, follow these steps: ## Backing up your Z-Wave network -It's recommended to create a backup before making any major changes to your Z-Wave network. For example, before migrating from one controller to another, or before resetting your controller. The backup stores your Z-Wave controller's non-volatile memory (NVM). The NVM contains your network information including paired devices. It is stored in a binary file that you can download. +It's recommended to create a backup before making any major changes to your Z-Wave network. For example, before migrating from one controller to another, or before resetting your controller. The backup stores your Z-Wave controller's non-volatile memory (NVM), which contains your network information including paired devices. It is stored in a binary file that you can download. ### Prerequisites