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-28 19:57:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

Tweaks

Browse Source
This commit is contained in:
Franck Nijhof 2025-01-17 19:15:43 +01:00 committed by GitHub
parent e4894e1cc5
commit b1f373a5b1
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -354,13 +354,13 @@ The `state_translated` function returns a translated state of an entity using a
### Availability ### Availability
Both state- and trigger-based templates can have an availability template which suppress further rendering of other templates if the availability renders as `False`. Both state- and trigger-based templates can have an availability template that suppresses further rendering of other templates if the availability renders as `False`.
If the template either fails to render or returns True, "1", "true", "yes", "on", "enable", or a non-zero number, the entity will be available. For any other value, the entity will be `unavailable`. Note that the string comparison not case sensitive; `"TrUe"` and `"yEs"` are allowed. If the template either fails to render or returns True, "1", "true", "yes", "on", "enable", or a non-zero number, the entity will be available. For any other value, the entity will be `unavailable`. Note that the string comparison is not case-sensitive; `"TrUe"` and `"yEs"` are allowed.
It can be important to understand the implications of suppressing other state attributes when the entity goes `unavailable`. It can be important to understand the implications of suppressing other state attributes when the entity goes `unavailable`.
With example as below, if the entity has the icon `mdi:on` and the entity goes unavailable, the icon will remain `mdi:on` until the entity comes back as available. At which point, it will again render the icon according to it's template. For example, if the entity has the icon `mdi:on` and becomes unavailable, the icon will remain `mdi:on` until the entity becomes available. At that point, it will again render the icon according to its template.
#### Availability use example #### Availability use example