Site updated at 2017-11-18 20:42:08 UTC
This commit is contained in:
Travis CI
parent
374261cd52
commit
3bb0d0697f
641 changed files with 7982 additions and 2283 deletions
|
|
@ -196,6 +196,7 @@
|
|||
<ul>
|
||||
<li><code class="highlighter-rouge">textInput</code> will only exist if <code class="highlighter-rouge">behavior</code> was set to <code class="highlighter-rouge">textInput</code>.</li>
|
||||
<li><code class="highlighter-rouge">actionData</code> is a dictionary with parameters passed in the <code class="highlighter-rouge">action_data</code> dictionary of the <code class="highlighter-rouge">push</code> dictionary in the original notification.</li>
|
||||
<li>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 <strong>Settings</strong> (gear icon) > <strong>Notification Settings</strong>.</li>
|
||||
</ul>
|
||||
</article>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@
|
|||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
<title>Upgrading Hassbian - Home Assistant</title>
|
||||
<meta name="author" content="Home Assistant">
|
||||
<meta name="description" content="Instructions how to upgrade Hasbian to the latest version.">
|
||||
<meta name="description" content="Instructions how to upgrade Hassbian to the latest version.">
|
||||
<meta name="viewport" content="width=device-width">
|
||||
<link rel="canonical" href="https://home-assistant.io/docs/installation/hassbian/upgrading/">
|
||||
<meta property="fb:app_id" content="338291289691179">
|
||||
|
|
@ -16,12 +16,12 @@
|
|||
<meta property="og:site_name" content="Home Assistant">
|
||||
<meta property="og:url" content="https://home-assistant.io/docs/installation/hassbian/upgrading/">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:description" content="Instructions how to upgrade Hasbian to the latest version.">
|
||||
<meta property="og:description" content="Instructions how to upgrade Hassbian to the latest version.">
|
||||
<meta property="og:image" content="https://home-assistant.io/images/default-social.png">
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:site" content="@home_assistant">
|
||||
<meta name="twitter:title" content="Upgrading Hassbian">
|
||||
<meta name="twitter:description" content="Instructions how to upgrade Hasbian to the latest version.">
|
||||
<meta name="twitter:description" content="Instructions how to upgrade Hassbian to the latest version.">
|
||||
<meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
|
||||
<link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet">
|
||||
<link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">
|
||||
|
|
|
|||
|
|
@ -79,6 +79,7 @@
|
|||
<p>Supported by MQTT discovery:</p>
|
||||
<ul>
|
||||
<li><a href="/components/binary_sensor.mqtt/">Binary sensors</a></li>
|
||||
<li><a href="/components/cover.mqtt/">Covers</a></li>
|
||||
<li><a href="/components/fan.mqtt/">Fans</a></li>
|
||||
<li><a href="/components/light.mqtt/">Lights</a></li>
|
||||
<li><a href="/components/sensor.mqtt/">Sensors</a></li>
|
||||
|
|
|
|||
|
|
@ -92,6 +92,7 @@
|
|||
<li><strong>Stop Network</strong> stops the Z-Wave network</li>
|
||||
<li><strong>Soft Reset</strong> 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.</li>
|
||||
<li><strong>Test Network</strong> 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”.</li>
|
||||
<li><strong>Save Config</strong> Saves the current cache of the network to zwcfg_[home_id].xml</li>
|
||||
</ul>
|
||||
<h2><a class="title-link" name="z-wave-node-management" href="#z-wave-node-management"></a> Z-Wave Node Management</h2>
|
||||
<ul>
|
||||
|
|
@ -101,7 +102,13 @@
|
|||
<li>
|
||||
<p><strong>Print Node</strong> prints all state of Z-Wave node to the console log</p>
|
||||
</li>
|
||||
<li><strong>Rename Node</strong> sets a node’s name - this won’t happen immediately, and requires you to restart Home Assistant (not reboot) to set the new name</li>
|
||||
<li>
|
||||
<p><strong>Rename Node</strong> sets a node’s name - this won’t happen immediately, and requires you to restart Home Assistant (not reboot) to set the new name</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>Heal Node</strong> starts healing of the node.(Update neighbour list and update return routes)</p>
|
||||
</li>
|
||||
<li><strong>Test Node</strong> sends no_op test messages to the node. This could in theory bring back a dead node.</li>
|
||||
</ul>
|
||||
<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.
|
||||
|
|
@ -157,7 +164,8 @@ Battery powered devices need to be awake before you can use the Z-Wave control p
|
|||
<p>You can set the <em>wakeup</em> interval (in seconds) of the device, this is shown for all devices that can be battery powered, even if they are currently mains powered. The wakeup interval only applies when those devices are battery powered.</p>
|
||||
<p>Underneath that you can select any supported configuration parameter to see the current setting. You can then change this and select <strong>Set Config Parameter</strong> to updated it. Battery powered devices will be updated the next time they wake.</p>
|
||||
<h2><a class="title-link" name="ozw-log" href="#ozw-log"></a> OZW Log</h2>
|
||||
<p>Select <strong>Refresh</strong> to display the log if you need it to check activities.</p>
|
||||
<p>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 <strong>Refresh</strong> to display the log if you need it to check activities.</p>
|
||||
</article>
|
||||
</div>
|
||||
<aside id="sidebar" class="grid__item one-third lap-one-whole palm-one-whole">
|
||||
|
|
|
|||
|
|
@ -104,6 +104,10 @@
|
|||
<td>heal_network</td>
|
||||
<td>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.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>heal_node</td>
|
||||
<td>Tells the controller to “heal” a specific node on the network. Requires <code class="highlighter-rouge">node_id</code> field. You can also force return route update with <code class="highlighter-rouge">return_routes</code> field.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>print_config_parameter</td>
|
||||
<td>Prints Z-Wave node’s config parameter value to the (console) log.</td>
|
||||
|
|
@ -164,6 +168,10 @@
|
|||
<td>test_network</td>
|
||||
<td>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.”</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>test_node</td>
|
||||
<td>Tells the controller to send no-op command(s) to a specific node. Requires <code class="highlighter-rouge">node_id</code> field. You can specify amount of test_messages to send by specifying it with <code class="highlighter-rouge">messages</code> field. In theory, this could bring back nodes marked as “presumed dead”</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p>The <code class="highlighter-rouge">soft_reset</code> and <code class="highlighter-rouge">heal_network</code> 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 <code class="highlighter-rouge">heal_network</code> at midnight. This is a configuration option for the <code class="highlighter-rouge">zwave</code> component. The option defaults to <code class="highlighter-rouge">true</code> but can be disabled by setting <code class="highlighter-rouge">autoheal</code> to false. If you’re having issues with your Z-Wave network, try disabling this automation.</p>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue