Site updated at 2016-08-13 19:22:59 UTC
This commit is contained in:
parent
b043f25a3b
commit
f5b903f5ec
347 changed files with 6259 additions and 2708 deletions
|
@ -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>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue