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

Merge branch 'master' into next

Browse source
This commit is contained in:
Paulus Schoutsen 2016-05-21 09:52:05 -07:00
commit 0f14803a22
33 changed files with 294 additions and 123 deletions
Download patch file Download diff file Expand all files Collapse all files

2
source/_components/automation.markdown
View file

@ -11,6 +11,6 @@ logo: home-assistant.png
ha_category: Automation
---
Please see the [getting started section] for in-depth documentation on how to use the automation compnoent.
Please see the [getting started section] for in-depth documentation on how to use the automation component.
[getting started section]: /getting-started/automation/

2
source/_components/binary_sensor.apcupsd.markdown
View file

@ -14,7 +14,7 @@ ha_release: 0.13
In addition to the [APCUPSd Sensor](/components/sensor.apcupsd/) devices, you may also create a device which is simply "on" when the UPS status is online and "off" at all other times.
To enable this sensor, add the following lines to your `configuration.yaml` file for a GET request:
To enable this sensor, add the following lines to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry

2
source/_components/dweet.markdown
View file

@ -9,7 +9,7 @@ sharing: true
footer: true
logo: dweet.png
ha_category: "History"
featured: true
featured: false
ha_release: 0.19
---

4
source/_components/light.markdown
View file

@ -49,7 +49,7 @@ Turns one or multiple lights off.
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | no | String or list of strings that point at `entity_id`s of lights. Else targets all.
| `transition` | no | Integer that represents the time the light should take to transition to the new state.
| `transition` | yes | Integer that represents the time the light should take to transition to the new state.
### {% linkable_title Service `light.toggle` %}
@ -60,4 +60,4 @@ Toggles the state of one or multiple lights using [groups]({{site_root}}/compone
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- |
| `entity_id` | no | String or list of strings that point at `entity_id`s of lights. Else targets all.
| `transition` | no | Integer that represents the time the light should take to transition to the new state.
| `transition` | yes | Integer that represents the time the light should take to transition to the new state.

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

@ -31,6 +31,7 @@ Push your remote and your device should be added:
Here the name is 0b11000102ef9f210010f70 and you can verify that it works from the frontend.
Then you should update your configuration to:
```yaml
light:
platform: rfxtrx
@ -40,6 +41,7 @@ light:
```
Example configuration:
```yaml
# Example configuration.yaml entry
light:

2
source/_components/media_player.cast.markdown
View file

@ -26,4 +26,4 @@ media_player:
Configuration variables:
- **host** *Optional*: Use only if you don't want to scan for devices.
- **host** (*Optional*): Use only if you don't want to scan for devices.

6
source/_components/media_player.firetv.markdown
View file

@ -45,9 +45,9 @@ media_player:
Configuration variables:
- **host** *Optional*: Where `firetv-server` is running. Default is *localhost:5556*.
- **device** *Optional*: The device ID, default is *default*.
- **name** *Optional*: The friendly name of the device, default is 'Amazon Fire TV'.
- **host** (*Optional*): Where `firetv-server` is running. Default is *localhost:5556*.
- **device** (*Optional*): The device ID, default is *default*.
- **name** (*Optional*): The friendly name of the device, default is 'Amazon Fire TV'.
<p class='note warning'>

4
source/_components/media_player.itunes.markdown
View file

@ -30,5 +30,5 @@ media_player:
Configuration variables:
- **host** *Required*: The URL of the itunes-api API, eg. http://192.168.1.50
- **port** *Optional*: The port where itunes-api is accessible, eg. 8181.
- **host** (*Required*): The URL of the itunes-api API, eg. http://192.168.1.50
- **port** (*Optional*): The port where itunes-api is accessible, eg. 8181.

10
source/_components/media_player.kodi.markdown
View file

@ -31,8 +31,8 @@ media_player:
Configuration variables:
- **host** *Required*: The host name or address of the device that is running XBMC/Kodi
- **port** *Required*: The port number, default 8080
- **name** *Optional*: The name of the device used in the frontend.
- **username** *Optional*: The XBMC/Kodi HTTP username.
- **password** *Optional*: The XBMC/Kodi HTTP password.
- **host** (*Required*): The host name or address of the device that is running XBMC/Kodi
- **port** (*Required*): The port number, default 8080
- **name** (*Optional*): The name of the device used in the frontend.
- **username** (*Optional*): The XBMC/Kodi HTTP username.
- **password** (*Optional*): The XBMC/Kodi HTTP password.

8
source/_components/media_player.mpd.markdown
View file

@ -29,10 +29,10 @@ media_player:
Configuration variables:
- **server** *Required*: IP address of the Music Player Daemon, eg. 192.168.1.32
- **port** *Optional*: Port of the Music Player Daemon, defaults to 6600.
- **location** *Optional*: Location of your Music Player Daemon.
- **password** *Optional*: Password for your Music Player Daemon.
- **server** (*Required*): IP address of the Music Player Daemon, eg. 192.168.1.32
- **port** (*Optional*): Port of the Music Player Daemon, defaults to 6600.
- **location** (*Optional*): Location of your Music Player Daemon.
- **password** (*Optional*): Password for your Music Player Daemon.
This platform works with [Music Player Daemon](http://www.musicpd.org/) and [mopidy](https://www.mopidy.com/) with [Mopidy-MPD](https://docs.mopidy.com/en/latest/ext/mpd/) as used by [Pi MusicBox](http://www.pimusicbox.com/).

6
source/_components/media_player.panasonic_viera.markdown
View file

@ -34,7 +34,7 @@ media_player:
Configuration variables:
- **host** *Required*: The IP of the Panasonic Viera TV, e.g. `192.168.0.10`
- **port** *Optional*: The port of your Panasonic Viera TV. Defaults to `55000`
- **name** *Optional*: The name you would like to give to the Panasonic Viera TV.
- **host** (*Required*): The IP of the Panasonic Viera TV, e.g. `192.168.0.10`
- **port** (*Optional*): The port of your Panasonic Viera TV. Defaults to `55000`
- **name** (*Optional*): The name you would like to give to the Panasonic Viera TV.

4
source/_components/media_player.pioneer.markdown
View file

@ -27,6 +27,6 @@ media_player:
Configuration variables:
- **host** *Required*: The IP of the Pioneer device, eg. `192.168.0.10`
- **name** *Optional*: The name you would like to give to the receiver.
- **host** (*Required*): The IP of the Pioneer device, eg. `192.168.0.10`
- **name** (*Optional*): The name you would like to give to the receiver.

6
source/_components/media_player.samsungtv.markdown
View file

@ -29,8 +29,8 @@ media_player:
Configuration variables:
- **host** *Required*: The IP of the Samsung Smart TV, e.g. 192.168.0.10
- **name** *Optional*: The name you would like to give to the Samsung Smart TV.
- **host** (*Required*): The IP of the Samsung Smart TV, eg. 192.168.0.10
- **name** (*Optional*): The name you would like to give to the Samsung Smart TV.
Currently known supported models:
@ -44,3 +44,5 @@ Currently known supported models:
If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io).
The two letters at the beginning of the model number represent the region, UE is Europe, UN is North America and UA is Asia & Australia. The two numbers following that represent the screen size. If you add your model remember to remove these before adding them to the list.
There's currently a [known issue](https://github.com/home-assistant/home-assistant/issues/2098) with some TV's receiving a *Key press UP* that can interrupt certain applications.

8
source/_components/media_player.squeezebox.markdown
View file

@ -30,7 +30,7 @@ media_player:
Configuration variables:
- **host** *Required*: The host name or address of the Logitech Media Server, eg. 192.168.1.21.
- **port** *Optional*: Telnet port to Logitech Media Server, default 9090.
- **username** *Optional*: The username, if password protection is enabled.
- **password** *Optional*: The password, if password protection is enabled.
- **host** (*Required*): The host name or address of the Logitech Media Server, eg. 192.168.1.21.
- **port** (*Optional*): Telnet port to Logitech Media Server, default 9090.
- **username** (*Optional*): The username, if password protection is enabled.
- **password** (*Optional*): The password, if password protection is enabled.

8
source/_components/media_player.webostv.markdown
View file

@ -13,11 +13,11 @@ ha_iot_class: "Local Poll"
ha_release: 0.18
---
The `webostv` platform allows you to control a LG WebOS Smart TV.
The `webostv` platform allows you to control a [LG](http://www.lg.com) WebOS Smart TV.
When the TV is first connected, you will need to accept Home Assistant on the TV to allow communication.
To add a TV to your installation, add the following to your `configuration.yaml` file and follow the configurator instructions:
To add a TV to your installation, add the following to your `configuration.yaml` file:
```yaml
# Example configuration.yaml entry
@ -29,7 +29,7 @@ media_player:
Configuration variables:
- **host** *Optional*: The IP of the LG WebOS Smart TV, e.g. 192.168.0.10
- **name** *Optional*: The name you would like to give to the LG WebOS Smart TV.
- **host** (*Optional*): The IP of the LG WebOS Smart TV, eg. 192.168.0.10
- **name** (*Optional*): The name you would like to give to the LG WebOS Smart TV.
If you do not provide a host name, all LG WebOS Smart TV's within your network will be auto-discovered if your TV network name is set to `[LG] webOS TV`

3
source/_components/sensor.rfxtrx.markdown
View file

@ -14,6 +14,7 @@ The `rfxtrx` platform support sensors that communicate in the frequency range of
First you have to set up your [rfxtrx hub.](/components/rfxtrx/)
The easiest way to find your sensors is to add this to your `configuration.yaml`:
```yaml
sensor:
platform: rfxtrx
@ -28,6 +29,7 @@ Then when the sensor emits a signal it will be automatically added:
Here the name is 0a52080000301004d240259 and you can verify that it works from the frontend.
Then you should update your configuration to:
```yaml
sensor:
platform: rfxtrx
@ -52,6 +54,7 @@ sensor:
Example configuration:
```yaml
# Example configuration.yaml entry
sensor:

2
source/_components/switch.rfxtrx.markdown
View file

@ -31,6 +31,7 @@ Push your remote and your device should be added:
Here the name is 0b11000102ef9f210010f70 and you can verify that it works from the frontend.
Then you should update your configuration to:
```yaml
switch:
platform: rfxtrx
@ -40,6 +41,7 @@ switch:
```
Example configuration:
```yaml
# Example configuration.yaml entry
switch:

6
source/_components/thermostat.zwave.markdown
View file

@ -13,3 +13,9 @@ ha_release: 0.17
---
To get your Z-Wave thermostat working with Home Assistant, follow the instructions for the general [Z-Wave component](/components/zwave/).
## NOTE
If your thermostat support fan modes or different operating modes, it should be considered a hvac component, and will also be detected as one. Thermostat component does not support setting fan or operation mode. This is controlled via the hvac component.
If the thermostat support different operationg modes, you will get one thermostat entity for each mode.
These can be hidden with settings using the customize setting in the config file.

8
source/_components/zwave.markdown
View file

@ -38,13 +38,13 @@ Then get the OpenZWave files and switch to the `python3` branch:
$ git clone https://github.com/OpenZWave/python-openzwave.git
$ cd python-openzwave
$ git checkout python3
$ PYTHON_EXEC=`which python3` make build
$ sudo PYTHON_EXEC=`which python3` make install
$ PYTHON_EXEC=$(which python3) make build
$ sudo PYTHON_EXEC=$(which python3) make install
```
<p class='note'>
Instead of `make install`, you can alternatively build your own python-openzwave package which can be easily uninstalled:
```$ sudo PYTHON_EXEC=`which python3` checkinstall --pkgname python-openzwave --pkgversion 1.0 --provides python-openzwave```
```$ sudo PYTHON_EXEC=$(which python3) checkinstall --pkgname python-openzwave --pkgversion 1.0 --provides python-openzwave```
</p>
@ -89,7 +89,7 @@ $ ls /dev/ttyACM*
```
<p class='note'>
Depending on what's plugged into your USB ports, the name found above may change. You an lock in a name, such as `/dev/zwave`, by following [these instructions](http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/).
Depending on what's plugged into your USB ports, the name found above may change. You can lock in a name, such as `/dev/zwave`, by following [these instructions](http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/).
</p>
#### {% linkable_title Events %}