jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-21 08:16:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fixing errors (#10267)

Browse Source 
There's a couple of examples where `.state` should be appended, but isn't
This commit is contained in:
Dubh Ad 2019-09-01 17:12:09 +01:00 committed by Klaas Schoute
parent f92d3cbe0b
commit 17d7e09f84
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
source/_docs/configuration/templating.markdown
View File

@ -61,7 +61,7 @@ Extensions allow templates to access all of the Home Assistant specific states a
<div class='note warning'>
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).
</div>
@ -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 %}