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] 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.