Site updated at 2017-07-16 05:06:47 UTC
This commit is contained in:
parent
477f499ed2
commit
3738c7d54a
524 changed files with 8458 additions and 2098 deletions
|
@ -106,22 +106,25 @@
|
|||
<ul>
|
||||
<li><strong>name</strong> (<em>Optional</em>): Name for the device, defaults to Rflink ID.</li>
|
||||
<li><strong>type</strong> (<em>Optional</em>): Override automatically detected type of the light device, can be: switchable, dimmable, hybrid or toggle. See ‘Light Types’ below. (default: Switchable)</li>
|
||||
<li><strong>aliasses</strong> (<em>Optional</em>): Alternative Rflink ID’s this device is known by.</li>
|
||||
<li><strong>aliases</strong> (<em>Optional</em>): Alternative Rflink ID’s this device is known by.</li>
|
||||
<li><strong>fire_event</strong> (<em>Optional</em>): Fire an <code class="highlighter-rouge">button_pressed</code> event if this device is turned on or off (default: False).</li>
|
||||
<li><strong>signal_repetitions</strong> (<em>Optional</em>): Repeat every Rflink command this number of times (default: 1).</li>
|
||||
<li><strong>fire_event_</strong> (<em>Optional</em>): Set default <code class="highlighter-rouge">fire_event</code> for RFLink switch devices (see below).</li>
|
||||
<li><strong>signal_repetitions</strong> (<em>Optional</em>): Set default <code class="highlighter-rouge">signal_repetitions</code> for RFLink switch devices (see below).</li>
|
||||
<li><strong>group</strong> (<em>Optional</em>): Allow light to respond to group commands (ALLON/ALLOFF). (default: yes)</li>
|
||||
<li><strong>group_aliases</strong> (<em>Optional</em>): <code class="highlighter-rouge">aliases</code> which only respond to group commands.</li>
|
||||
<li><strong>no_group_aliases</strong> (<em>Optional</em>): <code class="highlighter-rouge">aliases</code> which do not respond to group commands.</li>
|
||||
</ul>
|
||||
<h3><a class="title-link" name="light-state" href="#light-state"></a> Light state</h3>
|
||||
<p>Initially the state of a light is unknown. When the light is turned on or off (via frontend or remote) the state is known and will be shown in the frontend.</p>
|
||||
<p>Sometimes a light is controlled by multiple remotes, each remote has its own code programmed in the light. To allow tracking of the state when switched via other remotes add the corresponding remote codes as aliasses:</p>
|
||||
<p>Sometimes a light is controlled by multiple remotes, each remote has its own code programmed in the light. To allow tracking of the state when switched via other remotes add the corresponding remote codes as aliases:</p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
|
||||
<span class="s">light</span><span class="pi">:</span>
|
||||
<span class="pi">-</span> <span class="s">platform</span><span class="pi">:</span> <span class="s">rflink</span>
|
||||
<span class="s">devices</span><span class="pi">:</span>
|
||||
<span class="s">newkaku_0000c6c2_1</span><span class="pi">:</span>
|
||||
<span class="s">name</span><span class="pi">:</span> <span class="s">Living room</span>
|
||||
<span class="s">aliasses</span><span class="pi">:</span>
|
||||
<span class="s">aliases</span><span class="pi">:</span>
|
||||
<span class="pi">-</span> <span class="s">newkaku_000000001_2</span>
|
||||
<span class="pi">-</span> <span class="s">kaku_000001_a</span>
|
||||
<span class="s">Ansluta_ce30_0</span><span class="pi">:</span>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue