4.10.0-alpha.1
Pre-releaseWhat's new
Template variables. vars names values reusable across a scope's templates. Additional entities inherit the row's and may shadow them, and a variable can build on one declared before it. Values may themselves be templates.
- type: custom:multiple-entity-row
entity: switch.nas_plex
vars:
host: "{{ state_attr(entity, 'host') }}"
display_name: "{{ state_attr(entity, 'display_name') }}"
name: "{{ display_name }} on {{ host }}"
entities:
- vars:
service_action: restart
icon: mdi:restart
tap_action:
action: perform-action
perform_action: button.press
confirmation:
text: "{{ service_action | capitalize }} {{ display_name }} on {{ host }}?"
target:
entity_id: "{{ 'button.' ~ [host, service_action] | join('_') | slugify }}"Templates in actions. Every value inside tap_action, hold_action and double_tap_action is now templatable at any depth — service data, target, navigation_path, confirmation.text. Results keep their native type, and are resolved when the action fires, so a service call carries current values.
Variables are inlined into each template that uses them, so a field is still a single subscription. Full documentation: docs/templating.md.
Entity-less entries. An additional entity no longer needs entity, attribute or icon. An entry with none of them — even - {} — shows the main entity's state, which is the only way to repeat it when the id isn't known in advance, as under custom:auto-entities.
Changed
An entity id that doesn't resolve is now marked with a warning icon instead of silently disappearing from the row. If you have a renamed or removed entity in a row, you'll now see it. hide_unavailable: true hides it as before, and default: still takes precedence.
Fixed
- Icons and toggles no longer reserve a header line when their name is hidden, so rows mixing named values with icon-only entities go back to their pre-4.8 height (#425)
Addresses #422, #425, #340, #364 — these close with the 4.10.0 final release.
Full Changelog: v4.9.0...v4.10.0-alpha.1