Entity Card Pro
custom:entity-card-pro shows one entity as a tile: icon, name and value in one row of the sections grid, or with a gauge, bar or graph below. The entity keys sit directly on the card; the entity options explain every one of them. This page builds a tile up option by option.
Basic
Two lines. The tile takes the entity's icon, friendly name and formatted state, and colours the icon like Home Assistant does (lights amber when on, people green at home, plain sensors in the primary colour).
Name and value
name replaces the friendly name, decimals rounds the value, unit overrides the unit, prefix and suffix wrap the value in text.
Rules
rules pick colour, icon and label by value (below / above) or by state. The first rule that matches wins. The label sits next to the value.
State rules work the same way for anything that is not a number.
Controls
control: auto adds the control the entity's domain calls for: a light gets a switch and a brightness slider, a cover its buttons and a position slider, a thermostat a stepper. control: toggle and the other names pick one; see Controls. grid_options here sizes the tiles to half a section, see Sizing in sections.
Visuals
visual changes how the value is drawn: the default icon, a ring around the icon, a badge pill, or a gauge, bar, sparkline, columns or strip block below the row. min and max set the range for ring, gauge and bar.
All eight side by side. The history visuals (sparkline, columns, strip) read the recorder history for the card's hours_to_show, in buckets of bucket_minutes for columns and strip.
Each visual, the options it reads and the layouts it is drawn in are explained one by one under Visuals on the entity options page, including the history window that hours_to_show and bucket_minutes set for the sparkline, columns and strip.
Card tint
tint_card: true on a rule washes the whole card in that rule's colour while it matches. Use it for the states that deserve attention, not for the normal case. See Rules for the details.
Attribute
attribute shows an attribute instead of the state; unit, decimals and min / max apply to it like to a state. On a thermostat, attribute: hvac_mode shows the HVAC mode, which Home Assistant keeps in the state rather than in an attribute.
Text and templates
value replaces the state with plain text or a Jinja template. Without an entity the tile is a plain text or template card: give it a name, icon and color; there is nothing to open on tap.
Actions
A tile is a button. tap_action runs a scene, opens a dashboard or a URL, or toggles; hold_action and double_tap_action add two more. See Actions for every field.
More examples
One card type, many tiles. Rules colour a battery ring, an attribute drives a bar, a person becomes a badge, and prefix and suffix turn a number into a sentence.
Templates everywhere
name, icon, color, secondary and value all take templates. This tile compares two sensors and changes its whole look with the result.
Counting with templates
A template value that looks like a number gets rules, decimals and a unit like a state. Here the tile counts open windows and lights.
Reference
All entity options plus:
| Option | Default | Description |
|---|---|---|
toggle | false | Switch on the right that calls homeassistant.toggle. |
secondary | Line under the name instead of the value and label. Template allowed. | |
hours_to_show | 24 | History window for sparkline, columns and strip, at least 1. |
bucket_minutes | 60 | Bucket size for columns and strip, at least 5. |
tap_action / hold_action / double_tap_action | more-info / more-info / none | See Actions. |
Grid defaults
6 columns × 1 row; rows: auto for the block visuals (gauge, bar, sparkline, columns, strip). See Sizing in sections.
Home Assistant options
Like every card, this one also accepts grid_options, visibility, layout_options, view_layout and card_mod. They are passed through to Home Assistant; see Sizing in sections for grid_options.