Site updated at 2017-04-08 23:38:08 UTC
This commit is contained in:
parent
0b450989d5
commit
b671c3bdf9
536 changed files with 6498 additions and 1728 deletions
|
@ -69,14 +69,6 @@
|
|||
<p>The <code class="highlighter-rouge">rflink</code> component support devices that use <a href="http://www.nemcon.nl/blog2/">RFLink gateway firmware</a>, for example the <a href="https://www.nodo-shop.nl/nl/21-rflink-gateway">Nodo RFLink Gateway</a>. RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).</p>
|
||||
<p>First you have to set up your <a href="/components/rflink/">rflink hub</a>.</p>
|
||||
<p>After configuring the RFLink hub lights will be automatically discovered and added.</p>
|
||||
<p>New/unknown lights can be assigned to a default group automatically by specifying the <code class="highlighter-rouge">new_devices_group</code> option with a group name. If the group doesn’t exist it will be created.</p>
|
||||
<p>For example:</p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
|
||||
<span class="s">sensor</span><span class="pi">:</span>
|
||||
<span class="s">platform</span><span class="pi">:</span> <span class="s">rflink</span>
|
||||
<span class="s">new_devices_group</span><span class="pi">:</span> <span class="s2">"</span><span class="s">New</span><span class="nv"> </span><span class="s">Rflink</span><span class="nv"> </span><span class="s">Lights"</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
<p>RFLink switch/light ID’s are composed of: protocol, id, switch. For example: <code class="highlighter-rouge">newkaku_0000c6c2_1</code>.</p>
|
||||
<p>Once the ID of a light is known it can be used to configure the light in HA, for example to add it to a different group, hide it or configure a nice name.</p>
|
||||
<p>Configuring a device as light with a nice name:</p>
|
||||
|
@ -93,8 +85,8 @@
|
|||
</div>
|
||||
<p>Configuration variables:</p>
|
||||
<ul>
|
||||
<li><strong>automatic_add</strong> (<em>Optional</em>): Automatically add new/unconfigured devices to HA if detected (default: True).</li>
|
||||
<li><strong>devices</strong> (<em>Optional</em>): A list of devices with their name to use in the frontend.</li>
|
||||
<li><strong>new_devices_group</strong> (<em>Optional</em>): Create group to add new/unknown devices to.</li>
|
||||
<li><strong>device_defaults</strong>: (<em>Optional</em>)
|
||||
<ul>
|
||||
<li><strong>fire_event</strong> (<em>Optional</em>): Set default <code class="highlighter-rouge">fire_event</code> for Rflink switch devices (see below).</li>
|
||||
|
@ -143,7 +135,7 @@
|
|||
<h3><a class="title-link" name="hidingignoring-lights" href="#hidingignoring-lights"></a> Hiding/ignoring lights</h3>
|
||||
<p>Lights are added automatically when the RFLink gateway intercepts a wireless command in the ether. To prevent cluttering the frontend use any of these methods:</p>
|
||||
<ul>
|
||||
<li>Configure a <code class="highlighter-rouge">new_devices_group</code> for lights and optionally add it to a different <code class="highlighter-rouge">view</code>.</li>
|
||||
<li>Disable automatically adding of unconfigured new sensors (set <code class="highlighter-rouge">automatic_add</code> to <code class="highlighter-rouge">false</code>).</li>
|
||||
<li>Hide unwanted devices using <a href="/getting-started/customizing-devices/">customizations</a></li>
|
||||
<li><a href="/components/rflink/#ignoring-devices">Ignore devices on a platform level</a></li>
|
||||
</ul>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue