From 19e7f6340e0d2c9ab9f2020ec1c8c21e96e0bbfd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=B6ren=20Beye?= Date: Sat, 19 Feb 2022 13:07:07 +0100 Subject: [PATCH] Improve glossary entry of automations (#21695) Co-authored-by: Franck Nijhof --- source/_data/glossary.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_data/glossary.yml b/source/_data/glossary.yml index e27bb5ab748..ffdd7f28fc6 100644 --- a/source/_data/glossary.yml +++ b/source/_data/glossary.yml @@ -3,7 +3,7 @@ - topic: Add-on description: "Add-ons provide additional, standalone, applications that can run beside Home Assistant. Most of these, add-on provided, applications can be integrated into Home Assistant using integrations. Examples of add-ons are: an MQTT broker, database service or a file server." - topic: Automation - description: "[Automations](/docs/automation/) offer the capability to call a service based on a simple or complex trigger. Automation allows a condition such as a sunset to cause an event, such as a light turning on." + description: "[Automations](/docs/automation/) connect one or more triggers to one or more actions in a 'when trigger then do action' fashion with additional optional conditions. For example, an automation might connect the trigger 'sunset' to the action 'turn the lights on' but only if the condition 'someone is home' is met. Pre-made automations for common use-cases are available via [the blueprints feature](/docs/automation/using_blueprints/)." - topic: Binary sensor description: "A [binary sensor](/integrations/binary_sensor) returns information about things that only have two states - such as on or off." - topic: Component