RFLink Light updated example (home-assistant#2296)

genestealer · fabaff · commit 42d62a2eadbb · 2017-03-24T21:12:23.000+01:00
* Updated example for Rflink Light

* Update light.rflink.markdown
diff --git a/source/_components/light.rflink.markdown b/source/_components/light.rflink.markdown
@@ -1,7 +1,7 @@
 ---
 layout: page
-title: "Rflink Light"
-description: "Instructions how to integrate Rflink lights into Home Assistant."
+title: "RFLink Light"
+description: "Instructions how to integrate RFLink lights into Home Assistant."
 date: 2016-01-04
 sidebar: true
 comments: false
@@ -12,11 +12,11 @@ ha_category: Light
 ha_release: 0.38
 ---
 
-The `rflink` component support devices that use [Rflink gateway firmware](http://www.nemcon.nl/blog2/), for example the [Nodo Rflink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). Rflink gateway is an Arduino firmware that allows communication with 433Mhz devices using cheap hardware (Arduino + 433Mhz tranceiver).
+The `rflink` component support devices that use [RFLink gateway firmware](http://www.nemcon.nl/blog2/), for example the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
 
 First you have to set up your [rflink hub](/components/rflink/).
 
-After configuring the Rflink hub lights will be automatically discovered and added.
+After configuring the RFLink hub lights will be automatically discovered and added.
 
 New/unknown lights can be assigned to a default group automatically by specifying the `new_devices_group` option with a group name. If the group doesn't exist it will be created.
 
@@ -29,7 +29,7 @@ sensor:
   new_devices_group: "New Rflink Lights"
 ```
 
-Rflink switch/light ID's are composed of: protocol, id, switch. For example: `newkaku_0000c6c2_1`.
+RFLink switch/light ID's are composed of: protocol, id, switch. For example: `newkaku_0000c6c2_1`.
 
 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.
 
@@ -39,6 +39,9 @@ Configuring a device as light with a nice name:
 # Example configuration.yaml entry
 light:
   platform: rflink
+  device_defaults:
+    fire_event: true
+    signal_repetitions: 2
   devices:
     newkaku_0000c6c2_1:
       name: Living room
@@ -49,22 +52,22 @@ Configuration variables:
 - **devices**  (*Optional*): A list of devices with their name to use in the frontend.
 - **new_devices_group** (*Optional*): Create group to add new/unknown devices to.
 - **device_defaults**: (*Optional*)
-  - **fire_event_** (*Optional*): Set default `fire_event` for Rflink switch devices (see below).
-  - **signal_repetitions** (*Optional*): Set default `signal_repetitions` for Rflink switch devices (see below).
+  - **fire_event_** (*Optional*): Set default `fire_event` for RFLink switch devices (see below).
+  - **signal_repetitions** (*Optional*): Set default `signal_repetitions` for RFLink switch devices (see below).
 
 Device configuration variables:
 
-- **name** (*Optional*): Name for the device, defaults to Rflink ID.
+- **name** (*Optional*): Name for the device, defaults to RFLink ID.
 - **type** (*Optional*): Override automatically detected type of the light device, can be: switchable, dimmable or hybrid. See 'Light Types' below.
-- **aliasses** (*Optional*): Alternative Rflink ID's this device is known by.
+- **aliasses** (*Optional*): Alternative RFLink ID's this device is known by.
 - **fire_event_** (*Optional*): Fire an `button_pressed` event if this device is turned on or off (default: False).
-- **signal_repetitions** (*Optional*): Repeat every Rflink command this number of times (default: 1)
+- **signal_repetitions** (*Optional*): Repeat every RFLink command this number of times (default: 1)
 
 ### {% linkable_title Light state %}
 
-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.
+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.
 
-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:
+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:
 
 ```yaml
 # Example configuration.yaml entry
@@ -82,7 +85,7 @@ Any on/off command from any allias ID updates the current state of the light. Ho
 
 ### {% linkable_title Light types %}
 
-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 `on` command as they turn into a pulsating state until `on` is pressed again (for example KlikAanKlikUit). The Rflink component support three types of lights to make things work in every situation:
+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 `on` command as they turn into a pulsating state until `on` is pressed again (for example KlikAanKlikUit). The RFLink component support three types of lights to make things work in every situation:
 
 - *Hybrid*: This type sends a `dim` followed by an a `on` command; and `off` 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 `on` signals will cause dimmers to go into disco mode.
 - *Switchable*: Device type that sends only `on` and `off` commands. It work for both on/off and dimmable type switches. However dimmables might have issues with signal repetition (see above).
@@ -92,7 +95,7 @@ By default new lights are assigned the `switchable` type. Protocol supporting di
 
 ### {% linkable_title Hiding/ignoring lights %}
 
-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:
+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:
 
 - Configure a `new_devices_group` for lights and optionally add it to a different `view`.
 - Hide unwanted devices using [customizations](/getting-started/customizing-devices/)
