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

Merge pull request #4001 from home-assistant/release-0-58

Browse source 
0.58
This commit is contained in:
Paulus Schoutsen 2017-11-18 12:19:59 -08:00 • committed by GitHub
commit 559cfe67c7
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
55 changed files with 1612 additions and 121 deletions
Download patch file Download diff file Expand all files Collapse all files

1
source/_docs/ecosystem/ios/notifications/actions.markdown
View file

@ -141,3 +141,4 @@ Notes:
* `textInput` will only exist if `behavior` was set to `textInput`.
* `actionData` is a dictionary with parameters passed in the `action_data` dictionary of the `push` dictionary in the original notification.
* When adding or updating push categories be sure to update push settings within the Home Assistant iOS app. This can be found within the app at **Settings** (gear icon) > **Notification Settings**.

2
source/_docs/installation/hassbian/upgrading.markdown
View file

@ -1,7 +1,7 @@
---
layout: page
title: "Upgrading Hassbian"
description: "Instructions how to upgrade Hasbian to the latest version."
description: "Instructions how to upgrade Hassbian to the latest version."
date: 2016-09-26 21:00
sidebar: true
comments: false

1
source/_docs/mqtt/discovery.markdown
View file

@ -16,6 +16,7 @@ The discovery of MQTT devices will enable one to use MQTT devices with only mini
Supported by MQTT discovery:
- [Binary sensors](/components/binary_sensor.mqtt/)
- [Covers](/components/cover.mqtt/)
- [Fans](/components/fan.mqtt/)
- [Lights](/components/light.mqtt/)
- [Sensors](/components/sensor.mqtt/)

6
source/_docs/z-wave/control-panel.markdown
View file

@ -28,6 +28,7 @@ Here is where you [include and exclude](/docs/z-wave/adding/) Z-Wave devices fro
* **Stop Network** stops the Z-Wave network
* **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, and may cause the Z-Wave network to hang.
* **Test Network** tells the controller to send no-op commands to each node and measure the time for a response. In theory, this can also bring back nodes which have been marked "presumed dead".
* **Save Config** Saves the current cache of the network to zwcfg_[home_id].xml
## {% linkable_title Z-Wave Node Management %}
@ -38,6 +39,10 @@ Here is where you [include and exclude](/docs/z-wave/adding/) Z-Wave devices fro
* **Rename Node** sets a node's name - this won't happen immediately, and requires you to restart Home Assistant (not reboot) to set the new name
* **Heal Node** starts healing of the node.(Update neighbour list and update return routes)
* **Test Node** sends no_op test messages to the node. This could in theory bring back a dead node.
<p class='note'>
Battery powered devices need to be awake before you can use the Z-Wave control panel to update their settings. How to wake your device is device specific, and some devices will stay awake for only a couple of seconds. Please refer to the manual of your device for more details.
</p>
@ -107,4 +112,5 @@ Underneath that you can select any supported configuration parameter to see the
## {% linkable_title OZW Log %}
If you want to only retrieve some lines at the end of the log, you can specify that with the selection field. Max is the last 1000 lines and minimum is 0 which equals the whole log. If this is not specified, you will retrieve the whole log.
Select **Refresh** to display the log if you need it to check activities.

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

@ -18,6 +18,7 @@ The `zwave` component exposes multiple services to help maintain the network. Al
| cancel_command | Cancels a running Z-Wave command. If you have started a add_node or remove_node command, and decide you are not going to do it, then this must be used to stop the inclusion/exclusion command. |
| change_association | Add or remove an association in the Z-Wave network |
| heal_network | Tells the controller to "heal" the Z-Wave network. Basically asks the nodes to tell the controller all of their neighbors so the controller can refigure out optimal routing. |
| heal_node | Tells the controller to "heal" a specific node on the network. Requires `node_id` field. You can also force return route update with `return_routes` field.
| print_config_parameter | Prints Z-Wave node's config parameter value to the (console) log. |
| print_node | Print all states of Z-Wave node. |
| refresh_entity | Refresh the Z-Wave entity by refreshing dependent values. |
@ -33,6 +34,7 @@ The `zwave` component exposes multiple services to help maintain the network. Al
| start_network | Starts the Z-Wave network. |
| stop_network | Stops the Z-Wave network. |
| test_network | Tells the controller to send no-op commands to each node and measure the time for a response. In theory, this can also bring back nodes which have been marked "presumed dead." |
| test_node | Tells the controller to send no-op command(s) to a specific node. Requires `node_id` field. You can specify amount of test_messages to send by specifying it with `messages` field. In theory, this could bring back nodes marked as "presumed dead"
The `soft_reset` and `heal_network` commands can be used as part of an automation script to help keep a Z-Wave network running reliably as shown in the example below. By default, Home Assistant will run a `heal_network` at midnight. This is a configuration option for the `zwave` component. The option defaults to `true` but can be disabled by setting `autoheal` to false. If you're having issues with your Z-Wave network, try disabling this automation.