Site updated at 2017-03-24 20:36:00 UTC
This commit is contained in:
Travis CI
parent
5134ca897a
commit
c67e006da9
227 changed files with 677 additions and 654 deletions
|
|
@ -6,22 +6,22 @@
|
|||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
<title>Rflink Light - Home Assistant</title>
|
||||
<title>RFLink Light - Home Assistant</title>
|
||||
<meta name="author" content="Home Assistant">
|
||||
<meta name="description" content="Instructions how to integrate Rflink lights into Home Assistant.">
|
||||
<meta name="description" content="Instructions how to integrate RFLink lights into Home Assistant.">
|
||||
<meta name="viewport" content="width=device-width">
|
||||
<link rel="canonical" href="https://home-assistant.io/components/light.rflink/">
|
||||
<meta property="fb:app_id" content="338291289691179">
|
||||
<meta property="og:title" content="Rflink Light">
|
||||
<meta property="og:title" content="RFLink Light">
|
||||
<meta property="og:site_name" content="Home Assistant">
|
||||
<meta property="og:url" content="https://home-assistant.io/components/light.rflink/">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:description" content="Instructions how to integrate Rflink lights into Home Assistant.">
|
||||
<meta property="og:description" content="Instructions how to integrate RFLink lights into Home Assistant.">
|
||||
<meta property="og:image" content="https://home-assistant.io/images/default-social.png">
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:site" content="@home_assistant">
|
||||
<meta name="twitter:title" content="Rflink Light">
|
||||
<meta name="twitter:description" content="Instructions how to integrate Rflink lights into Home Assistant.">
|
||||
<meta name="twitter:title" content="RFLink Light">
|
||||
<meta name="twitter:description" content="Instructions how to integrate RFLink lights into Home Assistant.">
|
||||
<meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
|
||||
<link href="/stylesheets/screen.css" media="screen, projection" rel="stylesheet">
|
||||
<link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">
|
||||
|
|
@ -62,13 +62,13 @@
|
|||
<article class="page">
|
||||
<header>
|
||||
<h1 class="title indent">
|
||||
Rflink Light
|
||||
RFLink Light
|
||||
</h1>
|
||||
</header>
|
||||
<hr class="divider">
|
||||
<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 communication with 433Mhz devices using cheap hardware (Arduino + 433Mhz tranceiver).</p>
|
||||
<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>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>
|
||||
|
|
@ -77,12 +77,15 @@
|
|||
<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>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>
|
||||
<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="s">platform</span><span class="pi">:</span> <span class="s">rflink</span>
|
||||
<span class="s">device_defaults</span><span class="pi">:</span>
|
||||
<span class="s">fire_event</span><span class="pi">:</span> <span class="s">true</span>
|
||||
<span class="s">signal_repetitions</span><span class="pi">:</span> <span class="s">2</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>
|
||||
|
|
@ -94,22 +97,22 @@
|
|||
<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>
|
||||
<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>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>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<p>Device configuration variables:</p>
|
||||
<ul>
|
||||
<li><strong>name</strong> (<em>Optional</em>): Name for the device, defaults to Rflink ID.</li>
|
||||
<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 or hybrid. See ‘Light Types’ below.</li>
|
||||
<li><strong>aliasses</strong> (<em>Optional</em>): Alternative Rflink ID’s this device is known by.</li>
|
||||
<li><strong>aliasses</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>signal_repetitions</strong> (<em>Optional</em>): Repeat every RFLink command this number of times (default: 1)</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 433Mhz remote) the state is known and will be shown in the frontend.</p>
|
||||
<p>Sometimes a light is controlled by multiple 433Mhz 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>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>
|
||||
<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="s">platform</span><span class="pi">:</span> <span class="s">rflink</span>
|
||||
|
|
@ -123,7 +126,7 @@
|
|||
</div>
|
||||
<p>Any on/off command from any allias ID updates the current state of the light. However when sending a command through the frontend only the primary ID is used.</p>
|
||||
<h3><a class="title-link" name="light-types" href="#light-types"></a> Light types</h3>
|
||||
<p>Light devices can come in different forms. Some only switch on and off, other support dimming. Dimmable devices might not always respond nicely to repeated <code class="highlighter-rouge">on</code> command as they turn into a pulsating state until <code class="highlighter-rouge">on</code> is pressed again (for example KlikAanKlikUit). The Rflink component support three types of lights to make things work in every situation:</p>
|
||||
<p>Light devices can come in different forms. Some only switch on and off, other support dimming. Dimmable devices might not always respond nicely to repeated <code class="highlighter-rouge">on</code> command as they turn into a pulsating state until <code class="highlighter-rouge">on</code> is pressed again (for example KlikAanKlikUit). The RFLink component support three types of lights to make things work in every situation:</p>
|
||||
<ul>
|
||||
<li><em>Hybrid</em>: This type sends a <code class="highlighter-rouge">dim</code> followed by an a <code class="highlighter-rouge">on</code> command; and <code class="highlighter-rouge">off</code> commands. This will make dimmable devices turn on at the requested dim level and on/off devices on. One caveat is this type is not compatible with signal repetition as multiple <code class="highlighter-rouge">on</code> signals will cause dimmers to go into disco mode.</li>
|
||||
<li><em>Switchable</em>: Device type that sends only <code class="highlighter-rouge">on</code> and <code class="highlighter-rouge">off</code> commands. It work for both on/off and dimmable type switches. However dimmables might have issues with signal repetition (see above).</li>
|
||||
|
|
@ -131,7 +134,7 @@
|
|||
</ul>
|
||||
<p>By default new lights are assigned the <code class="highlighter-rouge">switchable</code> type. Protocol supporting dimming are assigned the <code class="highlighter-rouge">hybrid</code> type. Currently only <code class="highlighter-rouge">newkaku</code> protocol is detected as dimmable. Please refer to Device Support to get your dimmers supported.</p>
|
||||
<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 433Mhz command in the ether. To prevent cluttering the frontend use any of these methods:</p>
|
||||
<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>Hide unwanted devices using <a href="/getting-started/customizing-devices/">customizations</a></li>
|
||||
|
|
@ -159,13 +162,13 @@
|
|||
<h1 class='title delta'>Related components</h1>
|
||||
<ul class='divided'>
|
||||
<li><a href='/components/rflink/'>
|
||||
Rflink
|
||||
RFLink
|
||||
</a></li>
|
||||
<li><a href='/components/sensor.rflink/'>
|
||||
Rflink Sensor
|
||||
RFLink Sensor
|
||||
</a></li>
|
||||
<li><a href='/components/switch.rflink/'>
|
||||
Rflink Switch
|
||||
RFLink Switch
|
||||
</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
|
|
@ -242,10 +245,10 @@
|
|||
<a href='/components/light.qwikswitch/'>QwikSwitch Light</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/light.rfxtrx/'>RFXtrx Light</a>
|
||||
RFLink Light
|
||||
</li>
|
||||
<li>
|
||||
Rflink Light
|
||||
<a href='/components/light.rfxtrx/'>RFXtrx Light</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href='/components/light.scsgate/'>SCSGate Light</a>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue