Update Rflink hub component configuration (#7171)

* Update Rflink hub component configuration

Update style of Rflink light component documentation to follow new configuration variables description.
Related to #6385.

* Homogeneous with PR #7200

* You are right

Co-Authored-By: javicalle <31999997+javicalle@users.noreply.github.com>

* 👕 Relative links
This commit is contained in:
javicalle 2018-11-11 10:38:35 +01:00 committed by Franck Nijhof
parent 8681aa3d6a
commit 806fdfb13e

View File

@ -12,15 +12,15 @@ ha_category: Hub
ha_release: 0.38
---
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 Mega 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 Mega firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
The 433 MHz spectrum is used by many manufacturers mostly using their own protocol/standard and includes devices like: light switches, blinds, weather stations, alarms and various other sensors.
RFLink Gateway supports a number of RF frequencies, using a wide range of low-cost hardware. [Their website](http://www.rflink.nl/blog2/) provides details for various RF transmitters, receivers and transceiver modules for 433MHz, 868MHz and 2.4 GHz.
<p class='note'>
Note: Versions later than R44 add support for Ikea Ansluta, Philips Living Colors Gen1 and MySensors devices.
</p>
<p class='note'>
Note: Versions later than R44 add support for Ikea Ansluta, Philips Living Colors Gen1 and MySensors devices.
</p>
A complete list of devices supported by RFLink can be found [here](http://www.rflink.nl/blog2/devlist).
@ -50,20 +50,20 @@ host:
wait_for_ack:
description: Wait for RFLink to acknowledge commands sent before sending new command (slower but more reliable).
required: false
type: string
default: true
type: boolean
ignore_devices:
description: List of device id's to ignore. Supports wildcards (`*`) at the end.
required: false
type: string
type: [list, string]
reconnect_interval:
description: Time in seconds between reconnect attempts.
required: false
default: 10
type: integer
{% endconfiguration %}
### {% linkable_title Full example %}
```yaml
# Example configuration.yaml entry
rflink:
@ -117,9 +117,9 @@ sensor:
automatic_add: true
```
[RFLink Switches](https://www.home-assistant.io/components/switch.rflink/) cannot be added automatically.
[RFLink Switches](/components/switch.rflink/) and [RFLink Binary Sensors](/components/binary_sensor.rflink/) cannot be added automatically.
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. However, 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.
The RFLink component does not know the difference between a binary sensor, a switch and a light. Therefore all switchable devices are automatically added as light by default. However, once the ID of a switch is known, it can be used to configure it as a switch or a binary sensor type in Home Assistant, for example, to add it to a different group, hide it or configure a nice name.
### {% linkable_title Ignoring devices %}
@ -161,7 +161,7 @@ If you find a device is recognized differently, with different protocols or the
### {% linkable_title Debug Logging %}
For debugging purposes or context when investigating issues you can enable debug logging for Rflink with the following config snippet:
For debugging purposes or context when investigating issues you can enable debug logging for RFLink with the following config snippet:
```yaml
logger: