From a7601b0760038797791e2829cf7ceb3642299bb5 Mon Sep 17 00:00:00 2001 From: On Freund Date: Sun, 6 Sep 2020 22:04:53 +0300 Subject: [PATCH 01/14] Add sensor as a supported Risco platform (#14411) --- source/_integrations/risco.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/risco.markdown b/source/_integrations/risco.markdown index 42f3b530682..eea0e8beb5c 100644 --- a/source/_integrations/risco.markdown +++ b/source/_integrations/risco.markdown @@ -94,3 +94,4 @@ This undoes a zone bypass. You can only unbypass a zone when the partitions it b - [Alarm Control Panel](/integrations/alarm_control_panel/) - [Binary Sensor](/integrations/binary_sensor/) +- [Sensor](/integrations/sensor/) From 16b2cda65976ff3a126e4e1d80c84c12b81f5a65 Mon Sep 17 00:00:00 2001 From: Bouwe Westerdijk <11290930+bouwew@users.noreply.github.com> Date: Sun, 6 Sep 2020 22:26:51 +0200 Subject: [PATCH 02/14] Plugwise - describe how to use OPTIONS (#13940) --- source/_integrations/plugwise.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_integrations/plugwise.markdown b/source/_integrations/plugwise.markdown index 4bda94c1517..b92b0547d70 100644 --- a/source/_integrations/plugwise.markdown +++ b/source/_integrations/plugwise.markdown @@ -45,6 +45,8 @@ The Plugwise Smile(s) present in your network will be automatically detected via Repeat the above procedure for each Smile gateway (i.e., if you have an Adam setup and a P1 DSMR you'll have to add two integrations). +After adding the Plugwise integration(s), the default Smile-data refresh-interval can be changed by pressing the "OPTIONS" button: change the number via the up- or down-button and press "SUBMIT". +
When you have an Anna and an Adam, make sure to only configure the Adam integration. You can press the "IGNORE" button on the Anna integration to remove this integration. In case you need to rediscover the Adam integration, make sure to click the "STOP IGNORING" button on the Plugwise integration first, available via "show ignored integrations".
From 071298ff1bc54b26e82f701458f02418d99c78cf Mon Sep 17 00:00:00 2001 From: Philip Allgaier Date: Mon, 7 Sep 2020 00:23:59 +0200 Subject: [PATCH 03/14] Clarifications for the Spotify integration (#14416) --- source/_integrations/spotify.markdown | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/source/_integrations/spotify.markdown b/source/_integrations/spotify.markdown index 824b8625ebd..5f6e0ba50e7 100644 --- a/source/_integrations/spotify.markdown +++ b/source/_integrations/spotify.markdown @@ -30,11 +30,15 @@ To create the required Spotify application: - Visit the [My Applications](https://developer.spotify.com/my-applications/#!/applications) page. - Select **Create An App**. Enter any name and description. - Once your application is created, view it and copy your **Client ID** and **Client Secret**, which are used in the Home Assistant configuration file. -- Add a **Redirect URI** in one of the following forms: +- On the Spotify page, enter the **Edit Settings** dialog of your newly created application and add a **Redirect URI**: - If you are not using SSL: `http://:/auth/external/callback` - If you are using SSL: `https://:/auth/external/callback` - Click **Save** after adding the URI. +
+ Your Home Assitant instance does not need to be exposed to the internet. It works just fine with local IP addresses. +
+ ## Configuration To add Spotify to your installation, add the following to your `configuration.yaml` file: @@ -61,18 +65,18 @@ client_secret: After you have set up the above: -- Go to the integrations page in the Home Assistant frontend -- Go to **Integrations** +- Go to the **Configurations** page in the Home Assistant frontend. +- Go to **Integrations**. - Add a new **Spotify** integration. - Follow the steps shown to authenticate Home Assistant with your Spotify account.
- If you receive an `INVALID_CLIENT: Invalid redirect URI` error while trying to authenticate with your Spotify account, make sure to check the Redirect URI in the address bar after adding the new integration. Compare this value with the Redirect URL defined in the Spotify Developer Portal. + If you receive an `INVALID_CLIENT: Invalid redirect URI` error while trying to authenticate with your Spotify account, make sure to check the Redirect URI in the address bar after adding the new integration. Compare this value with the Redirect URI defined in the Spotify Developer Portal.
-## URI Links For Playlists +## URI Links for Playlists You can send playlists to Spotify using the `"media_content_type": "playlist"`, which are part of the [media_player.play_media](/integrations/media_player/#service-media_playerplay_media) service. From 4f7216c7c999b383833dd8738d3f32388e89623b Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Mon, 7 Sep 2020 00:36:27 +0200 Subject: [PATCH 04/14] State condition can also accept an input_* Entity ID as state value (#14412) --- source/_docs/scripts/conditions.markdown | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/source/_docs/scripts/conditions.markdown b/source/_docs/scripts/conditions.markdown index f02f38f72e1..74ffbd3886f 100644 --- a/source/_docs/scripts/conditions.markdown +++ b/source/_docs/scripts/conditions.markdown @@ -225,6 +225,17 @@ condition: state: heat ``` +Finally, the `state` option accepts helper entities (also known as `input_*` +entities). The condition will pass if the state of the entity matches the state +of the given helper entity. + +```yaml +condition: + condition: state + entity_id: alarm_control_panel.home + state: input_select.guest_mode +``` + ### Sun condition #### Sun state condition From 1e9d3cb5fcbfdc4046ff33faaeb03b9fd8180949 Mon Sep 17 00:00:00 2001 From: Alexei Chetroi Date: Mon, 7 Sep 2020 02:44:17 -0400 Subject: [PATCH 05/14] Update ZHA radio types (#14410) --- source/_integrations/zha.markdown | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown index 7529cf2b66d..9c9db798ac7 100644 --- a/source/_integrations/zha.markdown +++ b/source/_integrations/zha.markdown @@ -103,7 +103,8 @@ a new pop-up asking for a radio type. In the pop-up: | ------------- | ------------- | | `ezsp` | Silicon Labs EmberZNet protocol (ex; Elelabs, HUSBZB-1, Telegesis) | | `deconz` | dresden elektronik deCONZ protocol: ConBee I/II, RaspBee I/II | -| `ti_cc` | Texas Instruments Z-Stack ZNP protocol (ex: CC253x, CC26x2, CC13x2) | +| `znp` | Actively maintained: Texas Instruments Z-Stack ZNP protocol (ex: CC253x, CC26x2, CC13x2) | +| `ti_cc` | Legacy & HA12 ZStack Texas Instruments Z-Stack ZNP protocol (ex: CC253x, CC26x2, CC13x2) | | `zigate` | ZiGate Serial protocol: PiZiGate, ZiGate USB-TTL, ZiGate WiFi | | `xbee` | Digi XBee ZB Coordinator Firmware protocol (Digi XBee Series 2, 2C, 3) | @@ -202,6 +203,7 @@ logger: zigpy_xbee.zigbee.application: debug zigpy_xbee.api: debug zigpy_zigate: debug + zigpy_znp: debug zhaquirks: debug ``` From 117a28a2e3b95496554881a6e5910cfa89c2142e Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Mon, 7 Sep 2020 08:53:07 +0200 Subject: [PATCH 06/14] Bump sinatra from 2.0.8.1 to 2.1.0 (#14419) Bumps [sinatra](https://github.com/sinatra/sinatra) from 2.0.8.1 to 2.1.0. - [Release notes](https://github.com/sinatra/sinatra/releases) - [Changelog](https://github.com/sinatra/sinatra/blob/master/CHANGELOG.md) - [Commits](https://github.com/sinatra/sinatra/compare/v2.0.8.1...v2.1.0) Signed-off-by: dependabot[bot] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- Gemfile | 2 +- Gemfile.lock | 10 +++++----- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/Gemfile b/Gemfile index bda3f75098c..e08d61455ce 100644 --- a/Gemfile +++ b/Gemfile @@ -18,7 +18,7 @@ group :jekyll_plugins do gem 'jekyll-commonmark', '1.3.1' end -gem 'sinatra', '2.0.8.1' +gem 'sinatra', '2.1.0' gem 'nokogiri', '1.10.10' # Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem diff --git a/Gemfile.lock b/Gemfile.lock index 3111dee22e0..b3f27a004e3 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -81,7 +81,7 @@ GEM forwardable-extended (~> 2.6) public_suffix (4.0.6) rack (2.2.3) - rack-protection (2.0.8.1) + rack-protection (2.1.0) rack rake (13.0.1) rb-fsevent (0.10.4) @@ -100,10 +100,10 @@ GEM ffi (~> 1.9) sassc (2.4.0-x64-mingw32) ffi (~> 1.9) - sinatra (2.0.8.1) + sinatra (2.1.0) mustermann (~> 1.0) - rack (~> 2.0) - rack-protection (= 2.0.8.1) + rack (~> 2.2) + rack-protection (= 2.1.0) tilt (~> 2.0) stringex (2.8.5) terminal-table (1.8.0) @@ -130,7 +130,7 @@ DEPENDENCIES nokogiri (= 1.10.10) rake (= 13.0.1) sass-globbing (= 1.1.5) - sinatra (= 2.0.8.1) + sinatra (= 2.1.0) stringex (= 2.8.5) tzinfo (~> 2.0) tzinfo-data From d8f8f06ac35cdc513157214b2d785befbd0b89ae Mon Sep 17 00:00:00 2001 From: Evan Bruhn Date: Mon, 7 Sep 2020 16:54:03 +1000 Subject: [PATCH 07/14] Update Logi Circle docs (#14417) Logitech have updated their form to specify that requests are only processed once per month. --- source/_integrations/logi_circle.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/logi_circle.markdown b/source/_integrations/logi_circle.markdown index 66cced5bff2..f5778bcb0a6 100644 --- a/source/_integrations/logi_circle.markdown +++ b/source/_integrations/logi_circle.markdown @@ -32,7 +32,7 @@ The `logi_circle` implementation allows you to integrate your [Logi Circle](http * At the time you submit your request to Logitech, you need to demonstrate that you have exclusive control of the fully qualified domain name in your redirect URI. An active Home Assistant instance at the redirect URI will suffice. If you don't want to expose your Home Assistant instance publicly, you may also place a static page at the redirect URI with a short message that you will manage redirection of the authorization token to your local Home Assistant instance. Free static hosts that issue subdomains for hosting (e.g., Netlify) are permitted. * As the redirect URI must be public facing, no local/reserved TLDs are permitted (eg. .local, .localhost, .example, etc. are not allowed). -Please note that the turn-around time for API access takes a few business days after which you will be contacted by Logitech using the email address you provided in the form. +Please note that the turn-around time for API access takes up to a month after which you will be contacted by Logitech using the email address you provided in the form. ## Configuration From 68a377989535bfd1c457b02089e93281fe61d7dc Mon Sep 17 00:00:00 2001 From: Guido Schmitz Date: Mon, 7 Sep 2020 15:49:07 +0200 Subject: [PATCH 08/14] Add devolo remote devices as binary sensors (#14288) --- source/_integrations/devolo_home_control.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_integrations/devolo_home_control.markdown b/source/_integrations/devolo_home_control.markdown index bded4431b74..6a50223ff9e 100644 --- a/source/_integrations/devolo_home_control.markdown +++ b/source/_integrations/devolo_home_control.markdown @@ -42,8 +42,10 @@ The integration provides support for the following Z-Wave devices: - devolo Door/Window Contact - devolo Flood Sensor +- devolo Key-Fob Switch - devolo Motion Sensor - devolo Smoke Detector +- devolo Wall Switch - Fibaro Floor Sensor - Fibaro Motion Sensor - Fibaro Smoke Sensor From c859cd071dd532826c8678e03f7f01d07494169a Mon Sep 17 00:00:00 2001 From: Anders Melchiorsen Date: Mon, 7 Sep 2020 16:11:27 +0200 Subject: [PATCH 09/14] Add state trigger examples with to/for and from/for (#14363) --- source/_docs/automation/trigger.markdown | 25 ++++++++++++++++++++++-- 1 file changed, 23 insertions(+), 2 deletions(-) diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown index 85ea844e05a..5658838c4e9 100644 --- a/source/_docs/automation/trigger.markdown +++ b/source/_docs/automation/trigger.markdown @@ -152,9 +152,30 @@ automation: from: "not_home" # Optional to: "home" +``` - # If given, will trigger when state has been the to state for X time. - for: "01:10:05" +#### Holding a state + +You can use `for` to have the state trigger only fire if the state holds for some time. + +```yaml +automation: + trigger: + platform: state + entity_id: light.office + # Must stay "on" for 30 seconds + to: "on" + for: "00:00:30" +``` + +```yaml +automation: + trigger: + platform: state + entity_id: media_player.kitchen + # Not "playing" for 30 seconds + from: "playing" + for: "00:00:30" ``` You can also use templates in the `for` option. From c6c4936172300b97f249ea0313d02126276897e8 Mon Sep 17 00:00:00 2001 From: Hedda Date: Mon, 7 Sep 2020 16:32:00 +0200 Subject: [PATCH 10/14] Update zha.markdown to clarify Z-Stack 3.x.x vs Z-Stack Home 1.2.x (#14421) Co-authored-by: Franck Nijhof --- source/_integrations/zha.markdown | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown index 9c9db798ac7..576fd14c220 100644 --- a/source/_integrations/zha.markdown +++ b/source/_integrations/zha.markdown @@ -101,12 +101,12 @@ a new pop-up asking for a radio type. In the pop-up: | Radio Type | Zigbee Radio Hardware | | ------------- | ------------- | -| `ezsp` | Silicon Labs EmberZNet protocol (ex; Elelabs, HUSBZB-1, Telegesis) | -| `deconz` | dresden elektronik deCONZ protocol: ConBee I/II, RaspBee I/II | -| `znp` | Actively maintained: Texas Instruments Z-Stack ZNP protocol (ex: CC253x, CC26x2, CC13x2) | -| `ti_cc` | Legacy & HA12 ZStack Texas Instruments Z-Stack ZNP protocol (ex: CC253x, CC26x2, CC13x2) | -| `zigate` | ZiGate Serial protocol: PiZiGate, ZiGate USB-TTL, ZiGate WiFi | -| `xbee` | Digi XBee ZB Coordinator Firmware protocol (Digi XBee Series 2, 2C, 3) | +| `ezsp` | Silicon Labs EmberZNet protocol (e.g., Elelabs, HUSBZB-1, Telegesis) | +| `deconz` | dresden elektronik deCONZ protocol (e.g., ConBee I/II, RaspBee I/II) | +| `znp` | Texas Instruments new (active): Z-Stack 3.x.x ZNP protocol (e.g., CC26x2, CC13x2) | +| `ti_cc` | Texas Instruments legacy & HA12: Z-Stack Home 1.2.x ZNP protocol (e.g., CC253x) | +| `zigate` | ZiGate Serial protocol (e.g., ZiGate USB-TTL, PiZiGate, ZiGate WiFi) | +| `xbee` | Digi XBee ZB Coordinator Firmware protocol (e.g., Digi XBee Series 2, 2C, 3) | - Submit From 0ea561ae9d673ff83c7f0a13b5a5dd6467a2df6d Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Mon, 7 Sep 2020 16:36:49 +0200 Subject: [PATCH 11/14] Support 'for' without setting the 'to'-state in automation state trigger (#14423) --- source/_docs/automation/trigger.markdown | 44 ++++++++++++++++++++++-- 1 file changed, 41 insertions(+), 3 deletions(-) diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown index 5658838c4e9..7c68d27bf30 100644 --- a/source/_docs/automation/trigger.markdown +++ b/source/_docs/automation/trigger.markdown @@ -158,6 +158,9 @@ automation: You can use `for` to have the state trigger only fire if the state holds for some time. +This example fires, when the entity state changed to `"on"` and holds that +state for 30 seconds: + ```yaml automation: trigger: @@ -168,14 +171,49 @@ automation: for: "00:00:30" ``` +You can also fire the trigger when the state value changed from a specific +state, but hasn't returned to that state value for the specified time. + +This can be useful, e.g., checking if a media player hasn't turned "off" for +the time specified, but doesn't care about "playing" or "paused". + ```yaml automation: trigger: platform: state entity_id: media_player.kitchen - # Not "playing" for 30 seconds - from: "playing" - for: "00:00:30" + # Not "off" for 30 minutes + from: "off" + for: "00:30:00" +``` + +Please note, that when using `from`, `to` and `for`, only the value of the +`to` option is considered for the time specified. + +In this example, the trigger fires if the state value of the entity remains the +same for `for` the time specified, regardless of the current state value. + +```yaml +automation: + trigger: + platform: state + entity_id: media_player.kitchen + # The media player remained in its current state for 1 hour + for: "01:00:00" +``` + +When the `attribute` option is specified, all of the above works, but only +applies to the specific state value of that attribute. + +For example, this trigger only fires if the boiler was heating for 10 minutes: + +```yaml +automation: + trigger: + platform: state + entity_id: climate.living_room + attribute: hvac_action + state: "heating" ``` You can also use templates in the `for` option. From ea17be1af8539ffd1fb7fed5bd4361af9f8b68d3 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Mon, 7 Sep 2020 18:23:44 +0200 Subject: [PATCH 12/14] Fix ha_release in KNX weather platform (#14425) --- source/_integrations/weather.knx.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/weather.knx.markdown b/source/_integrations/weather.knx.markdown index fc4a03a1679..c6f6d35ddf7 100644 --- a/source/_integrations/weather.knx.markdown +++ b/source/_integrations/weather.knx.markdown @@ -3,7 +3,7 @@ title: "KNX Weather" description: "Instructions on how to integrate KNX weather stations with Home Assistant." ha_category: - Weather -ha_release: 0.115.0 +ha_release: 0.115 ha_iot_class: Local Push ha_domain: knx --- From 1f408c36f0c547dc5407b8480da3ede678b7fe57 Mon Sep 17 00:00:00 2001 From: Bas Nijholt Date: Mon, 7 Sep 2020 19:24:43 +0200 Subject: [PATCH 13/14] add MENU as button option to webos.button service (#14420) --- source/_integrations/webostv.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/webostv.markdown b/source/_integrations/webostv.markdown index d79981272c3..c01d64f4e71 100644 --- a/source/_integrations/webostv.markdown +++ b/source/_integrations/webostv.markdown @@ -184,7 +184,7 @@ Available services: `button`, `command` | Service data attribute | Optional | Description | | ---------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `entity_id` | no | Target a specific webostv media player. | -| `button` | no | Name of the button. Known possible values are `LEFT`, `RIGHT`, `DOWN`, `UP`, `HOME`, `BACK`, `ENTER`, `DASH`, `INFO`, `ASTERISK`, `CC`, `EXIT`, `MUTE`, `RED`, `GREEN`, `BLUE`, `VOLUMEUP`, `VOLUMEDOWN`, `CHANNELUP`, `CHANNELDOWN`, `0`, `1`, `2`, `3`, `4`, `5`, `6`, `7`, `8`, `9` | +| `button` | no | Name of the button. Known possible values are `LEFT`, `RIGHT`, `DOWN`, `UP`, `HOME`, `MENU`, `BACK`, `ENTER`, `DASH`, `INFO`, `ASTERISK`, `CC`, `EXIT`, `MUTE`, `RED`, `GREEN`, `BLUE`, `VOLUMEUP`, `VOLUMEDOWN`, `CHANNELUP`, `CHANNELDOWN`, `0`, `1`, `2`, `3`, `4`, `5`, `6`, `7`, `8`, `9` | ### Service `webostv.command` From 6e962dc4b9dbf4407c8e3d827038393d0d5f162d Mon Sep 17 00:00:00 2001 From: Johnny Walker Date: Mon, 7 Sep 2020 16:04:12 -0400 Subject: [PATCH 14/14] Clarify preload stream option (#14426) While initially looking at the docs for this, it was not clear what option this paragraph was referencing. This makes it a little more clear what the option is and what it does. --- source/_integrations/camera.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/camera.markdown b/source/_integrations/camera.markdown index c60d11ec573..50530d7e4cd 100644 --- a/source/_integrations/camera.markdown +++ b/source/_integrations/camera.markdown @@ -14,7 +14,7 @@ The camera integration allows you to use IP cameras with Home Assistant. If your camera supports it, and the [`stream`](/integrations/stream) integration is setup, you will be able to stream your cameras in the frontend and on supported media players. -This option will keep the stream alive, and preload the feed on Home Assistant startup. This will result in reduced latency when opening the stream in the frontend, as well as when using the `play_stream` service or Google Assistant integration. It does, however, utilize more resources on your machine, so it is recommended to check CPU usage if you plan to use this feature. +The `Preload stream` option will start the camera feed on Home Assistant startup and continue to keep the stream alive. This will result in reduced latency when opening the stream in the frontend, as well as when using the `play_stream` service or Google Assistant integration. It does, however, utilize more resources on your machine, so it is recommended to check CPU usage if you plan to use this feature.

Screenshot showing Preload Stream option in Home Assistant front end.