From b84809545e61cba9ea890b46a2c2c50f5617826d Mon Sep 17 00:00:00 2001 From: arsaboo Date: Wed, 13 Dec 2017 11:37:42 -0500 Subject: [PATCH] Removed entity_id --- source/_components/sensor.template.markdown | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/source/_components/sensor.template.markdown b/source/_components/sensor.template.markdown index c5d5aba6cee..34d255184a9 100644 --- a/source/_components/sensor.template.markdown +++ b/source/_components/sensor.template.markdown @@ -46,10 +46,6 @@ sensor: description: Name to use in the frontend. required: false type: string - entity_id: - description: Add a list of entity IDs so the sensor only reacts to state changes of these entities. This will reduce the number of times the sensor will try to update its state. - required: false - type: string, list unit_of_measurement: description: Defines the units of measurement of the sensor, if any. required: false @@ -71,12 +67,11 @@ sensor: ## {% linkable_title Considerations %} If you are using the state of a platform that takes extra time to load, the -Template Sensor may get an `unknown` state during startup. This results -in error messages in your log file until that platform has completed loading. -If you use `is_state()` function in your template, you can avoid this situation. +Template Sensor may get an `unknown` state during startup. To avoid this (and the resulting +error messages in your log file), you can use `is_state()` function in your template. For example, you would replace {% raw %}`{{ states.switch.source.state == 'on' }}`{% endraw %} -with this equivalent that returns `true`/`false` and never gives an unknown +with this equivalent that returns `true`/`false` and never gives an `unknown` result: {% raw %}`{{ is_state('switch.source', 'on') }}`{% endraw %}