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 07:17:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

Wording tweak (#7148)

Browse Source 
* Wording tweak

Based upon feedback after the breaking change, re-wording the description of the `entity_id` line to hopefully be clearer.

* Added example about entity_id

Added a note about the template at the end not updating automatically, and an example about using the entity id
This commit is contained in:
DubhAd 2018-10-28 11:09:36 +00:00 committed by Fabian Affolter
parent 71d532ef1f
commit 3dc0126c31
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -55,7 +55,7 @@ sensor:
required: false
type: template
entity_id:
description: A list of entity IDs so the sensor only reacts to state changes of these entities. This can be used if the automatic analysis fails to find all relevant entities.
description: The template engine will attempt to work out what entities should trigger an update of the sensor. If this fails to get the correct list (for example if your template loops over the contents of a group) then you can provide a list of entity IDs that will cause the sensor to update.
required: false
type: string, list
unit_of_measurement:
@ -292,7 +292,7 @@ sensor:
### {% 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).
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`.
{% raw %}
```yaml
@ -301,6 +301,7 @@ sensor:
sensors:
nonsmoker:
value_template: '{{ (( as_timestamp(now()) - as_timestamp(strptime("06.07.2018", "%d.%m.%Y")) ) / 86400 ) | round(2) }}'
entity_id: sun.sun
friendly_name: 'Not smoking'
unit_of_measurement: "Days"
```