From 17d7e09f84155c5832b999483163b0fc933cebee Mon Sep 17 00:00:00 2001 From: Dubh Ad Date: Sun, 1 Sep 2019 17:12:09 +0100 Subject: [PATCH] Fixing errors (#10267) There's a couple of examples where `.state` should be appended, but isn't --- 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 08789841c4a..59260edf7cf 100644 --- a/source/_docs/configuration/templating.markdown +++ b/source/_docs/configuration/templating.markdown @@ -61,7 +61,7 @@ Extensions allow templates to access all of the Home Assistant specific states a
- Avoid using `states.sensor.temperature`, instead use `states('sensor.temperature')`. It is strongly advised to use the `states()`, `is_state()`, `state_attr()` and `is_state_attr()` as much as possible, to avoid errors and error message when the entity isn't ready yet (e.g., during Home Assistant startup). + Avoid using `states.sensor.temperature.state`, instead use `states('sensor.temperature')`. It is strongly advised to use the `states()`, `is_state()`, `state_attr()` and `is_state_attr()` as much as possible, to avoid errors and error message when the entity isn't ready yet (e.g., during Home Assistant startup).
@@ -74,7 +74,7 @@ The next two statements result in the same value if the state exists. The second {% raw %} ```text {{ states('device_tracker.paulus') }} -{{ states.device_tracker.paulus }} +{{ states.device_tracker.paulus.state }} ``` {% endraw %}