Skip to content

Commit d89e076

Browse files
persandstrompersandstrom
committed
Merge remote-tracking branch 'upstream/next' into kodi_settings
2 parents 547482e + 0fca778 commit d89e076

40 files changed

+980
-6
lines changed

‎source/_components/alarm_control_panel.nx584.markdown

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
layout: page
3+
title: "NX584 Alarm Control Panel"
4+
description: "Instructions how to integrate NX584 into Home Assistant."
5+
date: 2016-02-07 10:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: networx.png
11+
ha_category: Alarm
12+
---
13+
14+
The `nx584` platform provides integration with GE, Caddx, Interlogix (and other brands) alarm panels that support the NX584 interface module (or have it built in). Supported panels include NX4/6/8/8E. Actual integration is done through [pynx584](http://github.com/kk7ds/pynx584) which is required for this to work.
15+
16+
17+
To enable this, add the following lines to your `configuration.yaml`:
18+
19+
```yaml
20+
# Example configuration.yaml entry
21+
alarm_control_panel:
22+
platform: nx584
23+
host: ADDRESS
24+
```
25+
26+
Configuration variables:
27+
28+
- **host** (*Optional*): This is the host connection string (host:port) for the nx584 server process. If unset, it is assumed to be `localhost:5007`, which will work if the server process is running on the same system as home-assistant.
29+

‎source/_components/apcupsd.markdown

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
layout: page
3+
title: "APCUPSd"
4+
description: "Instructions on how to integrate APCUPSd status with Home Assistant."
5+
date: 2016-02-10 17:11
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: apcupsd.png
11+
ha_category: Hub
12+
---
13+
14+
[APCUPSd](http://www.apcupsd.org/) status information can be integrated into Home Assistant when the Network Information Server (NIS) [is configured](http://www.apcupsd.org/manual/manual.html#nis-server-client-configuration-using-the-net-driver).
15+
16+
Create an `apcupsd` section in your configuration, optionally containing the following parameters:
17+
18+
- **host**: The hostname/IP address on which the APCUPSd NIS is being served. Default: `localhost`
19+
- **port**: The port on which the APCUPSd NIS is listening. Default: `3551`
20+
21+
#### Example
22+
23+
Use defaults:
24+
25+
```yaml
26+
apcupsd:
27+
```
28+
29+
Set parameters:
30+
31+
```yaml
32+
apcupsd:
33+
host: 192.168.1.10
34+
port: 1234
35+
```

‎source/_components/binary_sensor.apcupsd.markdown

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
layout: page
3+
title: APCUPSd Binary Sensor
4+
description: "Instructions on how to set up an APCUPSd binary sensor within Home Assistant."
5+
date: 2016-02-10 18:47
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: apcupsd.png
11+
ha_category: Binary Sensor
12+
---
13+
14+
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.
15+
16+
#### Example
17+
18+
```yaml
19+
binary_sensor:
20+
- name: UPS Online
21+
platform: apcupsd
22+
```

‎source/_components/bloomsky.markdown

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
layout: page
3+
title: "BloomSky"
4+
description: "Instructions how to integrate the BloomSky within Home Assistant."
5+
date: 2016-02-03 20:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: bloomsky.png
11+
ha_category: Hub
12+
---
13+
14+
15+
The `bloomsky` component allows you to access your [BloomSky](http://www.insteon.com/) weather station's [sensors](/components/sensor.bloomsky) and [camera](/components/camera.bloomsky) from Home Assistant.
16+
17+
To integrate your BloomSky hub with Home Assistant, add the following section to your `configuration.yaml` file:
18+
19+
```yaml
20+
# Example configuration.yaml entry
21+
bloomsky:
22+
api_key: YOUR_API_KEY
23+
```
24+
25+
Configuration variables:
26+
27+
- **api_key** *Required*: Your BloomSky API key, obtained from your [BloomSky dashboard](https://dashboard.bloomsky.com) (click `developers` in the bottom left of the screen)

‎source/_components/camera.bloomsky.markdown

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
layout: page
3+
title: "BloomSky Camera"
4+
description: "Instructions how to integrate the BloomSky camera within Home Assistant."
5+
date: 2016-02-03 20:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: bloomsky.png
11+
ha_category: Camera
12+
---
13+
14+
15+
The `bloomsky` camera component allows you to view the current photo created by the camera in the [BloomSky](https://www.bloomsky.com) weather station. This can work in concert with [BloomSky sensors](/components/sensor.bloomsky).
16+
17+
To enable this camera in your installation, set up the [BloomSky component](/components/bloomsky) with your API key and add the following to your `configuration.yaml` file:
18+
19+
```yaml
20+
# Example configuration.yaml entry
21+
camera:
22+
platform: bloomsky
23+
```

‎source/_components/camera.uvc.markdown

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
layout: page
3+
title: "UniFi Video Camera"
4+
description: "Instructions how to integrate UVC cameras within Home Assistant."
5+
date: 2016-02-07 10:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: ubiquiti.png
11+
ha_category: Camera
12+
---
13+
14+
15+
The `uvc` component allows you to integrate [UniFi Video Camera (UVC)](https://www.ubnt.com/unifi-video/unifi-video-camera/) into Home Assistant.
16+
17+
To enable a UVC camera in your installation, add the following to your `configuration.yaml` file:
18+
19+
```yaml
20+
# Example configuration.yaml entry
21+
camera:
22+
platform: uvc
23+
nvr: IP_ADDRESS
24+
port: PORT
25+
key: APIKEY
26+
```
27+
28+
Configuration variables:
29+
30+
- **nvr** *Optional*: The IP or hostname of the NVR (Network Video Recorder) server.
31+
- **port** *Optional*: The port number to use for accessing the NVR.
32+
- **key** *Required*: The API key available from the NVR web interface.
33+

‎source/_components/garage_door.markdown

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
layout: page
3+
title: "Garage door"
4+
description: "Instructions how to integrate Garage doors into Home Assistant."
5+
date: 2016-02-12 07:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
---
11+
12+
Home Assistant can give you an interface to control any garage door.

‎source/_components/garage_door.wink.markdown

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
layout: page
3+
title: "Wink Garage door"
4+
description: "Instructions how to setup the Wink garage doors within Home Assistant."
5+
date: 2016-02-12 07:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: wink.png
11+
ha_category: Garage Door
12+
---
13+
14+
15+
The Wink garage door platform allows you to control your [Wink](http://www.wink.com/) enabled garage door.
16+
17+
The requirement is that you have setup your [Wink hub](/components/light.wink/).
18+

‎source/_components/influxdb.markdown

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,8 @@ influxdb:
2323
database: DB_TO_STORE_EVENTS
2424
username: MY_USERNAME
2525
password: MY_PASSWORD
26+
ssl: true
27+
verify_ssl: true
2628
```
2729
2830
Configuration variables:
@@ -32,4 +34,5 @@ Configuration variables:
3234
- **database** (*Optional*): Name of the database to use. Defaults to `home_assistant`. The database must already exist.
3335
- **username** (*Optional*): The username of the database user.
3436
- **password** (*Optional*): The password for the database user account.
35-
37+
- **ssl** (*Optional*): Use https instead of http to connect. Defaults to false.
38+
- **verify_ssl** (*Optional*): Verify SSL certificate for https request. Defaults to false.

‎source/_components/input_select.markdown

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
layout: page
3+
title: "Input Select"
4+
description: "Instructions how to integrate the Input Select component into Home Assistant."
5+
date: 2016-02-02 17:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: home-assistant.png
11+
ha_category: Automation
12+
---
13+
14+
The `input_select` component allows the user to define a list of values that can be selected via the frontend and can be used within conditions of automation.
15+
16+
To enable this platform, add the following lines to your `configuration.yaml`:
17+
18+
```yaml
19+
# Example configuration.yaml entry
20+
input_select:
21+
who_cooks:
22+
name: Who cooks today
23+
options:
24+
- Paulus
25+
- Anne Therese
26+
initial: Anne Therese
27+
icon: mdi:panda
28+
living_room_preset:
29+
options:
30+
- Visitors
31+
- Visitors with kids
32+
- Home Alone
33+
```
34+
35+
Configuration variables:
36+
37+
- **[alias]** (*Required*): Alias for the input.
38+
- **name** (*Optional*): Friendly name of the input.
39+
- **options** array (*Optional*): List of options to choose from
40+
- **initial** (*Optional*): Initial value when Home Assistant starts.
41+
- **icon** (*Optional*): Icon for entry.
42+
43+
Pick an icon that you can find on [materialdesignicons.com](https://materialdesignicons.com/) to use for your input and prefix the name with `mdi:`. For example `mdi:car`, `mdi:ambulance`, or `mdi:motorbike`.
44+

‎source/_components/light.scsgate.markdown

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
layout: page
3+
title: "SCSGate light"
4+
description: "Instructions how to integrate SCSGate lights into Home Assistant."
5+
date: 2016-01-31 19:30
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
ha_category: Light
11+
---
12+
13+
The SCSGate device can control lights of the BTicino MyHome system.
14+
15+
To enable SCSGate lights in your installation, add the following to your `configuration.yaml` file:
16+
17+
```yaml
18+
# Example configuration.yaml entry
19+
light:
20+
platform: scsgate
21+
devices:
22+
living_room:
23+
name: Living Room
24+
scs_id: XXXXX
25+
```
26+
27+
Configuration variables:
28+
29+
- **devices** (*Required*): A list of devices with their name to use in the frontend.

‎source/_components/lock.verisure.markdown

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
layout: page
3+
title: "Verisure Lock"
4+
description: "Instructions how to setup the Verisure locks within Home Assistant."
5+
date: 2016-02-12 06:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: wink.png
11+
ha_category: Lock
12+
---
13+
14+
15+
The Verisure lock platform allows you to control your [Verisure](https://www.verisure.com/) locks.
16+
17+
The requirement is that you have setup your [Verisure hub](/components/verisure/).
18+

‎source/_components/media_player.samsungtv.markdown

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
---
2+
layout: page
3+
title: "Samsung TV"
4+
description: "Instructions how to integrate a Samsung TV in Home Assistant."
5+
date: 2016-02-01 19:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: samsung.png
11+
ha_category: Media Player
12+
featured: false
13+
---
14+
15+
The `samsungtv` platform allows you to control an [Samsung TV](http://www.samsung.com).
16+
17+
18+
To add an Samsung TV to your installation, add the following to your `configuration.yaml` file:
19+
20+
```yaml
21+
# Example configuration.yaml entry
22+
media_player:
23+
platform: samsungtv
24+
```
25+

‎source/_components/mqtt_eventstream.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ comments: false
88
sharing: true
99
footer: true
1010
logo: mqtt.png
11-
ha_category: Others
11+
ha_category: Other
1212
---
1313

1414
The `mqtt_eventstream` components two Home Assistant instances via MQTT.

‎source/_components/mysensors.markdown

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,8 +24,10 @@ mysensors:
2424
gateways:
2525
- port: '/dev/ttyUSB0'
2626
persistence_file: 'path/mysensors.json'
27+
baud_rate: 38400
2728
- port: '/dev/ttyACM1'
2829
persistence_file: 'path/mysensors2.json'
30+
baud_rate: 115200
2931
debug: true
3032
persistence: true
3133
version: '1.5'
@@ -38,6 +40,7 @@ Configuration variables:
3840
- **persistence** (*Optional*): Enable or disable local persistence of sensor information. If this is disabled, then each sensor will need to send presentation messages after Home Assistant starts. Default is true.
3941
- **persistence_file** (*Optional*): Path to a file to save sensor information. The file extension determines the file type. Currently supported file types are 'pickle' and 'json'.
4042
- **version** (*Optional*): Specifies the MySensors protocol version to use. Supports 1.4 and 1.5. Default is 1.4.
43+
- **baud_rate** (*Optional*): Specifies baud rate of the connected gateway.
4144
4245
If you are using an original Arduino the port will be named `ttyACM*`. The exact number can be determined with the command shown below.
4346

0 commit comments

Comments
 (0)