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

Site updated at 2018-01-25 17:33:45 UTC

Browse source
This commit is contained in:
Travis CI 2018-01-25 17:33:45 +00:00
parent 2a429df2b2
commit 94552b64db
144 changed files with 304 additions and 301 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/z-wave/adding/index.html
View file

@ -81,7 +81,7 @@
<li>Go to the <a href="/docs/z-wave/control-panel/">Z-Wave control panel</a> in the Home Assistant frontend</li>
<li>Click the <strong>Add Node</strong> button in the <em>Z-Wave Network Management</em> card - this will place the controller in inclusion mode</li>
<li>Activate your device to be included by following the instructions provided with the device</li>
<li>With the device in its final location, run a <em>Heal</em></li>
<li>With the device in its final location, run a <em>Heal Network</em></li>
</ol>
<p>Don’t use this for <a href="https://home-assistant.io/docs/z-wave/adding/#adding-secure-devices">secure devices</a>, since this is likely to limit the features the device supports.</p>
<p class="note warning">
@ -115,6 +115,7 @@ Ensure you keep a backup of this key. If you have to rebuild your system and don
<li>Go to the <a href="/docs/z-wave/control-panel/">Z-Wave control panel</a> in the Home Assistant frontend</li>
<li>Click the <strong>Add Node Secure</strong> button in the <em>Z-Wave Network Management</em> card - this will place the controller in inclusion mode</li>
<li>Activate your device to be included by following the instructions provided with the device</li>
<li>With the device in its final location, run a <em>Heal Network</em></li>
</ol>
<h2><a class="title-link" name="removing-devices" href="#removing-devices"></a> Removing Devices</h2>
<p>To remove (exclude) a Z-Wave device from your system:</p>
@ -122,7 +123,7 @@ Ensure you keep a backup of this key. If you have to rebuild your system and don
<li>Go to the Z-Wave control panel in the Home Assistant frontend</li>
<li>Click the <strong>Remove Node</strong> button in the <em>Z-Wave Network Management</em> card - this will place the controller in exclusion mode</li>
<li>Activate your device to be excluded by following the instructions provided with the device</li>
<li>With the device in its final location, run a <em>Heal</em></li>
<li>Run a <em>Heal Network</em> so all the other nodes learn about its removal</li>
</ol>
</article>
</div>

4
docs/z-wave/control-panel/index.html
View file

@ -106,7 +106,7 @@
<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>
<p><strong>Heal Node</strong> starts healing of the node.(Update neighbor 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>
@ -165,7 +165,7 @@ 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="node-user-codes" href="#node-user-codes"></a> Node user codes</h2>
<p>If your node has user codes, you can set and delete them. The format is raw hex Ascii code. Bellow the input you will see your actual code. For normal nodes this is as follows:</p>
<p>If your node has user codes, you can set and delete them. The format is raw hex Ascii code. Below the input you will see your actual code. For normal nodes this is as follows:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">\x30 = 0</span>
<span class="s">\x31 = 1</span>
<span class="s">\x32 = 2</span>

2
docs/z-wave/device-specific/index.html
View file

@ -85,7 +85,7 @@ These devices will either show as a binary sensor or a sensor called <code class
<p>Home Assistant stores logs from Z-Wave in <code class="highlighter-rouge">OZW_log.txt</code> in the Home Assistant config directory, when you pair a secure device you should see communication from the node with lines starting with <code class="highlighter-rouge">info: NONCES</code> in <code class="highlighter-rouge">OZW_log.txt</code> when the device is paired successfully with a secure connection.</p>
<h3><a class="title-link" name="specific-devices" href="#specific-devices"></a> Specific Devices</h3>
<h3><a class="title-link" name="aeotec-z-stick" href="#aeotec-z-stick"></a> Aeotec Z-Stick</h3>
<p>It’s totally normal for your Z-Wave stick to cycle through its LEDs (Yellow, Blue and Red) while plugged into your system. If you don’t like this behaviour it can be turned off.</p>
<p>It’s totally normal for your Z-Wave stick to cycle through its LEDs (Yellow, Blue and Red) while plugged into your system. If you don’t like this behavior it can be turned off.</p>
<p>Use the following example commands from a terminal session on your Pi where your Z-Wave stick is connected.</p>
<p>Turn off “Disco lights”:</p>
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span><span class="nb">echo</span> -e -n <span class="s2">"</span><span class="se">\x</span><span class="s2">01</span><span class="se">\x</span><span class="s2">08</span><span class="se">\x</span><span class="s2">00</span><span class="se">\x</span><span class="s2">F2</span><span class="se">\x</span><span class="s2">51</span><span class="se">\x</span><span class="s2">01</span><span class="se">\x</span><span class="s2">00</span><span class="se">\x</span><span class="s2">05</span><span class="se">\x</span><span class="s2">01</span><span class="se">\x</span><span class="s2">51"</span> &gt; /dev/serial/by-id/usb-0658_0200-if00

4
docs/z-wave/installation/index.html
View file

@ -85,7 +85,7 @@
</code></pre>
</div>
<p class="note">
The installation of python-openzwave happens when you first enable the Z-Wave component, and can take half an hour or more on a Raspbery Pi.
The installation of python-openzwave happens when you first enable the Z-Wave component, and can take half an hour or more on a Raspberry Pi.
</p>
<h2><a class="title-link" name="configuration" href="#configuration"></a> Configuration</h2>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
@ -228,7 +228,7 @@ The device type is <code class="highlighter-rouge">c</code> (character special)
</div>
<p>Ensure you keep a backup of this key. If you have to rebuild your system and don’t have a backup of this key, you won’t be able to reconnect to any security devices. This may mean you have to do a factory reset on those devices, and your controller, before rebuilding your Z-Wave network.</p>
<h2><a class="title-link" name="first-run" href="#first-run"></a> First Run</h2>
<p>The (compilation and) installation of python-openzwave happens when you first enable the Z-Wave component, and can take half an hour or more on a Raspbery Pi. When you upgrade Home Assistant and python-openzwave is also upgraded, this will also result in a delay while the new version is compiled and installed.</p>
<p>The (compilation and) installation of python-openzwave happens when you first enable the Z-Wave component, and can take half an hour or more on a Raspberry Pi. When you upgrade Home Assistant and python-openzwave is also upgraded, this will also result in a delay while the new version is compiled and installed.</p>
<p>The first run after adding a device is when the <code class="highlighter-rouge">zwave</code> component will take time to initialize the entities, some entities may appear with incomplete names. Running a network heal may speed up this process.</p>
<h2><a class="title-link" name="troubleshooting" href="#troubleshooting"></a> Troubleshooting</h2>
<h3><a class="title-link" name="component-could-not-be-set-up" href="#component-could-not-be-set-up"></a> Component could not be set up</h3>