State-based and trigger-based template entities have the special template variable this available in their templates and actions. # Define trigger-based template entities - trigger. # Example configuration.yaml entry with two sections template : # Define state-based template entities - sensor. The state of other trigger-based template entities is not restored. The state, including attributes, of trigger-based sensors and binary sensors is restored when Home Assistant is restarted. This functionality can be added back by defining a state trigger for each entity that you want to trigger updates.
#SAVE TEMPLATE CONTROLLER EDITOR UPDATE#
Trigger-based entities do not automatically update when states referenced in the templates change.
Whenever the trigger fires, all related entities will re-render and it will have access to the trigger data in the templates. This feature is a great way to create entities based on webhook data ( example), or update entities based on a schedule. Triggers follow the same format and work exactly the same as triggers in automations. If you want more control over when an entity updates, you can define a trigger. Template : - sensor : - name : " Average temperature" unit_of_measurement : " ☌" state : > Trigger-based template binary sensors, buttons, numbers, selects and sensors Home Assistant will update your template sensor as soon as either source sensor updates. Template entities will by default update as soon as any of the referenced data in the template updates.įor example, you can have a template that takes the averages of two sensors. State-based template binary sensors, buttons, numbers, selects and sensors Each block defines sensor/binary sensor/number/select entities and can contain an optional update trigger.įor old sensor/binary sensor configuration format, see below. You can define multiple configuration blocks as a list. Sensor, binary sensor, button, number and select template entities are defined in your YAML configuration files, directly under the template: key and cannot be configured via the UI. For other types, please see the specific pages: Sensors, binary (on/off) sensors, buttons, numbers and selects are covered on this page.
This is done by specifying templates for properties of an entity, like the name or the state. The template integration allows creating entities which derive their values from other data.
0 kommentar(er)
