Merge pull request home-assistant#2823 from home-assistant/release-0-47

0.47

_config.yml

@@ -140,13 +140,13 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 46
-current_patch_version: 1
-date_released: 2017-06-09
+current_minor_version: 47
+current_patch_version: 0
+date_released: 2017-06-17
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.
 # Major release:
-patch_version_notes: "#release-0461---june-9"
+patch_version_notes: "#"
 # Minor release (Example #release-0431---april-25):
 

source/_components/alarm_control_panel.spc.markdown

@@ -0,0 +1,20 @@
+---
+layout: page
+title: "Vanderbilt SPC Alarm"
+description: "Instructions how to setup the Vanderbilt SPC Alarm control panel within Home Assistant."
+date: 2017-05-18 22:01
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: vanderbilt_spc.png
+ha_category: Alarm
+ha_release: 0.47
+ha_iot_class: "Local Push"
+---
+
+
+The `spc` alarm control panel platform allows you to control your [Vanderbilt SPC](http://www.spc-intruder-detection.com/ssp-spc/) alarms.
+
+The requirement is that you have setup your [SPC hub](/components/spc/).
+

source/_components/binary_sensor.spc.markdown

@@ -0,0 +1,20 @@
+---
+layout: page
+title: "SPC Binary Sensor"
+description: "Instructions how to integrate Vanderbilt SPC binary sensors into Home Assistant."
+date: 2017-05-18 22:05
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: vanderbilt_spc.png
+ha_release: 0.47
+ha_category: Binary Sensor
+ha_iot_class: "Local Push"
+---
+
+The `spc` platform allows you to get data from your [Vanderbilt SPC](http://www.spc-intruder-detection.com/ssp-spc/) binary sensors from within Home Assistant. 
+
+Check the [type/class](/components/binary_sensor/) list for a possible visualization of your zone. Currently motion, smoke and door sensors are supported.
+
+The requirement is that you have setup your [SPC hub](/components/spc/).

source/_components/binary_sensor.tapsaff.markdown

@@ -0,0 +1,32 @@
+---
+layout: page
+title: "Taps Aff"
+description: "Instructions how to use the Taps Aff binary sensor in Home Assistant."
+date: 2017-05-28 18:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: tapsaff.png
+ha_category: Weather
+featured: false
+ha_release: 0.47
+ha_iot_class: "Local Polling"
+---
+
+
+The `tapsaff` binary sensor provides the 'Taps Aff' status for a given location within the UK using [Taps Aff](http://www.taps-aff.co.uk). 
+
+To enable this sensor, add the following lines to your `configuration.yaml`:
+
+```yaml
+# Example configuration.yaml entry
+binary_sensor:
+  - platform: tapsaff
+    location: glasgow
+```
+
+Configuration variables:
+
+- **location** (*Required*): The location for the Taps Aff. It must be configured with a UK postcode or city to work. 
+- **name** (*Optional*): The name to use when displaying this sensor.

source/_components/camera.onvif.markdown

@@ -0,0 +1,36 @@
+---
+layout: page
+title: "ONVIF Camera"
+description: "Instructions on how to integrate a ONVIF camera within Home Assistant."
+date: 2017-06-09 21:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: onvif.png
+ha_category: Camera
+ha_release: 0.47
+---
+
+
+The `ONVIF` platform allows you to use an ONVIF camera in Home Assistant. This requires FFmpeg component to be already configured.
+
+To enable your ONVIF in your installation, add the following to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+camera:
+  - platform: onvif
+    host: 192.168.1.111
+```
+
+Configuration variables:
+
+- **host** (*Required*): An IP or hostname of the camera.
+- **name** (*Optional*): Override the name of your camera.
+- **username** (*Optional*): The username for the camera.
+- **password** (*Optional*): The password for the camera.
+- **port** (*Optional*): The port for the camera. This defaults to 5000
+
+
+If you are running into trouble with this sensor, please refer to the [Troubleshooting section](/components/ffmpeg/#troubleshooting).

source/_components/climate.flexit.markdown

@@ -0,0 +1,58 @@
+---
+layout: page
+title: "Flexit A/C controller"
+description: "Instructions how to integrate Flexit A/C unit into Home Assistant."
+date: 2017-06-02 16:30 +0200
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: flexit.png
+ha_category: Climate
+ha_release: 0.47
+ha_iot_class: "Local Polling"
+---
+
+Integrates [Flexit](https://www.flexit.no/en/) Air Conditioning unit into Home Assistant.
+
+Requires an CI66 Modbus Adapter [CI66](https://www.flexit.no/en/products/air_handling_unit/accessories_ahu/modul/modbusadapter_ci66/modbus_adapter_ci66_k2-c2-uni/)
+
+To enable this platform, add the following lines to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+climate:
+  - platform: flexit
+    slave: 21
+```
+
+Configuration variables:
+
+- **slave** (*Required*): The slave ID of the modbus adapter, set using DIP-switches.
+- **name** (*Optional*): Displayed name of the A/C unit
+
+<p class='note'>
+This component requires the [Modbus](/components/modbus/) component to be set up to work
+</p>
+
+Full configuration example including modbus setup shown below:
+
+DIP-switch settings on the CI66:
+1=ON, 2=ON, 3=OFF, 4=ON, 5=OFF, 6=ON, 7=ON, 8=ON
+
+```yaml
+# Full example configuration.yaml entry
+modbus:
+  type: serial
+  method: rtu
+  port: /dev/ttyUSB0
+  baudrate: 56000
+  stopbits: 1
+  bytesize: 8
+  parity: E
+
+climate:
+  - platform: flexit
+    name: Main A/C
+    slave: 21
+```

source/_components/cover.garadget.markdown

@@ -7,7 +7,7 @@ sidebar: true
 comments: false
 sharing: true
 footer: true
-logo: garadget_logo.jpg
+logo: garadget.png
 ha_category: Cover
 ha_release: 0.32
 ha_iot_class: "Cloud Polling"

source/_components/cover.mqtt.markdown

@@ -47,6 +47,8 @@ Configuration variables:
 - **qos** (*Optional*): The maximum QoS level of the state topic. Default is `0`. Will also be used when publishing messages.
 - **retain** (*Optional*): If the published message should have the retain flag on or not. Default is `false`.
 - **value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload.
+- **set_position_topic** (*Optional*): The MQTT topic to publish position commands to.
+- **set_position_template** (*Optional*): Defines a [template](/topics/templating/) to define the position to be sent to the `set_position_topic` topic. Incoming position value is available for use in the template `{{position}}`. If no template is defined, the numeric position (0-100) will be written directly to the topic.
 - **tilt_command_topic** (*Optional*): The MQTT topic to publish commands to control the cover tilt.
 - **tilt_status_topic** (*Optional*): The MQTT topic subscribed to receive tilt status update values.
 - **tilt_min** (*Optional*): The minimum tilt value. Default is `0`

source/_components/dyson.markdown

@@ -0,0 +1,60 @@
+---
+layout: page
+title: "Dyson"
+description: "Instructions how to integrate Dyson into Home Assistant."
+date: 2017-05-27 10:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: dyson.png
+ha_category: Hub
+ha_iot_class: "Cloud Polling"
+ha_release: 0.47
+---
+
+The `dyson` component is the main component to integrate all [Dyson](https://dyson.com) related platforms.
+
+Currently limited to Cool Link Purifier.
+
+To enable this component, add the following lines to your `configuration.yaml`:
+
+```yaml
+dyson:
+  username: <dyson_account_user_email>
+  password: <dyson_acount_password>
+  language: <dyson_account_language>
+  devices:
+    - device_id: <device_id_1>
+      device_ip: <device_ip_1>
+    - device_id: <device_id_2>
+      device_ip: <device_ip_2>
+    ...
+```
+
+Configuration variables:
+
+- **username** (*Required*): Dyson account username (email address)
+- **password** (*Required*): Dyson account password
+- **language** (*Required*): Dyson account language country code. Known working codes: `FR`, `NL`, `UK`, `AU`. But others codes should work.
+- **devices** (*Optional*): List of devices
+  - **device_id** (*Required*): Device ID. Available in the mobiles applications (*Settings* page)
+  - **device_ip** (*Required*): Device IP address
+
+`devices` list is optional but you'll have to provide them if discovery is not working (warnings in the logs and the devices are not available in Home Assistant web interface).
+To find devices IP address, you can use your router or `nmap`:
+
+```bash
+$ nmap -p 1883 XXX.XXX.XXX.XXX/YY -- open
+```
+
+Where:
+
+- **XXX.XXX.XXX.XXX** is your network address
+- **YY** is your network mask
+
+For example:
+
+```bash
+$ nmap -p 1883 192.168.0.0/24 -- open
+```

source/_components/fan.dyson.markdown

@@ -0,0 +1,24 @@
+---
+layout: page
+title: "Dyson Purifier Fan"
+description: "Instructions how to setup the Dyson Purifier fans within Home Assistant."
+date: 2017-05-27 10:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: dyson.png
+ha_category: Fan
+ha_iot_class: "Cloud Polling"
+ha_release: 0.47
+---
+
+
+The `dyson` fan platform allows you to control your Dyson Purifier fans.
+
+You have first to setup the [Dyson component](/components/dyson/)
+
+### {% linkable_title Supported fan devices %}
+
+- Pure Cool link (desk and tower)
+- Pure Hot+cool link (but heating is not yet supported)

source/_components/ha.markdown

@@ -1,6 +1,6 @@
 ---
 layout: page
-title: "Home Assistant 0.46"
+title: "Home Assistant 0.47"
 description: ""
 date: 2016-12-16 17:00
 sidebar: true
@@ -9,7 +9,7 @@ sharing: true
 footer: true
 logo: home-assistant.png
 ha_category: Other
-ha_release: 0.46
+ha_release: 0.47
 ---
 
 Details about the latest release can always be found at:

source/_components/image_processing.opencv.markdown

@@ -10,9 +10,44 @@ footer: true
 logo: opencv.png
 ha_category: Image Processing
 featured: false
-ha_release: 0.44
+ha_release: 0.47
 ---
 
-The `opencv` image processing platform allows you to create a standalone image processor without the linked camera entity as mentioned in the [OpenCV page](https://home-assistant.io/components/opencv).
+[OpenCV](http://www.opencv.org) is an open source computer vision image and video processing library.
 
-Please refer to the [component](/components/opencv/) configuration on how to setup the image processor.
+Some pre-defined classifiers can be found here: https://github.com/opencv/opencv/tree/master/data
+
+### {% linkable_title Configuration %}
+
+To setup OpenCV with Home Assistant, add the following section to your `configuration.yaml` file:
+
+```yaml
+# Example configuration.yaml entry
+image_processing:
+  - platform: opencv
+    name: Front Door Faces
+    source:
+      - entity_id: camera.front_door
+    classifier:
+      mom: /path/to/classifier.xml
+```
+
+- **name** (*Required*): The name of the OpenCV image processor.
+- **source** array (*Required*): List of image sources.
+  - **entity_id** (*Required*): A camera entity id to get picture from.
+    - **name** (*Optional*): This parameter allows you to override the name of your `image_processing` entity.
+- **classifier** (*Optional*): Dictionary of name to path to the classifier xml file. If this field is not provided, a face classifier will be downloaded from OpenCV's github repo.
+
+**classifier** may also be defined as a dictionary of names to classifier configurations:
+
+```yaml
+    mom:
+      file: /path/to/classifier/xml
+      neighbors: 4
+      min_size: (40, 40)
+      scale: 1.1f
+```
+
+- **file** (*Required*): The path to the classifier xml file.
+- **scale** (*Optional*): The scale to perform when processing, this is a `float` value that must be greater than or equal to `1.0`, default is `1.1`.
+- **neighbors** (*Optional*): The minimum number of neighbors required for a match, default is `4`. The higher this number, the more picky the matching will be; lower the number, the more false positives you may experience.

source/_components/image_processing.seven_segments.markdown

@@ -42,8 +42,10 @@ Configuration variables:
 - **y_position** (*Optional*):  Y coordinate of the upper left corner of the area to crop. Defaults to `0`.
 - **height** (*Optional*): Height of the area to crop. Defaults to `0`.
 - **width** (*Optional*): Width of the area to crop. Defaults to `0`.
+- **rotate** (*Optional*): Rotation of the image. Defaults to `0`.
 - **threshold** (*Optional*): Threshold for the difference between the digits and the background. Defaults to `0`.
 - **digits** (*Optional*): Number of digits in the display. Defaults to `-1`.
+- **extra_arguments** (*Optional*): Other arguments to use. Like `-D`, `dilation`, `erosion`, `greyscale`, `make_mono`, etc.
 - **source** array (*Required*): List of image sources.
   - **entity_id** (*Required*): A camera entity id to get picture from.
   - **name** (*Optional*): This parameter allows you to override the name of your `image_processing` entity.
@@ -54,15 +56,15 @@ Configuration variables:
 It's suggested that the first attempt to determine the needed parameters is using `ssocr` directly. This may require a couple of iterations to get the result
 
 ```bash
-$ ssocr -D erosion crop 390 250 490 280 -t 20 -d 4 ss-test.jpg
+$ ssocr -D erosion crop 390 250 490 280 -t 20 -d 4 seven-seg.png
 ```
 
 This would lead to the following entry for the `configuration.yaml` file:
 
 ```yaml
 camera:
   - platform: local_file
-    file_path: /home/fab/.homeassistant/seven-seg.png
+    file_path: /home/homeassistant/.homeassistant/seven-seg.png
     name: seven_segments
 image_processing:
   - platform: seven_segments