jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Merge branch 'current' into next

Browse source
This commit is contained in:
Fabian Affolter 2017-12-15 10:11:27 +01:00
commit b064441866
No known key found for this signature in database
GPG key ID: DDF3D6F44AAB1336
13 changed files with 48 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

2
source/_docs/autostart/systemd.markdown
View file

@ -128,7 +128,7 @@ Because the log can scroll quite quickly, you can select to view only the error
$ sudo journalctl -f -u home-assistant@[your user] | grep -i 'error'
```
When working on Home Assitant, you can easily restart the system and then watch the log output by combining the above commands using `&&`
When working on Home Assistant, you can easily restart the system and then watch the log output by combining the above commands using `&&`
```bash
$ sudo systemctl restart home-assistant@[your user] && sudo journalctl -f -u home-assistant@[your user]

4
source/_docs/installation/windows.markdown
View file

@ -9,7 +9,7 @@ sharing: true
footer: true
---
To run Home Assistant on Microsoft Windows installation you need to install Python first. Download Python for https://www.python.org/downloads/windows/ and follow the instructions of the installer.
To run Home Assistant on Microsoft Windows installation you need to install Python first. Download Python for [https://www.python.org/downloads/windows/](https://www.python.org/downloads/windows/) and follow the instructions of the installer.
Start
@ -23,5 +23,5 @@ For autostarting Home Assistant please refer to this [guide](https://community.h
Check this [video](https://www.youtube.com/watch?v=X27eVvuqwnY) for the installation on Windows 10.
<p class='note warning'>
The Microsoft Windows platform is not a primary target to install home Assistant. Also, not all tools and third-party modules will work.
The Microsoft Windows platform is not a primary target to install Home Assistant. Also, not all tools and third-party modules will work.
</p>

2
source/_docs/z-wave.markdown
View file

@ -20,7 +20,7 @@ Before configuring the Z-Wave setup, please take a moment and read [this article
Z-Wave is a wireless communication protocol designed for home automation. It uses a low power, and low bandwidth, mesh network that allows devices that aren't within direct range of each other to communicate indirectly, via other nodes. Any device that's permanently powered (not battery powered) will help build the mesh, if you don't have enough powered devices, or you locate these poorly, your mesh will be unreliable.
There is a limit of 232 devices in a single Z-Wave network. If you need more devices then you could set up a second Home Assistant system with its own Z-Wave network and connect these with the [MQTT Eventstream](/components/mqtt_eventstream/) or [MQTT Statestream](/components/mqtt_statestream) components.
There is a limit of 232 devices in a single Z-Wave network. If you need more devices then you could set up a second Home Assistant system with its own Z-Wave network and connect these with the [MQTT Eventstream](/components/mqtt_eventstream/) or [MQTT Statestream](/components/mqtt_statestream) components. There is also a limit of 4 hops for Z-Wave, so placing the controller as centrally as you can is important.
The Z-Wave standard was improved with Z-Wave Plus, and if you only use Z-Wave plus devices then you will gain the full benefits.

2
source/_docs/z-wave/installation.markdown
View file

@ -159,7 +159,7 @@ To enable Z-Wave, plug your Z-Wave USB stick into your Raspberry Pi 3 and add th
```yaml
zwave:
usb_path: /dev/ttyACM0
usb_path: /dev/ttyAMA0
```
For some devices the `/dev/ttyAMA0` device is not detected by udev and is therefore not mapped by Docker. To explicitly set this device for mapping to Home-Assistant, execute the following command using the ssh add-on: