diff --git a/source/_components/binary_sensor.rflink.markdown b/source/_components/binary_sensor.rflink.markdown index cfe439201a8..d73b4f73dea 100644 --- a/source/_components/binary_sensor.rflink.markdown +++ b/source/_components/binary_sensor.rflink.markdown @@ -47,7 +47,7 @@ devices: name: description: Name for the device. required: false - default: Rflink ID + default: RFLink ID type: string aliases: description: Alternative RFLink ID's this device is known by. diff --git a/source/_components/cover.rflink.markdown b/source/_components/cover.rflink.markdown index 8a5f6f53edd..5d38115cd14 100644 --- a/source/_components/cover.rflink.markdown +++ b/source/_components/cover.rflink.markdown @@ -13,11 +13,11 @@ ha_release: 0.55 --- -The `rflink` cover platform supports 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). +The `rflink` component supports 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/). +First, you have to set up your [RFLink hub](/components/rflink/). -After configuring the RFLink hub covers will be automatically discovered and added. Except the Somfy RTS devices. +After configuring the RFLink hub, covers will be automatically discovered and added. Except the Somfy RTS devices. ### {% linkable_title Setting up a Somfy RTS device %} @@ -29,7 +29,7 @@ Press the Learn button on the original Somfy remote enter the following code wit 10;RTS;02FFFF;0412;3;PAIR; ``` -Your blinds will go up and down again. This means your Rflink is now paired with your RTS motor. +Your blinds will go up and down again. This means your RFLink is now paired with your RTS motor. To check this enter the following code again and see if there is a record. ```text @@ -79,12 +79,12 @@ device_defaults: type: map keys: fire_event: - description: Set default `fire_event` for Rflink cover devices. + description: Set default `fire_event` for RFLink cover devices. required: false default: False type: boolean signal_repetitions: - description: Set default `signal_repetitions` for Rflink cover devices. + description: Set default `signal_repetitions` for RFLink cover devices. required: false default: 1 type: integer @@ -101,10 +101,10 @@ devices: name: description: Name for the device. required: false - default: Rflink ID + default: RFLink ID type: string aliases: - description: Alternative Rflink ID's this device is known by. + description: Alternative RFLink ID's this device is known by. required: false type: [list, string] fire_event: @@ -113,7 +113,7 @@ devices: default: False type: boolean signal_repetitions: - description: The number of times every Rflink command should repeat. + description: The number of times every RFLink command should repeat. required: false type: integer group: diff --git a/source/_components/light.rflink.markdown b/source/_components/light.rflink.markdown index 770e6b2f6e0..c181c93800f 100644 --- a/source/_components/light.rflink.markdown +++ b/source/_components/light.rflink.markdown @@ -13,15 +13,15 @@ ha_release: 0.38 ha_iot_class: "Assumed state" --- -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). +The `rflink` component supports 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/). +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. -RFLink switch/light ID's are composed of: protocol, id, switch. For example: `newkaku_0000c6c2_1`. +RFLink binary_sensor/switch/light ID's are composed of: protocol, id, switch/channel. 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. +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. Configuring devices as a light: @@ -43,12 +43,12 @@ device_defaults: type: map keys: fire_event: - description: Set default `fire_event` for Rflink switch devices (see below). + description: Set default `fire_event` for RFLink switch devices (see below). required: false default: False type: boolean signal_repetitions: - description: Set default `signal_repetitions` for Rflink switch devices (see below). + description: Set default `signal_repetitions` for RFLink switch devices (see below). required: false default: 1 type: integer @@ -70,7 +70,7 @@ devices: name: description: Name for the device. required: false - default: Rflink ID + default: RFLink ID type: string type: description: "Override automatically detected type of the light device, can be: switchable, dimmable, hybrid or toggle. See [Light Types](/components/light.rflink/#light-types) below." @@ -78,7 +78,7 @@ devices: default: switchable type: string aliases: - description: Alternative Rflink ID's this device is known by. + description: Alternative RFLink ID's this device is known by. required: false type: [list, string] group_aliases: @@ -95,7 +95,7 @@ devices: default: false type: boolean signal_repetitions: - description: Repeat every Rflink command this number of times. + description: Repeat every RFLink command this number of times. required: false default: 1 type: integer @@ -105,7 +105,7 @@ devices: default: true type: boolean aliasses: - description: (**deprecated**) Alternative Rflink ID's this device is known by. + description: (**deprecated**) Alternative RFLink ID's this device is known by. required: false type: [list, string] group_aliasses: diff --git a/source/_components/sensor.rflink.markdown b/source/_components/sensor.rflink.markdown index a0b15bcf5d7..0e8340f1627 100644 --- a/source/_components/sensor.rflink.markdown +++ b/source/_components/sensor.rflink.markdown @@ -13,15 +13,15 @@ ha_release: 0.38 ha_iot_class: "Local Polling" --- -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). +The `rflink` component supports 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/). +First, you have to set up your [RFLink hub](/components/rflink/). -After configuring the RFLink hub sensors will be automatically discovered and added. +After configuring the RFLink hub, sensors will be automatically discovered and added. -RFLink sensor ID's are composed of: protocol, id and type (optional). For example: `alectov1_0334_temp`. Some sensors emit multiple types of data. Each will be created as its own +RFLink sensor ID's are composed of: protocol, id and type (optional). For example: `alectov1_0334_temp`. Some sensors emit multiple types of data. Each will be created as its own. -Once the ID of a sensor is known it can be used to configure the sensor in HA, for example to add it to a different group, hide it or configure a nice name. +Once the ID of a sensor is known, it can be used to configure the sensor in HA, for example to add it to a different group, hide it or configure a nice name. Configuring a device as a sensor: diff --git a/source/_components/switch.rflink.markdown b/source/_components/switch.rflink.markdown index ef550189edd..7a915b2f07c 100644 --- a/source/_components/switch.rflink.markdown +++ b/source/_components/switch.rflink.markdown @@ -12,15 +12,15 @@ ha_category: Switch 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 two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver). +The `rflink` component supports 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/). +First, you have to set up your [RFLink hub](/components/rflink/). -The RFLink component does not know the difference between a `switch` and a `light`. Therefore all switchable devices are automatically added as `light` by default. +The RFLink component does not know the difference between a `switch`, a `binary_sensor` and a `light`. Therefore all switchable devices are automatically added as `light` by default. -RFLink switch/light ID's are composed of: protocol, id, switch. For example: `newkaku_0000c6c2_1`. +RFLink binary_sensor/switch/light ID's are composed of: protocol, id, switch/channel. For example: `newkaku_0000c6c2_1`. -Once the ID of a switch is known it can be used to configure it as a switch type in HA, for example to add it to a different group, hide it or configure a nice name. +Once the ID of a switch is known, it can be used to configure it as a switch type in HA and, for example, to add it to a different group, hide it or configure a nice name. Configuring devices as switch : @@ -40,12 +40,12 @@ device_defaults: type: map keys: fire_event: - description: Set default `fire_event` for Rflink switch devices (see below). + description: Set default `fire_event` for RFLink switch devices (see below). required: false default: False type: boolean signal_repetitions: - description: Set default `signal_repetitions` for Rflink switch devices (see below). + description: Set default `signal_repetitions` for RFLink switch devices (see below). required: false default: 1 type: integer @@ -62,10 +62,10 @@ devices: name: description: Name for the device. required: false - default: Rflink ID + default: RFLink ID type: string aliases: - description: Alternative Rflink ID's this device is known by. + description: Alternative RFLink ID's this device is known by. required: false type: [list, string] group_aliases: @@ -92,7 +92,7 @@ devices: default: true type: boolean aliases: - description: "(**deprecated**) Alternative Rflink ID's this device is known by." + description: "(**deprecated**) Alternative RFLink ID's this device is known by." required: false type: [list, string] group_aliases: