Skip to content

Commit 58d1fb9

Browse files
balloobballoob
authored
Merge pull request home-assistant#5059 from home-assistant/rc
0.66.0
2 parents 58c5eb8 + e4d6347 commit 58d1fb9

Some content is hidden

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

46 files changed

+1886
-193
lines changed

‎_config.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -139,14 +139,14 @@ social:
139139

140140
# Home Assistant release details
141141
current_major_version: 0
142-
current_minor_version: 65
143-
current_patch_version: 6
144-
date_released: 2018-03-21
142+
current_minor_version: 66
143+
current_patch_version: 0
144+
date_released: 2018-03-30
145145

146146
# Either # or the anchor link to latest release notes in the blog post.
147147
# Must be prefixed with a # and have double quotes around it.
148148
# Major release:
149-
patch_version_notes: "#release-0656---march-21"
149+
patch_version_notes: "#"
150150
# Minor release (Example #release-0431---april-25):
151151

152152
# Date we moved to Discourse for comments

‎source/_components/alarm_control_panel.ifttt.markdown

Lines changed: 93 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,93 @@
1+
---
2+
layout: page
3+
title: "IFTTT Alarm Control Panel"
4+
description: "Instructions on how to integrate IFTTT-controlled security systems into Home Assistant."
5+
date: 2018-03-10 21:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: ifttt.png
11+
ha_category: Alarm
12+
ha_release: 0.66
13+
---
14+
15+
The `ifttt` platform allows you to integrate security systems that have no open API but can be controlled through [IFTTT](https://ifttt.com/discover).
16+
17+
This platform depends on the [IFTTT](https://home-assistant.io/components/ifttt/) Home Assistant component. See the component's documentation to set it up.
18+
19+
<p class='note'>
20+
It is important to note that this platform fully relies on IFTTT to receive updates when the security system's state changes. Therefore, this platform shows an assumed state.
21+
</p>
22+
23+
To enable this, setup the required IFTTT applets as listed below and add the following lines to your `configuration.yaml` file:
24+
25+
```yaml
26+
# Example configuration.yaml entry
27+
ifttt:
28+
key: YOUR_WEBHOOK_KEY
29+
30+
alarm_control_panel:
31+
- platform: ifttt
32+
name: YOUR_ALARM_NAME
33+
code: YOUR_ALARM_CODE
34+
event_arm_away: YOUR_ARM_AWAY_EVENT
35+
event_arm_home: YOUR_ARM_HOME_EVENT
36+
event_arm_night: YOUR_ARM_NIGHT_EVENT
37+
event_disarm: YOUR_DISARM_EVENT
38+
```
39+
40+
<p class='note warning'>
41+
It is strongly discouraged to use this platform when you don't use encryption; otherwise, your API password will be send unprotected through the IFTTT Webhooks. It is adviced to [setup encryption using Let's Encrypt](https://home-assistant.io/blog/2017/09/27/effortless-encryption-with-lets-encrypt-and-duckdns/).
42+
</p>
43+
44+
{% linkable_title Required IFTTT applets %}
45+
46+
This platform supports the services `alarm_disarm`, `alarm_arm_away`, `alarm_arm_home` and `alarm_arm_night`. For each of these services, an IFTTT webhook will be triggered.
47+
48+
For this system to operate correctly, the following IFTTT applets have to be setup. Obviously, if your alarm device does not support some states, no applets have to be provided for those.
49+
* **IF** Webhook event `YOUR_DISARM_EVENT` is called, **THEN** disarm the alarm system.
50+
* **IF** Webhook event `YOUR_ARM_HOME_EVENT` is called, **THEN** set the alarm system to armed home.
51+
* **IF** Webhook event `YOUR_ARM_NIGHT_EVENT` is called, **THEN** set the alarm system to armed away.
52+
* **IF** Webhook event `YOUR_DISARM_EVENT` is called, **THEN** set the alarm system to armed night.
53+
* **IF** the alarm system was disarmed, **THEN** perform a Webhook `POST` web request to url `https://HASS_URL/api/services/alarm_control_panel/ifttt_push_alarm_state?api_password=API_PASSWORD` with content type `application/json` and body `{"entity_id": "alarm_control_panel.DEVICE_NAME", "state": "disarmed"}`.
54+
* **IF** the alarm system state changed to armed home, **THEN** perform a Webhook `POST` web request to url `https://HASS_URL/api/services/alarm_control_panel/ifttt_push_alarm_state?api_password=API_PASSWORD` with content type `application/json` and body `{"entity_id": "alarm_control_panel.DEVICE_NAME", "state": "armed_home"}`.
55+
* **IF** the alarm system state changed to armed away, **THEN** perform a Webhook `POST` web request to url `https://HASS_URL/api/services/alarm_control_panel/ifttt_push_alarm_state?api_password=API_PASSWORD` with content type `application/json` and body `{"entity_id": "alarm_control_panel.DEVICE_NAME", "state": "armed_away"}`.
56+
* **IF** the alarm system state changed to armed night, **THEN** perform a Webhook `POST` web request to url `https://HASS_URL/api/services/alarm_control_panel/ifttt_push_alarm_state?api_password=API_PASSWORD` with content type `application/json` and body `{"entity_id": "alarm_control_panel.DEVICE_NAME", "state": "armed_night"}`.
57+
58+
59+
{% configuration %}
60+
name:
61+
description: The name of your Home Assistant alarm control panel.
62+
required: false
63+
type: string
64+
code:
65+
description: The code for the alarm control panel.
66+
required: false
67+
type: string
68+
event_arm_away:
69+
description: IFTTT webhook event to call when the state is set to armed away.
70+
required: false
71+
type: string
72+
default: alarm_arm_away
73+
event_arm_home:
74+
description: IFTTT webhook event to call when the state is set to armed home.
75+
required: false
76+
type: string
77+
default: alarm_arm_home
78+
event_arm_night:
79+
description: IFTTT webhook event to call when the state is set to armed night.
80+
required: false
81+
type: string
82+
default: alarm_arm_night
83+
event_disarm:
84+
description: IFTTT webhook event to call when the state is set to disarmed.
85+
required: false
86+
type: string
87+
default: alarm_disarm
88+
optimistic:
89+
description: Specify if the state will be updated by a ifttt_push_alarm_state call (false) or can be set immediately (true).
90+
required: false
91+
type: boolean
92+
default: false
93+
{% endconfiguration %}

‎source/_components/binary_sensor.bmw_connected_drive.markdown

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
layout: page
3+
title: "BMW connected drive"
4+
description: "Instructions on how to setup your BMW connected drive account with Home Assistant."
5+
date: 2018-02-22 23:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: bmw.png
11+
ha_category: Binary Sensor
12+
ha_release: 0.66
13+
---
14+
15+
16+
The `bmw_connected_drive` platform allows you to import data on your BMW into Home Assistant.
17+
18+
The binary sensors will be automatically configured if 'bmw_connected_drive' component is configured.
19+
20+
For more configuration information see the [bmw_connected_drive component](/components/bmw_connected_drive/) documentation.

‎source/_components/camera.proxy.markdown

Lines changed: 40 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -29,17 +29,46 @@ camera:
2929
max_image_width: 720
3030
```
3131
32-
Configuration variables:
33-
34-
- **entity_id** (*Required*): The ID of another Home Assistant camera to post-process.
35-
- **name** (*Optional*): This parameter allows you to override the name of your camera.
36-
- **max_image_width** (*Optional*): The maximum width of single images taken from the camera (aspect ratio will be maintained).
37-
- **max_stream_width** (*Optional*): The maximum width of the MJPEG stream from the camera (aspect ratio will be maintained).
38-
- **image_quality** (*Optional*): The quality level used for resulting JPEG for snapshots (default: 75).
39-
- **stream_quality** (*Optional*): The quality level used for resulting MJPEG streams (default: 75).
40-
- **image_refresh_rate** (*Optional*): The minimum time in seconds between generating successive image snapshots.
41-
- **force_resize** (*Optional*): Resize the image even if the resulting image would take up more bandwidth than the original.
42-
- **cache_images** (*Optional*): Preserve the last image and re-send in the case the camera is not responding.
32+
{% configuration %}
33+
entity_id:
34+
description: The ID of another Home Assistant camera to post-process.
35+
required: true
36+
type: string
37+
name:
38+
description: This parameter allows you to override the name of your camera.
39+
required: false
40+
type: string
41+
max_image_width:
42+
description: The maximum width of single images taken from the camera (aspect ratio will be maintained).
43+
required: false
44+
type: integer
45+
max_stream_width:
46+
description: The maximum width of the MJPEG stream from the camera (aspect ratio will be maintained).
47+
required: false
48+
type: integer
49+
image_quality:
50+
description: The quality level used for resulting JPEG for snapshots.
51+
required: false
52+
type: integer
53+
default: 75
54+
stream_quality:
55+
description: The quality level used for resulting MJPEG streams.
56+
required: false
57+
type: integer
58+
default: 75
59+
image_refresh_rate:
60+
description: The minimum time in seconds between generating successive image snapshots.
61+
required: false
62+
type: float
63+
force_resize:
64+
description: Resize the image even if the resulting image would take up more bandwidth than the original.
65+
required: false
66+
type: boolean
67+
cache_images:
68+
description: Preserve the last image and re-send in the case the camera is not responding.
69+
required: false
70+
type: boolean
71+
{% endconfiguration %}
4372
4473
4574
## {% linkable_title Examples %}

‎source/_components/cover.group.markdown

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
---
2+
layout: page
3+
title: "Cover Group"
4+
description: "Instructions how to setup grouped covers in Home Assistant."
5+
date: 2018-02-11 10:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
ha_category: Cover
11+
ha_release: 0.66
12+
ha_iot_class: "Local Push"
13+
logo: home-assistant.png
14+
---
15+
16+
The `group` platform can create a cover that combines several cover entities into one.
17+
18+
To enable `Cover Groups` in your installation, add the following to your `configuration.yaml` file:
19+
20+
```yaml
21+
# Example configuration.yaml entry
22+
cover:
23+
- platform: group
24+
entities:
25+
- cover.hall_window
26+
- cover.living_room_window
27+
```
28+
29+
{% configuration %}
30+
name:
31+
description: Name to use in the frontend.
32+
required: false
33+
type: string
34+
default: "Cover Group"
35+
entities:
36+
description: List of all cover entities you want to control.
37+
required: true
38+
type: [string | list]
39+
{% endconfiguration %}
40+
41+
## {% linkable_title Functionality %}
42+
43+
It works best if you group covers with the same supported features together (like support for `open`/`close`/`stop`/`position`/`tilt controls`), but is not limited to it. In case you have bundled covers with different features together, the controls will only affect those covers that support the actions.

‎source/_components/deconz.markdown

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,11 @@ ha_iot_class: "Local Push"
2020
### {% linkable_title Supported device types %}
2121

2222
- [Zigbee Lights](/components/light.deconz/)
23+
- [Consumption Sensors](/components/sensor.deconz/)
2324
- [Humidity Sensors](/components/sensor.deconz/)
2425
- [Light Level Sensors](/components/sensor.deconz/)
2526
- [OpenClose Detectors](/components/binary_sensor.deconz/)
27+
- [Power Sensors](/components/sensor.deconz/)
2628
- [Presence Detectors](/components/binary_sensor.deconz/)
2729
- [Pressure Sensors](/components/sensor.deconz/)
2830
- [Switches (Remote Controls)](/components/sensor.deconz/)

‎source/_components/downloader.markdown

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,3 +42,29 @@ This will download the file from the given URL.
4242
| `subdir` | yes | Download into subdirectory of **download_dir** |
4343
| `filename` | yes | Determine the filename. |
4444
| `overwrite` | yes | Whether to overwrite the file or not, defaults to `false`. |
45+
46+
### {% linkable_title Download Status Events %}
47+
48+
When a download finished successfully, Home Assistant will emit a 'downloader_download_completed' event to the event bus which you can use to write automations against.
49+
In case download failed another event 'downloader_download_failed' is emitted to indicate that the download did not complete successfully.
50+
51+
Along with the event the following payload parameters are available:
52+
53+
| Parameter | Description |
54+
|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
55+
| `url` | The `url` that was requested.|
56+
| `filename` | The `name` of the file that was being downloaded.|
57+
58+
#### Example Automation:
59+
60+
```yaml
61+
- alias: Download Failed Notification
62+
trigger:
63+
platform: event
64+
event_type: downloader_download_failed
65+
action:
66+
service: persistent_notification.create
67+
data_template:
68+
message: "{{trigger.event.data.filename}} download failed"
69+
title: "Download Failed"
70+
```

‎source/_components/fan.xiaomi_miio.markdown

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -71,6 +71,15 @@ name:
7171
7272
## {% linkable_title Platform Services %}
7373
74+
### {% linkable_title Service `fan.set_speed` %}
75+
76+
Set the fan speed/operation mode.
77+
78+
| Service data attribute | Optional | Description |
79+
|---------------------------|----------|---------------------------------------------------------------------|
80+
| `entity_id` | yes | Only act on a specific air purifier. Else targets all. |
81+
| `speed` | no | Fan speed. Valid values are 'Auto', 'Silent', 'Favorite' and 'Idle' |
82+
7483
### {% linkable_title Service `fan.xiaomi_miio_set_buzzer_on` %}
7584

7685
Turn the buzzer on.

‎source/_components/fan.zha.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: "ZigBee Home Automation Fan"
4+
description: "Instructions how to setup ZigBee Home Automation fans within Home Assistant."
5+
date: 2018-02-10 00:00
6+
sidebar: true
7+
comments: false
8+
sharing: true
9+
footer: true
10+
logo: zigbee.png
11+
ha_category: Fan
12+
ha_iot_class: "Local Polling"
13+
ha_release: 0.66
14+
---
15+
16+
To get your ZigBee fans working with Home Assistant, follow the instructions for the general [ZigBee Home Automation component](/components/zha/).

0 commit comments

Comments
 (0)