From 6f53634937b1e7f7d756a15c00953d7d7072767b Mon Sep 17 00:00:00 2001 From: Martijn van der Pol Date: Fri, 21 Jul 2023 10:47:36 +0200 Subject: [PATCH] Update templating.markdown (#28269) --- source/_docs/configuration/templating.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_docs/configuration/templating.markdown b/source/_docs/configuration/templating.markdown index be3160ad3e0..164ab62b26c 100644 --- a/source/_docs/configuration/templating.markdown +++ b/source/_docs/configuration/templating.markdown @@ -110,8 +110,8 @@ Templates for some [triggers](/docs/automation/trigger/) as well as `trigger_var Not supported in [limited templates](#limited-templates). -- Iterating `states` will yield each state sorted alphabetically by entity ID. -- Iterating `states.domain` will yield each state of that domain sorted alphabetically by entity ID. +- Iterating `states` will yield each state object. +- Iterating `states.domain` will yield each state object of that domain. - `states.sensor.temperature` returns the state object for `sensor.temperature` (avoid when possible, see note below). - `states` can also be used as a function, `states(entity_id, rounded=False, with_unit=False)`, which returns the state string (not the state object) of the given entity, `unknown` if it doesn't exist, and `unavailable` if the object exists but is not available. - The optional arguments `rounded` and `with_unit` control the formatting of sensor state strings, please see the [examples](#formatting-sensor-states) below.