Remove duplicate Z-Wave docs (#15543)

These docs mostly duplicate what is in the main Z-Wave docs; they even link to those docs at the end of the page.

I propose we remove it entirely and just redirect to the main Z-Wave docs for any stale links.
This commit is contained in:
Adam Ernst 2020-11-06 12:58:10 -06:00 committed by GitHub
parent 00b9e34b03
commit 0b6d543a23
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 1 additions and 65 deletions

View File

@ -18,7 +18,6 @@
Advanced Advanced
<ul> <ul>
<li>{% active_link /hassio/commandline/ Command line %}</li> <li>{% active_link /hassio/commandline/ Command line %}</li>
<li>{% active_link /hassio/zwave/ Z-Wave %}</li>
<li>{% active_link /hassio/enable_i2c/ Enable I2C %}</li> <li>{% active_link /hassio/enable_i2c/ Enable I2C %}</li>
</ul> </ul>
</li> </li>

View File

@ -2097,6 +2097,7 @@
/getting-started/z-wave-installation /docs/z-wave/installation /getting-started/z-wave-installation /docs/z-wave/installation
/getting-started/z-wave-panel /docs/z-wave/control-panel /getting-started/z-wave-panel /docs/z-wave/control-panel
/getting-started/z-wave-device-specific /docs/z-wave/device-specific /getting-started/z-wave-device-specific /docs/z-wave/device-specific
/hassio/zwave /docs/z-wave
/topics/events /docs/configuration/events /topics/events /docs/configuration/events
/topics/packages /docs/configuration/packages /topics/packages /docs/configuration/packages
/topics/platform_options /docs/configuration/platform_options /topics/platform_options /docs/configuration/platform_options

View File

@ -1,64 +0,0 @@
---
title: "Z-Wave"
description: "Instructions on how-to enable Z-Wave with Hass.io."
---
To enable Z-Wave, plug your Z-Wave USB stick into your Raspberry Pi 3 and add the following to your `configuration.yaml`:
```yaml
zwave:
usb_path: /dev/ttyACM0
```
## RAZBERRY BOARD
If you need GPIO on Raspberry Pi 3 for your Z-Wave module, add the following line into `config.txt` (you have to access that on the SD card directly. Simply plug it into your PC and edit it there.
The `config.txt` is not accessible from the Home Assistant Operating System, you may need to open the SD card on a Windows or Linux system:
```txt
dtoverlay=pi3-miniuart-bt
```
After that, you need to change `usb_path` to `/dev/ttyAMA0` in your `configuration.yaml`.
```yaml
zwave:
usb_path: /dev/ttyAMA0
```
## HUSBZB-1
```yaml
zwave:
usb_path: /dev/ttyUSB0
zha:
usb_path: /dev/ttyUSB1
database_path: /config/zigbee.db
```
## Ubuntu and Debian based host system
If your instance is running on a Debian-based system, e.g., Ubuntu, the ModemManager may cause unexpected issues.
The ModemManager might be claiming or interfering with a USB Z-Wave stick, like the much used Aeotec ones. If you experience issues where the stick stops responding, needs to be re-plugged or Home Assistant needs a restart to get Z-Wave back, chances are high that the ModemManager is causing the issue.
Execute the following command on your host system to disable the ModemManager:
```bash
systemctl disable ModemManager.service
```
### Finding the path
If the above defaults don't work, you can check what hardware has been found using the [`ha` command](/hassio/commandline/#hardware):
```bash
ha hardware info
```
Or you can use the UI and look in the *System* section of the *Supervisor* menu. There you'll find a *Hardware* button which will list all the hardware found.
## Further reading
For more information on using Z-Wave, see the [main documentation](/docs/z-wave/).