From 78d2b4bcac61cea2c3b1269945ad60285a243f4d Mon Sep 17 00:00:00 2001 From: Matheson Steplock Date: Mon, 1 Jun 2020 10:18:16 -0400 Subject: [PATCH 1/4] Remove alert detail from Environment Canada docs (#13612) --- source/_integrations/environment_canada.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/environment_canada.markdown b/source/_integrations/environment_canada.markdown index a7b949a7d3b..1029462f51c 100644 --- a/source/_integrations/environment_canada.markdown +++ b/source/_integrations/environment_canada.markdown @@ -159,7 +159,7 @@ weather_alert_tts: sequence: - service: tts.amazon_polly_say data_template: - message: "{{ states('sensor.warnings') }} in effect. {{ state_attr('sensor.warnings', 'alert detail') }}" + message: "{{ states('sensor.warnings') }} in effect." ``` {% endraw %} From fc1d2291f31fc3e0e9dbfd70eea82df5a7c1d486 Mon Sep 17 00:00:00 2001 From: tucoti <64128492+tucoti@users.noreply.github.com> Date: Tue, 2 Jun 2020 04:52:26 +1000 Subject: [PATCH 2/4] Updated vacuum.xiaomi_miio.markdown to warn of access token method (#13128) Co-authored-by: Franck Nijhof --- source/_integrations/vacuum.xiaomi_miio.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_integrations/vacuum.xiaomi_miio.markdown b/source/_integrations/vacuum.xiaomi_miio.markdown index 257e5b4ef32..8d625c8418d 100644 --- a/source/_integrations/vacuum.xiaomi_miio.markdown +++ b/source/_integrations/vacuum.xiaomi_miio.markdown @@ -228,6 +228,8 @@ The following table shows the units of measurement for each attribute: 8. You should now see 2 extra options listed in English, this means you enabled developer mode. [if not, try all steps again!]. 9. Under "Hub info" there is quite some text in JSON format, this includes the "token" that you need. +Note: If you have multiple devices needing a token, e.g., Xiaomi Mi Robot Vacuum and a Xiaomi IR Remote, the above method may not work. The Xiaomi Home app will display a token, though it isn't the correct one. The alternative method using "Mi Home v5.4.49" will provide the correct token. + ### Alternative methods
From aefc4429d856d0e33a85557eef6410b4aa85cb5d Mon Sep 17 00:00:00 2001 From: Artur 'Wodor' Wielogorski Date: Mon, 1 Jun 2020 19:54:29 +0100 Subject: [PATCH 3/4] Add unique_id to the example of mqtt switch (#13295) I was surprised that I cannot define the Id of the created switch, it is difficult to use it in automation without an id. It turns out that there is `unique_id` parameter, so why not show it to the world? --- source/_integrations/switch.mqtt.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/switch.mqtt.markdown b/source/_integrations/switch.mqtt.markdown index 179a946baac..7b3ca3be0b9 100644 --- a/source/_integrations/switch.mqtt.markdown +++ b/source/_integrations/switch.mqtt.markdown @@ -159,6 +159,7 @@ The example below shows a full configuration for a switch. # Example configuration.yaml entry switch: - platform: mqtt + unique_id: bedroom_switch name: "Bedroom Switch" state_topic: "home/bedroom/switch1" command_topic: "home/bedroom/switch1/set" From 681549e282de7147a3b080b974bc153b1a3bd92c Mon Sep 17 00:00:00 2001 From: Max <870074+max-te@users.noreply.github.com> Date: Mon, 1 Jun 2020 21:00:34 +0200 Subject: [PATCH 4/4] Add a bit on device triggers in /automation/trigger (#13289) Co-authored-by: Franck Nijhof --- source/_docs/automation/trigger.markdown | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown index be745deb41a..567c34ac4d5 100644 --- a/source/_docs/automation/trigger.markdown +++ b/source/_docs/automation/trigger.markdown @@ -389,6 +389,15 @@ automation: event: enter # or "leave" ``` +### Device triggers + +Device triggers encompass a set of events that are defined by an integration. This includes, for example, state changes of sensors as well as button events from remotes. +[MQTT device triggers](/integrations/device_trigger.mqtt/) are set up through autodiscovery. + +In contrast to state triggers, device triggers are tied to a device and not necessarily an entity. +To use a device trigger, set up an automation through the browser frontend. +If you would like to use a device trigger for an automation that is not managed through the browser frontend, you can copy the YAML from the trigger widget in the frontend and paste it into your automation's trigger list. + ### Multiple triggers It is possible to specify multiple triggers for the same rule. To do so just prefix the first line of each trigger with a dash (-) and indent the next lines accordingly. Whenever one of the triggers fires, [processing](#what-are-triggers) of your automation rule begins.