From 8afaf28036139f673cf0eb2d8f4ff1f1eec9e067 Mon Sep 17 00:00:00 2001 From: G Johansson Date: Fri, 15 Nov 2024 12:01:24 +0100 Subject: [PATCH] Update text on `this` in templates (#35757) --- source/_integrations/template.markdown | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/_integrations/template.markdown b/source/_integrations/template.markdown index bf61ce994b4..4d11c34ddcb 100644 --- a/source/_integrations/template.markdown +++ b/source/_integrations/template.markdown @@ -435,6 +435,7 @@ template: [trigger-doc]: /docs/automation/trigger #### Video tutorial + This video tutorial explains how to set up a Trigger based template that makes use of an action to retrieve the weather forecast (precipitation). @@ -444,7 +445,7 @@ This video tutorial explains how to set up a Trigger based template that makes u State-based and trigger-based template entities have the special template variable `this` available in their templates and actions. The `this` variable is the current [state object](/docs/configuration/state_object) of the entity and aids [self-referencing](#self-referencing) of an entity's state and attributes in templates and actions. Trigger-based entities also provide [the trigger data](/docs/automation/templating/). {% note %} -Self-referencing using `this` provides the current state for the entity. To access the new state, use the `value` variable. +Self-referencing using `this` provides the state and attributes for the entity before rendering the templates to calculate a new state. To access the new state, use the `value` or `value_json` variable. {% endnote %} ### Rate limiting updates