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-19 15:26:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove some redundant information (#7221)

Browse Source 
* Remove some redundant information

* Use sensor.date in example instead, more even behavior
This commit is contained in:
Thomas Lovén 2018-10-29 13:27:36 +01:00 committed by Franck Nijhof
parent 39ab9079c4
commit 9cd4a5b4df
1 changed files with 3 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
source/_components/sensor.template.markdown
View File

@ -292,7 +292,7 @@ sensor:
### {% linkable_title Working with dates %} ### {% linkable_title Working with dates %}
The `template` sensors are not limited to use attributes from other entities but can also work with [Home Assistant's template extensions](/docs/configuration/templating/#home-assistant-template-extensions). This template contains no entities that will trigger an update, so either we need to use `homeassistant.update_entity` or add an `entity_id:` line for an entity that will force an update - here we're using `sun.sun`. The `template` sensors are not limited to use attributes from other entities but can also work with [Home Assistant's template extensions](/docs/configuration/templating/#home-assistant-template-extensions). This template contains no entities that will trigger an update, so either we need to use `homeassistant.update_entity` or add an `entity_id:` line for an entity that will force an update - here we're using `sensor.date`.
{% raw %} {% raw %}
```yaml ```yaml
@ -301,28 +301,13 @@ sensor:
sensors: sensors:
nonsmoker: nonsmoker:
value_template: '{{ (( as_timestamp(now()) - as_timestamp(strptime("06.07.2018", "%d.%m.%Y")) ) / 86400 ) | round(2) }}' value_template: '{{ (( as_timestamp(now()) - as_timestamp(strptime("06.07.2018", "%d.%m.%Y")) ) / 86400 ) | round(2) }}'
entity_id: sun.sun entity_id: sensor.date
friendly_name: 'Not smoking' friendly_name: 'Not smoking'
unit_of_measurement: "Days" unit_of_measurement: "Days"
``` ```
{% endraw %} {% endraw %}
### {% linkable_title Template tracking %} Useful entities to choose might be `sensor.date` which update once per day, or `sensor.time` which updates once per minute.
This example shows how to add `entity_id` to a template to allow tracking of updates. Fixing an error caused in (81.0)
{% raw %}
```yaml
sensor:
- platform: template
sensors:
nonsmoker:
entity_id: now.strptime
value_template: '{{ (( as_timestamp(now()) - as_timestamp(strptime("06.07.2018", "%d.%m.%Y")) ) / 86400 ) | round(2) }}'
friendly_name: 'Not smoking'
unit_of_measurement: "Days"
```
{% endraw %}
Note: If a template uses more than one sensor they can be listed Note: If a template uses more than one sensor they can be listed