Skip to content

Commit 706472a

Browse files
balloobballoob
authored
Merge pull request home-assistant#1741 from home-assistant/next
0.36
2 parents 7304efc + 94f7c7e commit 706472a

File tree

70 files changed

+1753
-86
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

70 files changed

+1753
-86
lines changed

‎_config.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -130,9 +130,9 @@ social:
130130

131131
# Home Assistant release details
132132
current_major_version: 0
133-
current_minor_version: 35
134-
current_patch_version: 3
135-
date_released: 2016-12-23
133+
current_minor_version: 36
134+
current_patch_version: 0
135+
date_released: 2017-01-15
136136

137137
# Either # or the anchor link to latest release notes in the blog post.
138138
# Must be prefixed with a # and have double quotes around it.

‎source/_components/bbb_gpio.markdown

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
layout: page
3+
title: "BeagleBone Black GPIO"
4+
description: "Instructions how to integrate the GPIO capability of a BeagleBone Black into Home Assistant."
5+
date: 2017-01-14 10:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: beaglebone-black.png
11+
ha_category: DIY
12+
ha_release: 0.36
13+
---
14+
15+
The `bbb_gpio` component is the base for all [BeagleBone Black][https://beagleboard.org/black] related GPIO platforms in Home Assistant. There is no setup needed for the component itself, for the platforms please check their corresponding pages.
16+

‎source/_components/binary_sensor.flic.markdown

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,7 @@ Configuration variables:
3030
- **host** (*Optional*): The IP or hostname of the flic service server. (default: `localhost`)
3131
- **port** (*Optional*): The port of the flic service. (default: `5551`)
3232
- **discovery** (*Optional*): If `true`, the component is configured to constantly scan for new buttons. (default: `true`)
33+
- **ignored_click_types**: List of click types whose occurrence should not trigger and `flic_click` event.
3334
- **timeout** (*Optional*): Maximum time in seconds an event can be queued locally on a button before discarding the event. (default: `3`)
3435

3536
#### {% linkable_title Discovery %}
@@ -64,3 +65,7 @@ Event data:
6465
- **button_address**: The bluetooth address of the button, that triggered the event.
6566
- **click_type**: The type of click. Possible values are `single`, `double` and `hold`.
6667
- **queued_time**: The amount of time this event was queued on the button, in seconds.
68+
69+
##### {% linkable_title Ignoring Click Types %}
70+
71+
For some purposes it might make sense to exclude a specific click type from triggering click events. For example when ignoring double clicks, pressing the button twice fast results in two `single` instead of a `double` click event. This is very useful for applications where you want to click fast.

‎source/_components/camera.mjpeg.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Configuration variables:
3333
- **username** (*Optional*): The username for accessing your camera.
3434
- **password** (*Optional*): The password for accessing your camera.
3535
- **authentication** (*Optional*): `basic` (default) or `digest` auth for requests.
36-
-
36+
3737
<p class='note'>
3838
There is a <a href="https://github.com/shazow/urllib3/issues/800" target="_blank">known issue in urllib3</a> that you will get error messages in your logs like <code>[StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ''</code> but the component still works fine. You can ignore the messages.
3939
</p>

‎source/_components/demo.markdown

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,7 @@ Available demo platforms:
2222
- [Climate](/components/climate/) (`climate`)
2323
- [Cover](/components/cover/) (`cover`)
2424
- [Fan](/components/fan/) (`fan`)
25+
- [Image Processing](/components/image_processing/) (`image_processing`)
2526
- [Light](/components/light/) (`light`)
2627
- [Lock](/components/lock/) (`lock`)
2728
- [Notification](/components/notify/) (`notify`)

‎source/_components/device_tracker.bluetooth_le_tracker.markdown

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,10 @@ device_tracker:
3232
- platform: bluetooth_le_tracker
3333
```
3434
35+
Configuration variables:
36+
37+
- **device_id** (*Optional*): The device ID for the bluetooth device to be used for tracking. Defaults to `hci0`.
38+
3539
As some BT LE devices change their MAC address regularly, a new device is only discovered when it has been seen 5 times.
3640
Some BTLE devices (e.g. fitness trackers) are only visible to the devices that they are paired with. In this case, the BTLE tracker won't see this device.
3741

‎source/_components/device_tracker.ping.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: "Ping (ICMP)"
4+
description: "Instructions how to integrate Ping (ICMP)-based presence detection into Home Assistant."
5+
date: 2017-01-06 08:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: home-assistant.png
11+
ha_category: Presence Detection
12+
ha_release: 0.36
13+
---
14+
15+
16+
The `ping` platform offers presence detection by using `ping` to send ICMP echo requests. This can be useful when devices are running a firewall and are blocking UDP or TCP packets but responding to ICMP requests (like Android phones). This tracker doesn't need to know the MAC address since the host can be on a different subnet. This makes this an option to detect hosts on a different subnet when `nmap` or other solutions don't work since `arp` doesn't work.
17+
18+
To use this presence detection in your installation, add the following to your `configuration.yaml` file:
19+
20+
```yaml
21+
# Example configuration.yaml entry
22+
device_tracker:
23+
- platform: ping
24+
hosts:
25+
hostone: 192.168.2.10
26+
```
27+
28+
Configuration variables:
29+
30+
- **hosts** array (*Required*): List of device names and their corresponding IP address or hostname.
31+
- **count** (*Optional*): Number of packet used for each device (avoid false detection).
32+
33+
See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.

‎source/_components/device_tracker.trackr.markdown

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
layout: page
3+
title: "TrackR"
4+
description: "Instructions how to use TrackR to track devices in Home Assistant."
5+
date: 2016-12-22 1000
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: trackr.png
11+
ha_release: 0.36
12+
ha_category: Presence Detection
13+
ha_iot_class: "Cloud Polling"
14+
---
15+
16+
17+
The `trackr` platform allows you to detect presence using [TrackR](https://www.thetrackr.com/) devices.
18+
19+
The offical TrackR mobile app handles the tracking of the TrackR devices using your phones bluetooth and GPS.
20+
21+
To integrate TrackR in Home Assistant, add the following section to your `configuration.yaml` file:
22+
23+
```yaml
24+
# Example configuration.yaml entry
25+
device_tracker:
26+
platform: trackr
27+
username: USERNAME
28+
password: PASSWORD
29+
```
30+
31+
Configuration variables:
32+
33+
- **username** (*Required*): The email address for the TrackR account.
34+
- **password** (*Required*): The password for your given username.

‎source/_components/device_tracker.upc_connect.markdown

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
layout: page
3+
title: "UPC ConnectBox"
4+
description: "Instructions how to integrate UPC ConnectBox into Home Assistant."
5+
date: 2016-12-30 00:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: upc.png
11+
ha_category: Presence Detection
12+
ha_release: 0.36
13+
---
14+
15+
16+
The `upc_connect` platform offers presence detection by looking at connected devices to an [ConnectBox](https://www.upc.ch/de/internet/connectbox/) router from [Liberty Global](http://www.libertyglobal.com/), which is a Internet provider in Switzerland, Austria.
17+
18+
To use an Internet-Box router in your installation, add the following to your `configuration.yaml` file:
19+
20+
```yaml
21+
# Example configuration.yaml entry
22+
device_tracker:
23+
platform: upc_connect
24+
password: '123456'
25+
host: "192.168.0.1" # only required if not 192.168.0.1
26+
```
27+
28+
See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.

‎source/_components/device_tracker.xiaomi.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: "Xiaomi Router"
4+
description: "Instructions how to integrate Xiaomi routers into Home Assistant."
5+
date: 2017-01-12 12:04
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: xiaomi.png
11+
ha_category: Presence Detection
12+
ha_release: 0.36
13+
---
14+
15+
16+
The `xiaomi` platform offers presence detection by looking at connected devices to a [Xiaomi](http://miwifi.com) router.
17+
18+
To use an Xiaomi router in your installation, add the following to your `configuration.yaml` file:
19+
20+
```yaml
21+
# Example configuration.yaml entry
22+
device_tracker:
23+
- platform: xiaomi
24+
host: YOUR_ROUTER_IP
25+
password: YOUR_ADMIN_PASSWORD
26+
```
27+
28+
Configuration variables:
29+
30+
- **host** (*Required*): The IP address of your router, eg. `192.168.0.1`.
31+
- **username** (*Optional*: The admin username. By default `admin`.
32+
- **password** (*Required*): The password for the admin account.
33+
34+
See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
35+

0 commit comments

Comments
 (0)