jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Minimizing of the configuration sample (#1024)

Browse source
This commit is contained in:
Fabian Affolter 2016-10-01 12:08:48 +02:00 • committed by GitHub
parent 3d47c6f54b
commit c7aaf72bbc
12 changed files with 109 additions and 94 deletions
Download patch file Download diff file Expand all files Collapse all files

13
source/_components/light.rfxtrx.markdown
View file

@ -15,23 +15,22 @@ ha_release: 0.7.5
The `rfxtrx` platform support lights that communicate in the frequency range of 433.92 MHz.
First you have to set up your [rfxtrx hub](/components/rfxtrx/).
The easiest way to find your lights is to add this to your `configuration.yaml`:
```yaml
light:
platform: rfxtrx
automatic_add: True
- platform: rfxtrx
automatic_add: True
```
Launch your homeassistant and go the website.
Push your remote and your device should be added:
Launch your Home Assistant and go the website. Push your remote and your device should be added:
<p class='img'>
<img src='/images/components/rfxtrx/switch.png' />
</p>
Here the name is `0b11000102ef9f210010f70` and you can verify that it works from the frontend.
Then you should update your configuration to:
Here the name is `0b11000102ef9f210010f70` and you can verify that it works from the frontend. Then you should update your configuration to:
```yaml
light:
@ -58,5 +57,5 @@ Configuration variables:
- **devices** (*Required*): A list of devices with their name to use in the frontend.
- **automatic_add** (*Optional*): To enable the automatic addition of new lights.
- **signal_repetitions** (*Optional*): Because the rxftrx device sends its actions via radio and from most receivers it's impossible to know if the signal was received or not. Therefore you can configure the switch to try to send each signal repeatedly.
- **signal_repetitions** (*Optional*): Because the RFXtrx device sends its actions via radio and from most receivers it's impossible to know if the signal was received or not. Therefore you can configure the switch to try to send each signal repeatedly.
- **fire_event** (*Optional*): Fires an event even if the state is the same as before. Can be used for automations.