From afd2eb5244ff2b46d096ef3e1b69280aad3af86b Mon Sep 17 00:00:00 2001 From: Arno M Date: Tue, 9 Nov 2021 04:03:48 -0800 Subject: [PATCH] Clarify zwave migration for zwave_js (#20189) * Update zwave_js.markdown I had a old config in which I still had the manual config entry in the configuration file. If you do not remove it, zwave simply comes back after reboot. This change makes the user aware of this case. * Update zwave_js.markdown Fixed zwave to 'zwave' per linter error * Fix note and adjust language * Fix note div render Co-authored-by: Martin Hjelmare --- source/_integrations/zwave_js.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/_integrations/zwave_js.markdown b/source/_integrations/zwave_js.markdown index 54a726a6ea0..401b168d810 100644 --- a/source/_integrations/zwave_js.markdown +++ b/source/_integrations/zwave_js.markdown @@ -515,6 +515,12 @@ There is no automatic migration wizard for the `ozw` integration. Please follow 2) Remove the Z-Wave integration from Home Assistant: Configuration --> Integrations --> Z-Wave (or OpenZWave) --> Press the three dots and click Delete. +
+ + If you have configured Z-Wave manually, make sure to also remove the `zwave:` section from your `configuration.yaml`. + +
+ 3) If you were running the OpenZWave beta, make sure to stop (or even remove) the OpenZWave add-on, also make sure it doesn't start automatically at startup. 4) Restart your Home Assistant host. This step is important to make sure that your Z-Wave stick is released by the operating system.