home-assistant · balloob · Jan 15, 2017 · Dec 17, 2016 · Dec 18, 2016 · Dec 18, 2016
diff --git a/_config.yml b/_config.yml
@@ -130,9 +130,9 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 35
-current_patch_version: 3
-date_released: 2016-12-23
+current_minor_version: 36
+current_patch_version: 0
+date_released: 2017-01-15
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.

diff --git a/source/_components/bbb_gpio.markdown b/source/_components/bbb_gpio.markdown
@@ -0,0 +1,16 @@
+---
+layout: page
+title: "BeagleBone Black GPIO"
+description: "Instructions how to integrate the GPIO capability of a BeagleBone Black into Home Assistant."
+date: 2017-01-14 10:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: beaglebone-black.png
+ha_category: DIY
+ha_release: 0.36
+---
+
+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.
+
diff --git a/source/_components/binary_sensor.flic.markdown b/source/_components/binary_sensor.flic.markdown
@@ -30,6 +30,7 @@ Configuration variables:
 - **host** (*Optional*): The IP or hostname of the flic service server. (default: `localhost`)
 - **port** (*Optional*): The port of the flic service. (default: `5551`)
 - **discovery** (*Optional*): If `true`, the component is configured to constantly scan for new buttons. (default: `true`)
+- **ignored_click_types**: List of click types whose occurrence should not trigger and `flic_click` event.
 - **timeout** (*Optional*): Maximum time in seconds an event can be queued locally on a button before discarding the event. (default: `3`)
 
 #### {% linkable_title Discovery %}
@@ -64,3 +65,7 @@ Event data:
 - **button_address**: The bluetooth address of the button, that triggered the event.
 - **click_type**: The type of click. Possible values are `single`, `double` and `hold`.
 - **queued_time**: The amount of time this event was queued on the button, in seconds.
+
+##### {% linkable_title Ignoring Click Types %}
+
+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.
diff --git a/source/_components/camera.mjpeg.markdown b/source/_components/camera.mjpeg.markdown
@@ -33,7 +33,7 @@ Configuration variables:
 - **username** (*Optional*): The username for accessing your camera.
 - **password** (*Optional*): The password for accessing your camera.
 - **authentication** (*Optional*): `basic` (default) or `digest` auth for requests.
-- 
+
 <p class='note'>
 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. 
 </p>
diff --git a/source/_components/demo.markdown b/source/_components/demo.markdown
@@ -22,6 +22,7 @@ Available demo platforms:
 - [Climate](/components/climate/) (`climate`)
 - [Cover](/components/cover/) (`cover`)
 - [Fan](/components/fan/) (`fan`)
+- [Image Processing](/components/image_processing/) (`image_processing`)
 - [Light](/components/light/) (`light`)
 - [Lock](/components/lock/) (`lock`)
 - [Notification](/components/notify/) (`notify`)

diff --git a/source/_components/device_tracker.bluetooth_le_tracker.markdown b/source/_components/device_tracker.bluetooth_le_tracker.markdown
@@ -32,6 +32,10 @@ device_tracker:
   - platform: bluetooth_le_tracker
 ```
 
+Configuration variables:
+
+- **device_id** (*Optional*): The device ID for the bluetooth device to be used for tracking. Defaults to `hci0`.
+
 As some BT LE devices change their MAC address regularly, a new device is only discovered when it has been seen 5 times.
 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.
 

diff --git a/source/_components/device_tracker.ping.markdown b/source/_components/device_tracker.ping.markdown
@@ -0,0 +1,33 @@
+---
+layout: page
+title: "Ping (ICMP)"
+description: "Instructions how to integrate Ping (ICMP)-based presence detection into Home Assistant."
+date: 2017-01-06 08:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: home-assistant.png
+ha_category: Presence Detection
+ha_release: 0.36
+---
+
+
+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.
+
+To use this presence detection in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+device_tracker:
+  - platform: ping
+    hosts:
+      hostone: 192.168.2.10
+```
+
+Configuration variables:
+
+- **hosts** array (*Required*): List of device names and their corresponding IP address or hostname.
+- **count** (*Optional*): Number of packet used for each device (avoid false detection).
+
+See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
diff --git a/source/_components/device_tracker.trackr.markdown b/source/_components/device_tracker.trackr.markdown
@@ -0,0 +1,34 @@
+---
+layout: page
+title: "TrackR"
+description: "Instructions how to use TrackR to track devices in Home Assistant."
+date: 2016-12-22 1000
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: trackr.png
+ha_release: 0.36
+ha_category: Presence Detection
+ha_iot_class: "Cloud Polling"
+---
+
+
+The `trackr` platform allows you to detect presence using [TrackR](https://www.thetrackr.com/) devices. 
+
+The offical TrackR mobile app handles the tracking of the TrackR devices using your phones bluetooth and GPS.
+
+To integrate TrackR in Home Assistant, add the following section to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+device_tracker:
+  platform: trackr
+  username: USERNAME
+  password: PASSWORD
+```
+
+Configuration variables:
+
+- **username** (*Required*): The email address for the TrackR account.
+- **password** (*Required*): The password for your given username.
diff --git a/source/_components/device_tracker.upc_connect.markdown b/source/_components/device_tracker.upc_connect.markdown
@@ -0,0 +1,28 @@
+---
+layout: page
+title: "UPC ConnectBox"
+description: "Instructions how to integrate UPC ConnectBox into Home Assistant."
+date: 2016-12-30 00:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: upc.png
+ha_category: Presence Detection
+ha_release: 0.36
+---
+
+
+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.
+
+To use an Internet-Box router in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+device_tracker:
+  platform: upc_connect
+  password: '123456'
+  host: "192.168.0.1" # only required if not 192.168.0.1
+```
+
+See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
diff --git a/source/_components/device_tracker.xiaomi.markdown b/source/_components/device_tracker.xiaomi.markdown
@@ -0,0 +1,35 @@
+---
+layout: page
+title: "Xiaomi Router"
+description: "Instructions how to integrate Xiaomi routers into Home Assistant."
+date: 2017-01-12 12:04
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: xiaomi.png
+ha_category: Presence Detection
+ha_release: 0.36
+---
+
+
+The `xiaomi` platform offers presence detection by looking at connected devices to a [Xiaomi](http://miwifi.com) router.
+
+To use an Xiaomi router in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+device_tracker:
+  - platform: xiaomi
+    host: YOUR_ROUTER_IP
+    password: YOUR_ADMIN_PASSWORD
+```
+
+Configuration variables:
+
+- **host** (*Required*): The IP address of your router, eg. `192.168.0.1`.
+- **username** (*Optional*: The admin username. By default `admin`.
+- **password** (*Required*): The password for the admin account.
+
+See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
+
diff --git a/source/_components/fan.wink.markdown b/source/_components/fan.wink.markdown
@@ -0,0 +1,19 @@
+---
+layout: page
+title: "Wink Fan"
+description: "Instructions how to setup the Wink fans within Home Assistant."
+date: 2017-01-14 12:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: wink.png
+ha_category: Fan
+ha_release: 0.36
+---
+
+
+The Wink fan platform allows you to control your [Wink](http://www.wink.com/) fans.
+
+The requirement is that you have setup your [Wink hub](/components/wink/).
+
diff --git a/source/_components/ha.markdown b/source/_components/ha.markdown
@@ -9,7 +9,7 @@ sharing: true
 footer: true
 logo: home-assistant.png
 ha_category: Release
-ha_release: 0.35
+ha_release: 0.36
 ---
 
 Details about the latest release can always be found at:

diff --git a/source/_components/image_processing.markdown b/source/_components/image_processing.markdown
@@ -0,0 +1,36 @@
+---
+layout: page
+title: "Image Processing"
+description: "Instructions how to setup image processing with Home Assistant."
+date: 2017-01-09 00:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+ha_release: 0.36
+---
+
+Image processing enables Home Assistant to process image from [cameras][/components/#camera]. Only camera entities are supported as sources.
+
+For interval control, use `scan_interval` in platform.
+
+## {% linkable_title ALPR %}
+
+Alpr entities attribute have a vehicle counter `vehicles` and all found plates as `plates`.
+
+This event is trigger after OpenALPR found a new licence plate.
+
+```yaml
+# Example configuration.yaml automation entry
+automation:
+- alias: Open garage door
+  trigger:
+    platform: event
+    event_type: openalpr.found
+    event_data:
+      entity_id: openalpr.camera_garage_1
+      plate: BE2183423
+...
+```
+
+The following event attributes will be present: `entity_id`, `plate`, `confidence`
diff --git a/source/_components/image_processing.openalpr_cloud.markdown b/source/_components/image_processing.openalpr_cloud.markdown
@@ -0,0 +1,35 @@
+---
+layout: page
+title: "OpenALPR Cloud"
+description: "Instructions how to integrate licences plates with OpenALPR cloud into Home Assistant."
+date: 2017-01-09 00:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: openalpr.png
+ha_category: Image_Processing
+featured: false
+ha_release: 0.36
+---
+
+[OpenALPR](http://www.openalpr.com/) integration for Home Assistant allows you to process licences plates from a camera. You can use them to open a garage door or trigger any other [automation](https://home-assistant.io/components/automation/).
+
+### {% linkable_title Configuration Home Assistant %}
+
+```yaml
+# Example configuration.yaml entry
+image_processing:
+ - platform: openalpr_cloud
+   region: eu
+   source:
+    - entity_id: camera.garage
+```
+Configuration variables:
+
+- **region** (*Required*): Country or region. List of supported [values](https://github.com/openalpr/openalpr/tree/master/runtime_data/config).
+- **alpr_bin** (*Optional*): The command line tool alpr from OpenALPR software for local processing. Defaults to `alpr`.
+- **confidence** (*Optional*):  The minimum of confidence in percent to process with Home Assistant. Defaults to 80.
+- **source** array (*Required*): List of image sources.
+  - **entities** (*Required*): A list of devices to add in Home Assistant.
+  - **name** (*Optional*): This parameter allows you to override the name of your OpenALPR entity.
diff --git a/source/_components/image_processing.openalpr_local.markdown b/source/_components/image_processing.openalpr_local.markdown
@@ -0,0 +1,54 @@
+---
+layout: page
+title: "OpenALPR Local"
+description: "Instructions how to integrate licences plates with OpenALPR local into Home Assistant."
+date: 2017-01-09 00:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: openalpr.png
+ha_category: Image_Processing
+featured: false
+ha_release: 0.36
+---
+
+[OpenALPR](http://www.openalpr.com/) integration for Home Assistant allows you to process licences plates from a camera. You can use them to open a garage door or trigger any other [automation](https://home-assistant.io/components/automation/).
+
+### {% linkable_title Local installation %}
+
+If you want process all data locally, you need version 2.3.1 or higher of the `alpr` commandline tool.
+
+If you don't find binaries for your distribution you can compile from source. Documention of how to build openalpr is found [here](https://github.com/openalpr/openalpr/wiki).
+
+On a Debian system you can use this `cmake` command to build only the command line tool:
+
+```bash
+$ cmake -DWITH_TEST=FALSE -DWITH_BINDING_JAVA=FALSE --DWITH_BINDING_PYTHON=FALSE --DWITH_BINDING_GO=FALSE -DWITH_DAEMON=FALSE -DCMAKE_INSTALL_PREFIX:PATH=/usr ..
+```
+
+Verify your `alpr` installation with:
+
+```
+$ wget -O- -q http://plates.openalpr.com/h786poj.jpg | alpr -
+```
+
+### {% linkable_title Configuration Home Assistant %}
+
+```yaml
+# Example configuration.yaml entry
+image_processing:
+ - platform: openalpr_cloud
+   api_key: 'sk_abcxyz123456'
+   region: eu
+   source:
+    - entity_id: camera.garage
+```
+Configuration variables:
+
+- **region** (*Required*): Country or region. List of supported [values](https://github.com/openalpr/openalpr/tree/master/runtime_data/config).
+- **api_key** (*Required*): You need an API key from [OpenALPR Cloud](https://cloud.openalpr.com/).
+- **confidence** (*Optional*): The minimum of confidence in percent to process with Home Assistant. Defaults to 80. 
+- **source** array (*Required*): List of image sources.
+  - **entities** (*Required*): A list of devices to add in Home Assistant.
+  - **name** (*Optional*): This parameter allows you to override the name of your OpenALPR entity.
diff --git a/source/_components/influxdb.markdown b/source/_components/influxdb.markdown
@@ -38,6 +38,23 @@ Configuration variables:
 - **tags** (*Optional*): Tags to mark the data.
 
 
+Starting with 0.36 the InfluxDB component has a new schema to store values in the InfluxDB databases.
+
+- There will not be any tags/fields named time anymore.
+- All numeric fields (int/float/bool) will be stored as float inside InfluxDB database.
+- All string fields corresponding to state attributes will be renamed as `FIELDNAME_str`, where `FIELDNAME` is the state attribute, to avoid type conflicts.
+- All string fields corresponding to a state will be renamed as state (former value).
+- Fields named value will always be stored as float.
+- Fields named state will always be stored as string.
+
+If you need to migrate your database, you may require to run the `influxdb_migrator` script.
+
+```bash
+$ hass --script influxdb_migrator \
+    -H IP_INFLUXDB_HOST -u INFLUXDB_USERNAME -p INFLUXDB_PASSWORD \
+    -o test_series -d INFLUXDB_DB_NAME
+```
+
 ## {% linkable_title Examples %}