4.8.0-beta.3
Pre-releaseWhat's new
Jinja templating, rendered server-side by Home Assistant and updated live whenever the entities a template references change. Any supported option containing {{ }} is treated as a template: name, icon, icon_color, secondary_info text, hide_if (string form or hide_if.template), and the new template: option that replaces the displayed value entirely. Each template gets an entity variable holding the owning entity's id.
- type: custom:multiple-entity-row
entity: sensor.next_ferry
name: "Next ferry {{ state_attr(entity, 'time') }}"
hide_if: "{{ is_state('binary_sensor.ferry_service', 'off') }}"
entities:
- entity: sensor.travel_time
template: "{{ states(entity) | round(0) }} min"Full documentation: docs/templating.md. Notes: a template: result is shown verbatim — do rounding in the template, format: is ignored. hide_if templates hide on true/yes/on/1. Templated rows open directly in the code editor.
Fixed since beta.2
- Custom
width/justify-contentstyling of.entities-rowhad no effect since 4.7.0 (#411) - Clicking the name or header of a
toggle: trueentity did nothing since 4.7.0 (#415)
Added since beta.2
wrap: truereflows entities onto multiple lines instead of overflowing the card on narrow screens (#411)
Heads-up for upgraders: the #411 fix restores the pre-4.7.0 DOM, which also drops HA's .text-content/.state wrapper styling (text-align: right, direction: ltr). If you added CSS to compensate during 4.7.x, you may want to revisit it.
Earlier in this beta cycle
unit:overrides ignored on state values of integrations with translated units, e.g. Analytics Insights (#413)
Addresses #409, #35, #249, #278, #247, #254, #269, #270 — these close with the 4.8.0 final release.
Full Changelog: v4.7.1...v4.8.0-beta.3