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 <marhje52@gmail.com>
This commit is contained in:
Arno M 2021-11-09 04:03:48 -08:00 committed by GitHub
parent 3dc5b6b871
commit afd2eb5244
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -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. 2) Remove the Z-Wave integration from Home Assistant: Configuration --> Integrations --> Z-Wave (or OpenZWave) --> Press the three dots and click Delete.
<div class='note info'>
If you have configured Z-Wave manually, make sure to also remove the `zwave:` section from your `configuration.yaml`.
</div>
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. 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. 4) Restart your Home Assistant host. This step is important to make sure that your Z-Wave stick is released by the operating system.