|
| 1 | +--- |
| 2 | +layout: page |
| 3 | +title: "TellStick" |
| 4 | +description: "Telldus TellStick service enabler and tools." |
| 5 | +date: 2017-11-30 21:43 |
| 6 | +sidebar: true |
| 7 | +comments: false |
| 8 | +sharing: true |
| 9 | +footer: true |
| 10 | +featured: false |
| 11 | +--- |
| 12 | + |
| 13 | +Setting up the [Tellstick](http://telldus.com) service and tools contained in the [telldus-core](http://developer.telldus.com/) package and adding configuration to enable Tellstick and Tellstick Duo to work on your Hass.io. |
| 14 | + |
| 15 | + |
| 16 | +To use this add-on, you first install it from the list of Built-in add-ons in Hass.io. |
| 17 | +After installation you are presented with a default and example configuration, to alter this you must follow both the JSON format and also be aligned with the [valid parameters for Tellstick configuration file (tellstick.conf)](https://developer.telldus.com/wiki/TellStick_conf). |
| 18 | + |
| 19 | +After any changes has been made to the configuration you need to restart the add-on for the changes to take effect. |
| 20 | + |
| 21 | + |
| 22 | +Configuration variables: |
| 23 | + |
| 24 | +- **id** (*Required*): This is a number and must be unique for each device. |
| 25 | +- **name** (*Required*): A name for easy identification of the device. |
| 26 | +- **protocol** (*Required*): This is the protocol the device uses. More on the different protocols later down. |
| 27 | +- **model** (*Optional*): The parameter model is only used by some protocols where there exists different types of devices using the same protocol. This can be dimmers versus non-dimmers, codeswitch versus selflearning etc. |
| 28 | +- **house** (*Optional*): Depending on protocol the values here can vary a lot to identify or group per house or type. |
| 29 | +- **unit** (*Optional*): Unit identifier, in most cases a value between 1 to 16 and often used in combination with house. |
| 30 | +- **fade** (*Optional*): Fade is either `true` or `false` and tells a dimmer if is should fade smooth or instand between values (only for IKEA protocol as it seems). |
| 31 | +- **code** (*Optional*): A number series based on ones and zeroes often used for dip-switch based devices. |
| 32 | + |
| 33 | + |
| 34 | + |
| 35 | + |
| 36 | +In order to communicate with the add-on you will also need to add Hass.io specific data in the `configuration.yaml` file. |
| 37 | +For regular Home Assistant you only add `tellstick:` but for Hass.io and this add-on you need to add internal communication details. |
| 38 | + |
| 39 | + |
| 40 | +```yaml |
| 41 | +# Example configuration.yaml entry |
| 42 | + |
| 43 | +tellstick: |
| 44 | + host: core-tellstick |
| 45 | + port: [50800, 50801] |
| 46 | + |
| 47 | +``` |
| 48 | +
|
| 49 | +
|
| 50 | +
|
| 51 | +To add [lights](https://home-assistant.io/components/light.tellstick/), [sensors](https://home-assistant.io/components/sensor.tellstick/) and [switches](https://home-assistant.io/components/switch.tellstick/) you follow the guidelines for each type individually that is [described for Home Assistant](https://home-assistant.io/components/tellstick/) |
| 52 | +
|
| 53 | +
|
| 54 | +## {% linkable_title Examples %} |
| 55 | +
|
| 56 | +
|
| 57 | +Example for adding more devices in the add-on configuration (note the comma separator between devices): |
| 58 | +
|
| 59 | +```json |
| 60 | +{ |
| 61 | + "devices": [ |
| 62 | + { |
| 63 | + "id": 1, |
| 64 | + "name": "Outdoor light", |
| 65 | + "protocol": "everflourish", |
| 66 | + "model": "selflearning-switch", |
| 67 | + "house": "A", |
| 68 | + "unit": "1" |
| 69 | + }, |
| 70 | + { |
| 71 | + "id": 2, |
| 72 | + "name": "Hallway dimmer", |
| 73 | + "protocol": "risingsun", |
| 74 | + "model": "selflearning-dimmer", |
| 75 | + "house": "A", |
| 76 | + "unit": "2" |
| 77 | + } |
| 78 | + ] |
| 79 | +} |
| 80 | +``` |
0 commit comments