Skip to content

Commit abfd390

Browse files
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

Lines changed: 4 additions & 4 deletions
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

File renamed without changes.
Lines changed: 20 additions & 0 deletions
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+
Lines changed: 20 additions & 0 deletions
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/).
Lines changed: 32 additions & 0 deletions
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.
Lines changed: 36 additions & 0 deletions
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).
Lines changed: 58 additions & 0 deletions
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

Lines changed: 1 addition & 1 deletion
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

Lines changed: 2 additions & 0 deletions
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`

0 commit comments

Comments
 (0)