Merge branch 'current' into next

This commit is contained in:
Fabian Affolter 2017-09-30 13:30:14 +02:00
commit c8ec8391f4
No known key found for this signature in database
GPG key ID: DDF3D6F44AAB1336
190 changed files with 787 additions and 379 deletions

View file

@ -25,7 +25,7 @@ Windows users start [Putty][ssh-putty], enter the IP address of the Raspberry Pi
Optionally, starting with Windows 10 anniversary update, you can use the built-in '[Bash on Windows][bash-windows]' to use SSH if you have enabled Developer mode and have installed the "Windows Subsystem for Linux (beta)" feature.
### {% linkable_title Start/Stop/Restart Home Assistant %}
Log in as the `pi` account account and execute the following commands:
Log in as the `pi` account and execute the following commands:
```bash
$ sudo systemctl stop home-assistant@homeassistant.service

View file

@ -192,7 +192,7 @@ Make the daemon file executable:
# chmod 777 /volume1/homeassistant/hass-daemon
```
Update your firewall (if it is turned on on the Synology device):
Update your firewall (if it is turned on the Synology device):
- Go to your Synology control panel
- Go to security

View file

@ -9,7 +9,7 @@ sharing: true
footer: true
---
The command-line and the frontend which simplify common tasks, are helping with migrations, and ensure that Home Assistant runs properly. Please do not confuse those with with Home Assistant's [script](/docs/scripts/) feature.
The command-line and the frontend which simplify common tasks, are helping with migrations, and ensure that Home Assistant runs properly. Please do not confuse those with Home Assistant's [script](/docs/scripts/) feature.
### {% linkable_title Configuration check %}

View file

@ -230,7 +230,8 @@ The `zwave` component exposes multiple services to help maintain the network.
| remove_failed_node | Remove a failed node from the network. The Node should be on the controller's Failed Node List, otherwise this command will fail.|
| replace_failed_node | Replace a failed device with another. If the node is not in the controller's Failed Node List, or the node responds, this command will fail.|
| reset_node_meters | Reset a node's meter values. Only works if the node supports this. |
| set_config_parameter | Lets the user set a config parameter to a node. NOTE: Use string for list values. For all others use integer. |
| set_config_parameter | Lets the user set a config parameter to a node. NOTE: Use the parameter option's `label` string as the `value` for list parameters (e.g. `"value": "Off"`). For all other parameters use the relevant integer `value` (e.g. `"value": 1`). |
| set_poll_intensity | Lets the user set the polling intensity of a value. Changes the polling intensity without the need of a restart. This does not persist over restarts. To keep the setting over restarts, use the Z-Wave entity-card to set the config also.
| soft_reset | Tells the controller to do a "soft reset." This is not supposed to lose any data, but different controllers can behave differently to a "soft reset" command.|
| start_network | Starts the Z-Wave network.|
| stop_network | Stops the Z-Wave network.|