Site updated at 2016-08-13 19:22:59 UTC
This commit is contained in:
Travis CI
parent
b043f25a3b
commit
f5b903f5ec
347 changed files with 6259 additions and 2708 deletions
|
|
@ -102,8 +102,8 @@
|
|||
<span class="comment"># Impacts weather/sunrise data (altitude above sea level) </span>
|
||||
<span class="key">elevation</span>: <span class="string"><span class="content">430</span></span>
|
||||
|
||||
<span class="comment"># C for Celsius, F for Fahrenheit</span>
|
||||
<span class="key">temperature_unit</span>: <span class="string"><span class="content">C</span></span>
|
||||
<span class="comment"># 'metric' for Metric, 'imperial' for Imperial</span>
|
||||
<span class="key">unit_system</span>: <span class="string"><span class="content">metric</span></span>
|
||||
|
||||
<span class="comment"># Pick yours from here:</span>
|
||||
<span class="comment"># http://en.wikipedia.org/wiki/List_of_tz_database_time_zones</span>
|
||||
|
|
|
|||
|
|
@ -125,6 +125,12 @@ Upon first run, the z-wave component will take time to initialize entities and e
|
|||
<td> </td>
|
||||
<td> </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>ZWave.me UZB1</td>
|
||||
<td>✓</td>
|
||||
<td> </td>
|
||||
<td> </td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
|
|
|||
|
|
@ -101,44 +101,6 @@ The option is commented out by default in <code>options.xml</code> and is a defa
|
|||
It is best to pair these devices in Open Zwave Control Panel or other Zwave tool that can show you logs while pairing. Test the device before you save the configuration.<br />
|
||||
Make sure you copy the newly saved <code>zwcfg_[home_id].xml</code>into your HomeAssistant config directory.</p>
|
||||
|
||||
<h5><a class="title-link" name="event-basic_level-for-automation" href="#event-basic_level-for-automation"></a> Event basic_level for automation</h5>
|
||||
<p>HomeAssistant will trigger a event when command_class_basic changes value on a node.<br />
|
||||
This can be virtually anything, so tests have to be made to determine what value equals what.<br />
|
||||
You can use this for automations.</p>
|
||||
|
||||
<p>Example:</p>
|
||||
|
||||
<div class="highlighter-coderay"><div class="CodeRay">
|
||||
<div class="code"><pre> - <span class="string"><span class="content">alias: Minimote Button Pressed</span></span>
|
||||
<span class="key">trigger</span>:
|
||||
<span class="key">platform</span>: <span class="string"><span class="content">event</span></span>
|
||||
<span class="key">event_type</span>: <span class="string"><span class="content">zwave.node_event</span></span>
|
||||
<span class="key">event_data</span>:
|
||||
<span class="key">object_id</span>: <span class="string"><span class="content">aeon_labs_minimote_1</span></span>
|
||||
<span class="key">basic_level</span>: <span class="string"><span class="content">255</span></span>
|
||||
</pre></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<h5><a class="title-link" name="event-scene_id-for-automation" href="#event-scene_id-for-automation"></a> Event scene_id for automation</h5>
|
||||
<p>HomeAssistant will trigger a event when a scene is activated by a node in the zwave network.<br />
|
||||
This can be a press of a button, so tests have to be made to determine what scene_id equals what.<br />
|
||||
You can use this for automations.</p>
|
||||
|
||||
<p>Example:</p>
|
||||
|
||||
<div class="highlighter-coderay"><div class="CodeRay">
|
||||
<div class="code"><pre> - <span class="string"><span class="content">alias: Minimote Button 1 Pressed</span></span>
|
||||
<span class="key">trigger</span>:
|
||||
<span class="key">platform</span>: <span class="string"><span class="content">event</span></span>
|
||||
<span class="key">event_type</span>: <span class="string"><span class="content">zwave.scene_activated</span></span>
|
||||
<span class="key">event_data</span>:
|
||||
<span class="key">object_id</span>: <span class="string"><span class="content">aeon_labs_minimote_1</span></span>
|
||||
<span class="key">scene_id</span>: <span class="string"><span class="content">1</span></span>
|
||||
</pre></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<h5><a class="title-link" name="aeon-minimote" href="#aeon-minimote"></a> Aeon Minimote</h5>
|
||||
|
||||
<p>Here’s a handy configuration for the Aeon Labs Minimote that defines all possible button presses. Put it into <code>automation.yaml</code>.</p>
|
||||
|
|
|
|||
|
|
@ -190,7 +190,77 @@ Depending on what’s plugged into your USB ports, the name found above may chan
|
|||
|
||||
<h4><a class="title-link" name="events" href="#events"></a> Events</h4>
|
||||
|
||||
<p>Some devices can also trigger scene activation events, which can be used in automation scripts (for example the press of a button on a wall switch):</p>
|
||||
<p><strong>zwave.network_complete</strong><br />
|
||||
HomeAssistant will trigger a event when the zwave network is complete. Meaning all of the nodes on the network have been queried. This can take quite som time, depending on wakeup intervals on the battery powered devices on the network.</p>
|
||||
|
||||
<div class="highlighter-coderay"><div class="CodeRay">
|
||||
<div class="code"><pre> - <span class="string"><span class="content">alias: ZWave network is complete</span></span>
|
||||
<span class="key">trigger</span>:
|
||||
<span class="key">platform</span>: <span class="string"><span class="content">event</span></span>
|
||||
<span class="key">event_type</span>: <span class="string"><span class="content">zwave.network_complete</span></span>
|
||||
</pre></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<p><strong>zwave.network_ready</strong><br />
|
||||
HomeAssistant will trigger a event when the zwave network is ready for use. Between <code>zwave.network_start</code> and <code>zwave.network_ready</code> HomeAssistant will feel sluggish when trying to send commands to zwave nodes. This is because the controller is requesting information from all of the nodes on the network. When this is triggered all awake nodes have been queried and sleeping nodes will be queried when they awake.</p>
|
||||
|
||||
<div class="highlighter-coderay"><div class="CodeRay">
|
||||
<div class="code"><pre> - <span class="string"><span class="content">alias: ZWave network is ready</span></span>
|
||||
<span class="key">trigger</span>:
|
||||
<span class="key">platform</span>: <span class="string"><span class="content">event</span></span>
|
||||
<span class="key">event_type</span>: <span class="string"><span class="content">zwave.network_ready</span></span>
|
||||
</pre></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<p><strong>zwave.network_start</strong><br />
|
||||
HomeAssistant will trigger a event when the zwave network is set up to be started.</p>
|
||||
|
||||
<div class="highlighter-coderay"><div class="CodeRay">
|
||||
<div class="code"><pre> - <span class="string"><span class="content">alias: ZWave network is starting</span></span>
|
||||
<span class="key">trigger</span>:
|
||||
<span class="key">platform</span>: <span class="string"><span class="content">event</span></span>
|
||||
<span class="key">event_type</span>: <span class="string"><span class="content">zwave.network_start</span></span>
|
||||
</pre></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<p><strong>zwave.network_stop</strong><br />
|
||||
HomeAssistant will trigger a event when the zwave network stopping.</p>
|
||||
|
||||
<div class="highlighter-coderay"><div class="CodeRay">
|
||||
<div class="code"><pre> - <span class="string"><span class="content">alias: ZWave network is stopping</span></span>
|
||||
<span class="key">trigger</span>:
|
||||
<span class="key">platform</span>: <span class="string"><span class="content">event</span></span>
|
||||
<span class="key">event_type</span>: <span class="string"><span class="content">zwave.network_start</span></span>
|
||||
</pre></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<p><strong>zwave.node_event</strong><br />
|
||||
HomeAssistant will trigger a event when command_class_basic changes value on a node.<br />
|
||||
This can be virtually anything, so tests have to be made to determine what value equals what.<br />
|
||||
You can use this for automations.</p>
|
||||
|
||||
<p>Example:</p>
|
||||
|
||||
<div class="highlighter-coderay"><div class="CodeRay">
|
||||
<div class="code"><pre> - <span class="string"><span class="content">alias: Minimote Button Pressed</span></span>
|
||||
<span class="key">trigger</span>:
|
||||
<span class="key">platform</span>: <span class="string"><span class="content">event</span></span>
|
||||
<span class="key">event_type</span>: <span class="string"><span class="content">zwave.node_event</span></span>
|
||||
<span class="key">event_data</span>:
|
||||
<span class="key">object_id</span>: <span class="string"><span class="content">aeon_labs_minimote_1</span></span>
|
||||
<span class="key">basic_level</span>: <span class="string"><span class="content">255</span></span>
|
||||
</pre></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<p>The <em>object_id</em> and <em>basic_level</em> of all triggered events can be seen in the console output.</p>
|
||||
|
||||
<p><strong>zwave.scene_activated</strong><br />
|
||||
Some devices can also trigger scene activation events, which can be used in automation scripts (for example the press of a button on a wall switch):</p>
|
||||
|
||||
<div class="highlighter-coderay"><div class="CodeRay">
|
||||
<div class="code"><pre><span class="comment"># Example configuration.yaml automation entry</span>
|
||||
|
|
@ -200,13 +270,13 @@ Depending on what’s plugged into your USB ports, the name found above may chan
|
|||
<span class="key">platform</span>: <span class="string"><span class="content">event</span></span>
|
||||
<span class="key">event_type</span>: <span class="string"><span class="content">zwave.scene_activated</span></span>
|
||||
<span class="key">event_data</span>:
|
||||
<span class="key">entity_id</span>: <span class="string"><span class="content">zwaveme_zme_wallcs_secure_wall_controller_8</span></span>
|
||||
<span class="key">object_id</span>: <span class="string"><span class="content">zwaveme_zme_wallcs_secure_wall_controller_8</span></span>
|
||||
<span class="key">scene_id</span>: <span class="string"><span class="content">11</span></span>
|
||||
</pre></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<p>The <em>entity_id</em> and <em>scene_id</em> of all triggered events can be seen in the console output.</p>
|
||||
<p>The <em>object_id</em> and <em>scene_id</em> of all triggered events can be seen in the console output.</p>
|
||||
|
||||
<h4><a class="title-link" name="services" href="#services"></a> Services</h4>
|
||||
|
||||
|
|
@ -225,13 +295,21 @@ Depending on what’s plugged into your USB ports, the name found above may chan
|
|||
<td>Put the zwave controller in inclusion mode. Allows one to add a new device to the zwave network.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>remove_node</td>
|
||||
<td>Put the zwave controller in exclusion mode. Allows one to remove a device from the zwave network.</td>
|
||||
<td>add_node_secure</td>
|
||||
<td>Put the zwave controller in secure inclusion mode. Allows one to add a new device with secure communications to the zwave network.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>cancel_command</td>
|
||||
<td>Cancels a running zwave 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>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>heal_network</td>
|
||||
<td>Tells the controller to “heal” the network. Bascially asks the nodes to tell the controller all of their neighbors so the controller can refigure out optimal routing.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>remove_node</td>
|
||||
<td>Put the zwave controller in exclusion mode. Allows one to remove a device from the zwave network.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>soft_reset</td>
|
||||
<td>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.</td>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue