Update Tellstick component configuration variable (#6762)

* Update Tellstick component configuration variable

* Minor changes
This commit is contained in:
Klaas Schoute 2018-10-13 23:02:51 +02:00 committed by Fabian Affolter
parent 9d13c99849
commit 4a43b29d47

View File

@ -14,6 +14,8 @@ ha_category: Hub
The `tellstick` component integrates [TellStick](http://www.telldus.se/products/tellstick) devices into Home Assistant. This integration allows users to add switches, lights, and sensors which are communicating with 433 MHz. There are a number of vendors (Capidi Elro, Intertechno, Nexa, Proove, Sartano, and Viking) who are selling products that work with TellStick. For more details, please check the TellStick [protocol list](http://developer.telldus.com/wiki/TellStick_conf).
## {% linkable_title Configuration %}
To get started, add the devices to your `configuration.yaml` file.
```yaml
@ -22,14 +24,23 @@ tellstick:
```
```yaml
# Example configuration.yaml entry for hass.io with TellStick add-on
# Example configuration.yaml entry for Hass.io with the TellStick add-on
tellstick:
host: core-tellstick
port: [50800, 50801]
```
Configuration variables:
- **signal_repetitions** (*Optional*): Because the tellstick 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 and light to try to send each signal repeatedly.
- **host** (*Optional*): If you run tellstick on another server or with a hass.io add-on.
- **port** (*Optional*): If needed with host config option. Must be port pair, for example `[50800, 50801]`.
{% configuration %}
signal_repetitions:
description: Because the TellStick 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 and light to try to send each signal repeatedly.
required: false
type: integer
host:
description: If you run TellStick on another server or with the Hass.io add-on.
required: inclusive
type: string
port:
description: Needed with the `host` configuration variable. Must be port pair, for example `[50800, 50801]`.
required: inclusive
type: list
{% endconfiguration %}