Skip to content

Commit abfd390

Browse files
balloobballoob
authored
Merge pull request home-assistant#2823 from home-assistant/release-0-47
0.47
2 parents dbcca71 + 8fc3193 commit abfd390

File tree

104 files changed

+1650
-166
lines changed

Some content is hidden

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

104 files changed

+1650
-166
lines changed

‎_config.yml

+4-4
Original file line numberDiff line numberDiff line change
@@ -140,13 +140,13 @@ social:
140140

141141
# Home Assistant release details
142142
current_major_version: 0
143-
current_minor_version: 46
144-
current_patch_version: 1
145-
date_released: 2017-06-09
143+
current_minor_version: 47
144+
current_patch_version: 0
145+
date_released: 2017-06-17
146146

147147
# Either # or the anchor link to latest release notes in the blog post.
148148
# Must be prefixed with a # and have double quotes around it.
149149
# Major release:
150-
patch_version_notes: "#release-0461---june-9"
150+
patch_version_notes: "#"
151151
# Minor release (Example #release-0431---april-25):
152152

‎source/_addons/bluetooth_bcm43xx.markdonw renamed to ‎source/_addons/bluetooth_bcm43xx.markdown

File renamed without changes.

‎source/_addons/dnsmasq.markdonw renamed to ‎source/_addons/dnsmasq.markdown

File renamed without changes.

‎source/_components/alarm_control_panel.spc.markdown

+20
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
layout: page
3+
title: "Vanderbilt SPC Alarm"
4+
description: "Instructions how to setup the Vanderbilt SPC Alarm control panel within Home Assistant."
5+
date: 2017-05-18 22:01
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: vanderbilt_spc.png
11+
ha_category: Alarm
12+
ha_release: 0.47
13+
ha_iot_class: "Local Push"
14+
---
15+
16+
17+
The `spc` alarm control panel platform allows you to control your [Vanderbilt SPC](http://www.spc-intruder-detection.com/ssp-spc/) alarms.
18+
19+
The requirement is that you have setup your [SPC hub](/components/spc/).
20+

‎source/_components/binary_sensor.spc.markdown

+20
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
layout: page
3+
title: "SPC Binary Sensor"
4+
description: "Instructions how to integrate Vanderbilt SPC binary sensors into Home Assistant."
5+
date: 2017-05-18 22:05
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: vanderbilt_spc.png
11+
ha_release: 0.47
12+
ha_category: Binary Sensor
13+
ha_iot_class: "Local Push"
14+
---
15+
16+
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.
17+
18+
Check the [type/class](/components/binary_sensor/) list for a possible visualization of your zone. Currently motion, smoke and door sensors are supported.
19+
20+
The requirement is that you have setup your [SPC hub](/components/spc/).

‎source/_components/binary_sensor.tapsaff.markdown

+32
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
layout: page
3+
title: "Taps Aff"
4+
description: "Instructions how to use the Taps Aff binary sensor in Home Assistant."
5+
date: 2017-05-28 18:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: tapsaff.png
11+
ha_category: Weather
12+
featured: false
13+
ha_release: 0.47
14+
ha_iot_class: "Local Polling"
15+
---
16+
17+
18+
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).
19+
20+
To enable this sensor, add the following lines to your `configuration.yaml`:
21+
22+
```yaml
23+
# Example configuration.yaml entry
24+
binary_sensor:
25+
- platform: tapsaff
26+
location: glasgow
27+
```
28+
29+
Configuration variables:
30+
31+
- **location** (*Required*): The location for the Taps Aff. It must be configured with a UK postcode or city to work.
32+
- **name** (*Optional*): The name to use when displaying this sensor.

‎source/_components/camera.onvif.markdown

+36
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
layout: page
3+
title: "ONVIF Camera"
4+
description: "Instructions on how to integrate a ONVIF camera within Home Assistant."
5+
date: 2017-06-09 21:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: onvif.png
11+
ha_category: Camera
12+
ha_release: 0.47
13+
---
14+
15+
16+
The `ONVIF` platform allows you to use an ONVIF camera in Home Assistant. This requires FFmpeg component to be already configured.
17+
18+
To enable your ONVIF in your installation, add the following to your `configuration.yaml` file:
19+
20+
```yaml
21+
# Example configuration.yaml entry
22+
camera:
23+
- platform: onvif
24+
host: 192.168.1.111
25+
```
26+
27+
Configuration variables:
28+
29+
- **host** (*Required*): An IP or hostname of the camera.
30+
- **name** (*Optional*): Override the name of your camera.
31+
- **username** (*Optional*): The username for the camera.
32+
- **password** (*Optional*): The password for the camera.
33+
- **port** (*Optional*): The port for the camera. This defaults to 5000
34+
35+
36+
If you are running into trouble with this sensor, please refer to the [Troubleshooting section](/components/ffmpeg/#troubleshooting).

‎source/_components/climate.flexit.markdown

+58
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
---
2+
layout: page
3+
title: "Flexit A/C controller"
4+
description: "Instructions how to integrate Flexit A/C unit into Home Assistant."
5+
date: 2017-06-02 16:30 +0200
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: flexit.png
11+
ha_category: Climate
12+
ha_release: 0.47
13+
ha_iot_class: "Local Polling"
14+
---
15+
16+
Integrates [Flexit](https://www.flexit.no/en/) Air Conditioning unit into Home Assistant.
17+
18+
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/)
19+
20+
To enable this platform, add the following lines to your `configuration.yaml` file:
21+
22+
```yaml
23+
# Example configuration.yaml entry
24+
climate:
25+
- platform: flexit
26+
slave: 21
27+
```
28+
29+
Configuration variables:
30+
31+
- **slave** (*Required*): The slave ID of the modbus adapter, set using DIP-switches.
32+
- **name** (*Optional*): Displayed name of the A/C unit
33+
34+
<p class='note'>
35+
This component requires the [Modbus](/components/modbus/) component to be set up to work
36+
</p>
37+
38+
Full configuration example including modbus setup shown below:
39+
40+
DIP-switch settings on the CI66:
41+
1=ON, 2=ON, 3=OFF, 4=ON, 5=OFF, 6=ON, 7=ON, 8=ON
42+
43+
```yaml
44+
# Full example configuration.yaml entry
45+
modbus:
46+
type: serial
47+
method: rtu
48+
port: /dev/ttyUSB0
49+
baudrate: 56000
50+
stopbits: 1
51+
bytesize: 8
52+
parity: E
53+
54+
climate:
55+
- platform: flexit
56+
name: Main A/C
57+
slave: 21
58+
```

‎source/_components/cover.garadget.markdown

+1-1
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ sidebar: true
77
comments: false
88
sharing: true
99
footer: true
10-
logo: garadget_logo.jpg
10+
logo: garadget.png
1111
ha_category: Cover
1212
ha_release: 0.32
1313
ha_iot_class: "Cloud Polling"

‎source/_components/cover.mqtt.markdown

+2
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,8 @@ Configuration variables:
4747
- **qos** (*Optional*): The maximum QoS level of the state topic. Default is `0`. Will also be used when publishing messages.
4848
- **retain** (*Optional*): If the published message should have the retain flag on or not. Default is `false`.
4949
- **value_template** (*Optional*): Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract a value from the payload.
50+
- **set_position_topic** (*Optional*): The MQTT topic to publish position commands to.
51+
- **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.
5052
- **tilt_command_topic** (*Optional*): The MQTT topic to publish commands to control the cover tilt.
5153
- **tilt_status_topic** (*Optional*): The MQTT topic subscribed to receive tilt status update values.
5254
- **tilt_min** (*Optional*): The minimum tilt value. Default is `0`

‎source/_components/dyson.markdown

+60
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
---
2+
layout: page
3+
title: "Dyson"
4+
description: "Instructions how to integrate Dyson into Home Assistant."
5+
date: 2017-05-27 10:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: dyson.png
11+
ha_category: Hub
12+
ha_iot_class: "Cloud Polling"
13+
ha_release: 0.47
14+
---
15+
16+
The `dyson` component is the main component to integrate all [Dyson](https://dyson.com) related platforms.
17+
18+
Currently limited to Cool Link Purifier.
19+
20+
To enable this component, add the following lines to your `configuration.yaml`:
21+
22+
```yaml
23+
dyson:
24+
username: <dyson_account_user_email>
25+
password: <dyson_acount_password>
26+
language: <dyson_account_language>
27+
devices:
28+
- device_id: <device_id_1>
29+
device_ip: <device_ip_1>
30+
- device_id: <device_id_2>
31+
device_ip: <device_ip_2>
32+
...
33+
```
34+
35+
Configuration variables:
36+
37+
- **username** (*Required*): Dyson account username (email address)
38+
- **password** (*Required*): Dyson account password
39+
- **language** (*Required*): Dyson account language country code. Known working codes: `FR`, `NL`, `UK`, `AU`. But others codes should work.
40+
- **devices** (*Optional*): List of devices
41+
- **device_id** (*Required*): Device ID. Available in the mobiles applications (*Settings* page)
42+
- **device_ip** (*Required*): Device IP address
43+
44+
`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).
45+
To find devices IP address, you can use your router or `nmap`:
46+
47+
```bash
48+
$ nmap -p 1883 XXX.XXX.XXX.XXX/YY -- open
49+
```
50+
51+
Where:
52+
53+
- **XXX.XXX.XXX.XXX** is your network address
54+
- **YY** is your network mask
55+
56+
For example:
57+
58+
```bash
59+
$ nmap -p 1883 192.168.0.0/24 -- open
60+
```

‎source/_components/fan.dyson.markdown

+24
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
layout: page
3+
title: "Dyson Purifier Fan"
4+
description: "Instructions how to setup the Dyson Purifier fans within Home Assistant."
5+
date: 2017-05-27 10:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: dyson.png
11+
ha_category: Fan
12+
ha_iot_class: "Cloud Polling"
13+
ha_release: 0.47
14+
---
15+
16+
17+
The `dyson` fan platform allows you to control your Dyson Purifier fans.
18+
19+
You have first to setup the [Dyson component](/components/dyson/)
20+
21+
### {% linkable_title Supported fan devices %}
22+
23+
- Pure Cool link (desk and tower)
24+
- Pure Hot+cool link (but heating is not yet supported)

‎source/_components/ha.markdown

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
layout: page
3-
title: "Home Assistant 0.46"
3+
title: "Home Assistant 0.47"
44
description: ""
55
date: 2016-12-16 17:00
66
sidebar: true
@@ -9,7 +9,7 @@ sharing: true
99
footer: true
1010
logo: home-assistant.png
1111
ha_category: Other
12-
ha_release: 0.46
12+
ha_release: 0.47
1313
---
1414

1515
Details about the latest release can always be found at:

‎source/_components/image_processing.opencv.markdown

+38-3
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,44 @@ footer: true
1010
logo: opencv.png
1111
ha_category: Image Processing
1212
featured: false
13-
ha_release: 0.44
13+
ha_release: 0.47
1414
---
1515

16-
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).
16+
[OpenCV](http://www.opencv.org) is an open source computer vision image and video processing library.
1717

18-
Please refer to the [component](/components/opencv/) configuration on how to setup the image processor.
18+
Some pre-defined classifiers can be found here: https://github.com/opencv/opencv/tree/master/data
19+
20+
### {% linkable_title Configuration %}
21+
22+
To setup OpenCV with Home Assistant, add the following section to your `configuration.yaml` file:
23+
24+
```yaml
25+
# Example configuration.yaml entry
26+
image_processing:
27+
- platform: opencv
28+
name: Front Door Faces
29+
source:
30+
- entity_id: camera.front_door
31+
classifier:
32+
mom: /path/to/classifier.xml
33+
```
34+
35+
- **name** (*Required*): The name of the OpenCV image processor.
36+
- **source** array (*Required*): List of image sources.
37+
- **entity_id** (*Required*): A camera entity id to get picture from.
38+
- **name** (*Optional*): This parameter allows you to override the name of your `image_processing` entity.
39+
- **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.
40+
41+
**classifier** may also be defined as a dictionary of names to classifier configurations:
42+
43+
```yaml
44+
mom:
45+
file: /path/to/classifier/xml
46+
neighbors: 4
47+
min_size: (40, 40)
48+
scale: 1.1f
49+
```
50+
51+
- **file** (*Required*): The path to the classifier xml file.
52+
- **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`.
53+
- **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

+4-2
Original file line numberDiff line numberDiff line change
@@ -42,8 +42,10 @@ Configuration variables:
4242
- **y_position** (*Optional*): Y coordinate of the upper left corner of the area to crop. Defaults to `0`.
4343
- **height** (*Optional*): Height of the area to crop. Defaults to `0`.
4444
- **width** (*Optional*): Width of the area to crop. Defaults to `0`.
45+
- **rotate** (*Optional*): Rotation of the image. Defaults to `0`.
4546
- **threshold** (*Optional*): Threshold for the difference between the digits and the background. Defaults to `0`.
4647
- **digits** (*Optional*): Number of digits in the display. Defaults to `-1`.
48+
- **extra_arguments** (*Optional*): Other arguments to use. Like `-D`, `dilation`, `erosion`, `greyscale`, `make_mono`, etc.
4749
- **source** array (*Required*): List of image sources.
4850
- **entity_id** (*Required*): A camera entity id to get picture from.
4951
- **name** (*Optional*): This parameter allows you to override the name of your `image_processing` entity.
@@ -54,15 +56,15 @@ Configuration variables:
5456
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
5557

5658
```bash
57-
$ ssocr -D erosion crop 390 250 490 280 -t 20 -d 4 ss-test.jpg
59+
$ ssocr -D erosion crop 390 250 490 280 -t 20 -d 4 seven-seg.png
5860
```
5961

6062
This would lead to the following entry for the `configuration.yaml` file:
6163

6264
```yaml
6365
camera:
6466
- platform: local_file
65-
file_path: /home/fab/.homeassistant/seven-seg.png
67+
file_path: /home/homeassistant/.homeassistant/seven-seg.png
6668
name: seven_segments
6769
image_processing:
6870
- platform: seven_segments

0 commit comments

Comments
 (0)