configuration.yaml file:
(string)(Optional)Name to use in the frontend.
(string | list)(Optional)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.
-(device_class)(Optional)The type/class of the sensor to set the icon in the frontend.
@@ -176,22 +172,16 @@ original switch can then be hidden by value_template: "{{ is_state('switch.door', 'on') }}" -entity_idThis example combines multiple CO sensors into a single overall
status. When using templates with binary sensors, you need to return
-true or false explicitly. entity_id is used to limit which
-sensors are being monitored to update the state, making computing this
-sensor far more efficient.
true or false explicitly.
binary_sensor:
- platform: template
sensors:
co:
friendly_name: "CO"
device_class: gas
- entity_id:
- - sensor.bedroom_co_status
- - sensor.kitchen_co_status
- - sensor.wardrobe_co_status
value_template: >-
{{ is_state('sensor.bedroom_co_status', 'Ok')
and is_state('sensor.kitchen_co_status', 'Ok')
@@ -226,14 +216,6 @@ device tracking and Z-Wave multisensor presence sensors.
- platform: template
sensors:
people_home:
- entity_id:
- - device_tracker.sean
- - device_tracker.susan
- - binary_sensor.office_124
- - binary_sensor.hallway_134
- - binary_sensor.living_room_139
- - binary_sensor.porch_ms6_1_129
- - binary_sensor.family_room_144
value_template: >-
{{ is_state('device_tracker.sean', 'home')
or is_state('device_tracker.susan', 'home')
diff --git a/components/cover.template/index.html b/components/cover.template/index.html
index 8b75c3b787..a01bdb293b 100644
--- a/components/cover.template/index.html
+++ b/components/cover.template/index.html
@@ -107,10 +107,6 @@ stop, position, and tilt commands of a cover.
(string)(Optional)Name to use in the frontend.
- entity_id
-
- (string | list)(Optional)Add a list of entity IDs so the switch only reacts to state changes of these entities. This will reduce the number of times the cover will try to update its state.
-
value_template
(template)(Exclusive)Defines a template to get the state of the cover. Valid values are open/true or closed/false. value_template and position_template cannot be specified concurrently.
@@ -247,9 +243,6 @@ sensor into a cover.
{% else %}
mdi:window-closed
{% endif %}
- entity_id:
- - cover.bedroom
- - cover.livingroom
sensor:
- platform: template
@@ -263,9 +256,6 @@ sensor into a cover.
{% else %}
closed
{% endif %}
- entity_id:
- - cover.bedroom
- - cover.livingroom
script:
cover_group:
diff --git a/components/light.template/index.html b/components/light.template/index.html
index 0ef32fc99b..d226a6cd99 100644
--- a/components/light.template/index.html
+++ b/components/light.template/index.html
@@ -110,10 +110,6 @@ brightness commands of a light.
(string)(Optional)Name to use in the frontend.
- entity_id
-
- (string | list)(Optional)Add a list of entity IDs so the switch only reacts to state changes of these entities. This will reduce the number of times the light will try to update its state.
-
value_template
(template)(Optional)Defines a template to get the state of the light.
diff --git a/components/sensor.template/index.html b/components/sensor.template/index.html
index 33125fad2a..596883fcbd 100644
--- a/components/sensor.template/index.html
+++ b/components/sensor.template/index.html
@@ -105,10 +105,6 @@ from other entities.
(string)(Optional)Name to use in the frontend.
- entity_id
-
- (string | list)(Optional)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.
-
unit_of_measurement
(string)(Optional)Defines the units of measurement of the sensor, if any.
@@ -127,12 +123,11 @@ from other entities.
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
{{ states.switch.source.state == 'on' }}
-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:
{{ is_state('switch.source', 'on') }}
hidden
(string)(Optional)Name to use in the frontend.
(string | list)(Optional)Add a list of entity IDs so the switch only reacts to state changes of these entities. This will reduce the number of times the switch will try to update its state.
-(template)(Required)Defines a template to set the state of the switch.
diff --git a/sitemap.xml b/sitemap.xml index aeefb9d5c2..dd4fdb6620 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -3826,7 +3826,7 @@