The template platform supports sensors which breaks out the state and state_attributes from other entities.
To enable Template sensors in your installation, add the following to your configuration.yaml file:
To enable Template binary sensors in your installation, add the following to your configuration.yaml file:
# Example configuration.yaml entry @@ -131,10 +131,10 @@sensor: platform: template sensors: - furnace_on: - value_template: {{ states.sensor.furnace.state > 2.5 }} - friendly_name: 'Furnace Running - sensor_class: heat + furnace_on: + value_template: {{ states.sensor.furnace.state > 2.5 }} + friendly_name: 'Furnace Running + sensor_class: heat
The given file_path must be an existing file because the camera platform setup make a writeable check on it.
-Ensure that the Home Assistant user is in the video group.
-eg.
-
- sudo usermod -a -G video hass
-
The given file_path must be an existing file because the camera platform setup make a writeable check on it.
+ +Ensure that the user who is running Home Assistant is in the video group. Eg. for the user hass:
$ sudo usermod -a -G video hass +
By comparing the details published on the template page the same can be archived with a different approach:
+ +value_template: "{%if states.sensor.ENTITY_ID.state == 'on' %}running{%elif states.switch.ENTITY_ID.state == 'off' %}not running{% endif %}" +
The Binary template sensor is the one in similar cases if you prefer to see an icon instead of text.
+This example shows a multiple line template with and if test. It looks at a sensing switch and shows on/off in the frontend. It disables warnings to avoid log messages where the switch it depends on isn’t loaded yet.
diff --git a/sitemap.xml b/sitemap.xml index 7995f1753d..21052b8fd7 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -1914,34 +1914,34 @@