Site updated at 2016-10-22 22:37:41 UTC
This commit is contained in:
parent
ab857e95a7
commit
860912100c
408 changed files with 11332 additions and 1691 deletions
|
@ -98,12 +98,12 @@ These devices will either show as a binary sensor or a sensor called <code class
|
|||
|
||||
<p>The following parameters can be entered:</p>
|
||||
<ul>
|
||||
<li><strong>entity_id</strong> (<em>Required</em>): The entity_id of the device that you are going to set a parameter to. Any entity_id of the node can be used.</li>
|
||||
<li><strong>node_id</strong> (<em>Required</em>): The node_id of the device that you are going to set a parameter to.</li>
|
||||
<li><strong>parameter</strong> (<em>Required</em>): The index number of the parameter to be set. Refer to device manual or zwcfg_[home_id].xml</li>
|
||||
<li><strong>value</strong> (<em>Required</em>): The value to set the parameter to. Refer to device manual or zwcfg_[home_id].xml</li>
|
||||
<li><strong>size</strong> (<em>Optional</em>): The size of the value. It is normally not needed to specify this parameter, but in some cases it’s needed. Check OZW.log for details on this.
|
||||
You should check OZW.log to see if setting has been set
|
||||
Example entry in dev-service, setting binary report for Aeotec multisensor 6:
|
||||
You should check OZW.log to see if your new setting has been set
|
||||
Example entry in dev-service, setting binary reports for an Aeotec Multisensor 6:
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example entry in dev-service</span>
|
||||
<span class="pi">{</span><span class="s2">"</span><span class="s">entity_id"</span><span class="pi">:</span> <span class="s2">"</span><span class="s">sensor.aetoec_multisensor_6_luminance_5"</span><span class="pi">,</span>
|
||||
<span class="s2">"</span><span class="s">parameter"</span><span class="pi">:</span> <span class="s2">"</span><span class="s">5"</span><span class="pi">,</span>
|
||||
|
@ -116,10 +116,10 @@ Example entry in dev-service, setting binary report for Aeotec multisensor 6:
|
|||
|
||||
<h5><a class="title-link" name="locks-and-other-secure-devices" href="#locks-and-other-secure-devices"></a> Locks and other secure devices</h5>
|
||||
|
||||
<p>These devices require a network key to be set for the Z-Wave network before they are paired. This key is set in OpenZwave’s <code class="highlighter-rouge">options.xml</code> which is located in OpenZWave’s directory. This should also be the same directory as <code class="highlighter-rouge">config_path:</code> in your <code class="highlighter-rouge">configuration.yaml</code>. If it’s not, make sure you have the same values in all the files you are using.
|
||||
<p>These devices require a network key to be set for the Z-Wave network before they are paired. This key is set in OpenZWave’s <code class="highlighter-rouge">options.xml</code> which is located in OpenZWave’s directory. This should also be the same directory as <code class="highlighter-rouge">config_path:</code> in your <code class="highlighter-rouge">configuration.yaml</code>. If it’s not, make sure you have the same values in all the files you are using.
|
||||
The option is commented out by default in <code class="highlighter-rouge">options.xml</code> and is a default key. Make your own unique key. The key is in Hexadecimals.
|
||||
It is best to pair these devices in OpenZWave Control Panel or other Z-wave tool that can show you logs while pairing. Home Assistant show logs from zwave too and it is <code class="highlighter-rouge">OZW.log</code> in the Home Assistant config directory.
|
||||
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</code> when the device is paired secure successfully. If you use Open Zwave Control Panel to pair, test the device before you save the configuration.
|
||||
It is best to pair these devices in OpenZWave Control Panel or another Z-Wave tool that can show you logs while pairing. Home Assistant stores logs from Z-Wave in <code class="highlighter-rouge">OZW.log</code> in the Home Assistant config directory.
|
||||
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</code> when the device is paired successfully with a secure connection. If you use OpenZWave Control Panel to pair, test the device before you save the configuration.
|
||||
Make sure you copy the newly saved <code class="highlighter-rouge">zwcfg_[home_id].xml</code>into your Home Assistant configuration directory.</p>
|
||||
|
||||
<h5><a class="title-link" name="aeon-minimote" href="#aeon-minimote"></a> Aeon Minimote</h5>
|
||||
|
|
|
@ -156,7 +156,8 @@ Instead of <code class="highlighter-rouge">make install</code>, you can alternat
|
|||
<li><strong>polling_interval</strong> (<em>Optional</em>): The time period in milliseconds between polls of a nodes value. Be careful about using polling values below 30000 (30 seconds) as polling can flood the zwave network and cause problems.</li>
|
||||
<li><strong>customize</strong> (<em>Optional</em>): This attribute contains node-specific override values:
|
||||
<ul>
|
||||
<li><strong>polling_intensity</strong> (<em>Optional</em>): Enables polling of a value and sets the frequency of polling (0=none, 1=every time through the list, 2-every other time, etc). If not specified then your device will not be polled.</li>
|
||||
<li><strong>polling_intensity</strong> (<em>Optional</em>): Enables polling of a value and sets the frequency of polling (0=none, 1=every time through the list, 2=every other time, etc). If not specified then your device will not be polled.</li>
|
||||
<li><strong>ignored</strong> (<em>Optional</em>): Ignore this entitiy completely. It won’t be shown in the Web Interface and no events are generated for it.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
@ -295,7 +296,7 @@ You can use this for automations.</p>
|
|||
|
||||
<h3><a class="title-link" name="services" href="#services"></a> Services</h3>
|
||||
|
||||
<p>The <code class="highlighter-rouge">zwave</code> component exposes ten services to help maintain the network.</p>
|
||||
<p>The <code class="highlighter-rouge">zwave</code> component exposes multiple services to help maintain the network.</p>
|
||||
|
||||
<table>
|
||||
<thead>
|
||||
|
@ -313,6 +314,10 @@ You can use this for automations.</p>
|
|||
<td>add_node_secure</td>
|
||||
<td>Put the Z-Wave controller in secure inclusion mode. Allows one to add a new device with secure communications to the Z-Wave network.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>association</td>
|
||||
<td>Add or remove an association in th Z-Wave network</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>cancel_command</td>
|
||||
<td>Cancels a running Z-Wave command. If you have started a add_node or remove_node command, and decides you are not going to do it, then this must be used to stop the inclusion/exclusion command.</td>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue