mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-22 16:56:50 +00:00
Minimal configuration & Additional configuration examples
This commit is contained in:
javicalle
parent
bc29dfae1d
commit
df44eb6fab
@ -61,17 +61,15 @@ RFLink cover ID's are composed of: protocol, id, and gateway. For example: `RTS_
|
||||
|
||||
Once the ID of a cover is known, it can be used to configure the cover in Home Assistant, for example, to add it to a different group, hide it or set a nice name.
|
||||
|
||||
Assigning a name to a cover:
|
||||
Configuring devices as a cover:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
cover:
|
||||
- platform: rflink
|
||||
devices:
|
||||
RTS_0100F2_0:
|
||||
name: SunShade
|
||||
bofumotor_455201_0f:
|
||||
name: Sovrumsgardin
|
||||
RTS_0100F2_0: {}
|
||||
bofumotor_455201_0f: {}
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
@ -136,3 +134,32 @@ devices:
|
||||
### {% linkable_title Device support %}
|
||||
|
||||
See [device support](/components/rflink/#device-support).
|
||||
|
||||
### {% linkable_title Additional configuration examples %}
|
||||
|
||||
Multiple covers with custom names and aliases
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
cover:
|
||||
- platform: rflink
|
||||
devices:
|
||||
RTS_0A8720_0:
|
||||
name: enanos
|
||||
aliases:
|
||||
- rts_31e53f_01
|
||||
- rts_32e53f_01
|
||||
RTS_30E542_0:
|
||||
name: comedor
|
||||
aliases:
|
||||
- rts_33e53f_01
|
||||
- rts_fa872e_01
|
||||
RTS_33E542_0:
|
||||
name: dormitorio
|
||||
aliases:
|
||||
- rts_30e53f_01
|
||||
- rts_32e53f_01
|
||||
RTS_32E542_0:
|
||||
name: habitaciones
|
||||
fire_event: true
|
||||
```
|
||||
@ -23,18 +23,17 @@ RFLink switch/light ID's are composed of: protocol, id, switch. For example: `ne
|
||||
|
||||
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 a device as light with a nice name:
|
||||
Configuring devices as a light:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
light:
|
||||
- platform: rflink
|
||||
device_defaults:
|
||||
fire_event: true
|
||||
signal_repetitions: 2
|
||||
devices:
|
||||
newkaku_0000c6c2_1:
|
||||
name: Living room
|
||||
NewKaku_02a48800_0: {}
|
||||
newkaku_0000c6c2_1: {}
|
||||
Ansluta_ce30_0: {}
|
||||
Maclean_0d82_01: {}
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
@ -131,14 +130,9 @@ light:
|
||||
- platform: rflink
|
||||
devices:
|
||||
newkaku_0000c6c2_1:
|
||||
name: Living room
|
||||
aliases:
|
||||
- newkaku_000000001_2
|
||||
- kaku_000001_a
|
||||
Ansluta_ce30_0:
|
||||
name: Kitchen Under Counter Lights
|
||||
Maclean_0d82_01:
|
||||
name: Bedroom Lamp
|
||||
```
|
||||
|
||||
Any on/off command from any alias ID updates the current state of the light. However when sending a command through the frontend only the primary ID is used.
|
||||
@ -165,3 +159,30 @@ Lights are added automatically when the RFLink gateway intercepts a wireless com
|
||||
### {% linkable_title Device support %}
|
||||
|
||||
See [device support](/components/rflink/#device-support)
|
||||
|
||||
### {% linkable_title Additional configuration examples %}
|
||||
|
||||
Multiple lights with `signal_repetitions` and custom names
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
light:
|
||||
- platform: rflink
|
||||
device_defaults:
|
||||
fire_event: true
|
||||
signal_repetitions: 2
|
||||
automatic_add: true
|
||||
devices:
|
||||
NewKaku_02a48800_0:
|
||||
name: Kitchen
|
||||
type: hybrid
|
||||
newkaku_0000c6c2_1:
|
||||
name: Living room
|
||||
aliases:
|
||||
- newkaku_000000001_2
|
||||
- kaku_000001_a
|
||||
Ansluta_ce30_0:
|
||||
name: Kitchen Under Counter Lights
|
||||
Maclean_0d82_01:
|
||||
name: Bedroom Lamp
|
||||
```
|
||||
@ -23,15 +23,14 @@ RFLink sensor ID's are composed of: protocol, id and type (optional). For exampl
|
||||
|
||||
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.
|
||||
|
||||
Assigning name to a sensor:
|
||||
Configuring a device as a sensor:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: rflink
|
||||
devices:
|
||||
alectov1_0334_temp:
|
||||
sensor_type: temperature
|
||||
alectov1_0334_temp: {}
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
@ -121,3 +120,32 @@ Sensors are added automatically when the RFLink gateway intercepts a wireless co
|
||||
### {% linkable_title Device support %}
|
||||
|
||||
See [device support](/components/rflink/#device-support)
|
||||
|
||||
### {% linkable_title Additional configuration examples %}
|
||||
|
||||
Multiple sensors with `automatic_add` disabled and `aliases`
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: rflink
|
||||
automatic_add: false
|
||||
devices:
|
||||
oregontemp_0d93_temp:
|
||||
sensor_type: temperature
|
||||
oregontemp_0d93_bat:
|
||||
sensor_type: battery
|
||||
tunex_c001_temp:
|
||||
sensor_type: temperature
|
||||
aliases:
|
||||
- xiron_4001_temp
|
||||
tunex_c001_hum:
|
||||
sensor_type: humidity
|
||||
aliases:
|
||||
- xiron_4001_hum
|
||||
tunex_c001_bat:
|
||||
sensor_type: battery
|
||||
aliases:
|
||||
- xiron_4001_bat
|
||||
```
|
||||
|
||||
|
||||
@ -22,21 +22,15 @@ RFLink switch/light ID's are composed of: protocol, id, switch. For example: `ne
|
||||
|
||||
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.
|
||||
|
||||
Configuring a device as switch with a nice name:
|
||||
Configuring devices as switch :
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
switch:
|
||||
platform: rflink
|
||||
device_defaults:
|
||||
fire_event: true
|
||||
signal_repetitions: 2
|
||||
devices:
|
||||
newkaku_0000c6c2_1:
|
||||
name: Ceiling fan
|
||||
conrad_00785c_0a:
|
||||
name: Motion sensor kitchen
|
||||
|
||||
- platform: rflink
|
||||
devices:
|
||||
newkaku_0000c6c2_1: {}
|
||||
conrad_00785c_0a: {}
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
@ -120,13 +114,13 @@ Sometimes a switch is controlled by multiple wireless remotes, each remote has i
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
switch:
|
||||
platform: rflink
|
||||
devices:
|
||||
newkaku_0000c6c2_1:
|
||||
name: Ceiling fan
|
||||
aliases:
|
||||
- newkaku_000000001_2
|
||||
- kaku_000001_a
|
||||
- platform: rflink
|
||||
devices:
|
||||
newkaku_0000c6c2_1:
|
||||
name: Ceiling fan
|
||||
aliases:
|
||||
- newkaku_000000001_2
|
||||
- kaku_000001_a
|
||||
```
|
||||
|
||||
Any on/off command from any alias ID updates the current state of the switch. However when sending a command through the frontend only the primary ID is used.
|
||||
@ -134,3 +128,21 @@ Any on/off command from any alias ID updates the current state of the switch. Ho
|
||||
### {% linkable_title Device support %}
|
||||
|
||||
See [device support](/components/rflink/#device-support)
|
||||
|
||||
### {% linkable_title Additional configuration examples %}
|
||||
|
||||
Multiple switches with signal repetitions and custom names
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
switch:
|
||||
- platform: rflink
|
||||
device_defaults:
|
||||
fire_event: true
|
||||
signal_repetitions: 2
|
||||
devices:
|
||||
newkaku_0000c6c2_1:
|
||||
name: Ceiling fan
|
||||
conrad_00785c_0a:
|
||||
name: Motion sensor kitchen
|
||||
```
|
||||
Loading…
x
Reference in New Issue
Block a user