📝 Changelog¶
All notable changes to the Entity Progress Card are documented here, most recent
first. See docs/rc-testing.md for how to try a release
candidate safely before it becomes stable.
1.6.4¶
The colors Home Assistant would pick.
An entity's default color now comes from Home Assistant itself: the same state colors its own tiles use, from your theme, for every domain Home Assistant colors. Icons animate on the same rules Home Assistant applies, and tap to toggle like its tile card.
⚠️ Breaking Changes¶
text_shadow becomes text_effect¶
You can update right away — no extra action needed on your part.
text_shadow is replaced by text_effect:
text_shadow: true is read as text_effect: shadow, false is dropped.
Existing configs keep working as-is; the editor's Migrate config button
updates them whenever you like.
Duration sensors read in their own unit¶
A sensor whose value is a duration (a filter's hours left, an uptime) — by its
device class or by a time unit (h, min, s…) — is now read in its own unit:
min_value, max_value, watermark and
alert_when numbers follow it (max_value: 150 on a sensor in
hours means 150 h), no longer seconds. A config that gave them in seconds needs
them rewritten, or unit: s.
✨ New¶
bar_ring: place where the ring around the icon starts and leave part of it open, for a thermostat-like dial.
➡️ [Enhancement]: Ring position #144 (@addit248)text_effect:shadow,halo,outline,plateorcontrastkeeps the text readable over anoverlayorbackgroundbar.- Serbian, in Cyrillic and Latin: 41 languages.
➡️ feat: add Serbian translations (Cyrillic & Latin) #145 (@cpmarexel2f) bar_effectwaveturns a bar filling upward into water: a moving wave on top, bubbles rising through it.
🧩 Arrange the texts and the bar with content_order¶
content_orderplaces the name, its extra info, the value, the secondary info, the state content and the bar line by line, inhorizontalandverticallayouts, on asingle_linerow and on the rows of a Multi-Card or Multi-Feature; the editor builds it with one chip field per line.hidetakesname_info,infoandstate_contentto hide one text alone; removing acontent_orderchip in the editor writes it.
🧩 Single column, and Multi-Card in columns¶
density: single_columnstacks the icon, the texts and an upright bar in one column, the vertical twin ofsingle_line.layout: verticalturns a Multi-Card's rows into columns side by side, the bar standing under the texts or, withbar_position: overlay, behind them.
🩺 More from the console¶
EPB.doctor.jinja(2)shows a card's Jinja fields with Home Assistant's last result or error;EPB.doctor.history(2)the samples behind its trend indicator and peak marker.EPB.doctor.copy(2)gives the editor's issue report for any card on the page.EPB.debug('card')keeps debug logging on in this browser across reloads;EPB.debug(false)turns it off.EPB.doctor.dump()names the resources of a duplicate load, and gives a fingerprint of the files you run to compare with the release's.
🔧 Improvements¶
- Toggle mechanism: the default
icon_tap_actionnow aligns with the tile card's behavior. bar_orientation: up(ordown) stands the bar upright beside the texts of averticalcard; a value already set there, ignored until now, takes effect.-
Texts side by side are
·apart: the name andname_info,custom_infoand the value. -
bar_orientation: downfills a vertical bar from the top, the mirror ofup.
➡️ [Enhancement]: Ring position #144 (@addit248)
Around the icon, turn the ring and center it on zero¶
bar_orientationtakesclockwiseorcounterclockwisefor the ring;ltrandrtlread as the same, and the editor follows whenbar_positionchanges.
➡️ [Enhancement]: Ring position #144 (@addit248)center_zeroworks on the ring: zero sits at its middle and the value grows each way from it, marked by a line, and themes andbar_color_modefollow both arms.
➡️ [Enhancement]: Ring position #144 (@addit248)bar_segmentscuts the ring into blocks (that many per arm withcenter_zero).
➡️ [Enhancement]: Ring position #144 (@addit248)bar_effectglass,gradientandgradient_reversework on the ring.
➡️ [Enhancement]: Ring position #144 (@addit248)bar_ringsoftnesssets the blend of the ring's inner edge, in px (0for a crisp edge);--epb-ring-softnesssets it for a whole theme.
➡️ [Feature]: Make the ring mask gradient width configurable #148 (@addit248)
Unavailable entities and failed Jinja, handled alike¶
- When the card's entity, a
min_valueor amax_valueis unavailable, or its Jinja template fails, the bar stops and the line names the cause. - An unavailable
watermarkoralert_whenentity only drops its own mark or threshold.
Default colors follow your Home Assistant theme¶
- Every domain Home Assistant colors now gets its color here too: locks, media players, vacuums, binary sensors, alarm panels, weather and more.
-
A light takes your theme's light color instead of a fixed orange; a cover counts as active as soon as it is open; a climate in
autogets its color. -
input_numberreads its ownminandmax, likenumber. icon_animationfollows Home Assistant's idea of an active state per domain: a media player no longer animates while idle or paused, a lawn mower animates while mowing.alert_whenabove/belowfed by a timer, counter or number entity now use its value; they used to be ignored.- The editor's debug button adds the range the bar is drawn from (min, max, value, %) under the card's YAML.
- A
lightthat reports a color (rgb_color) takes that color, like the tile does (lifted when too pale), instead of the amber state color. uniton a duration sensor converts it:d,h,min,sormsshow the value in that unit, and the bounds are read in it.peak_markerandtrend_indicatorwindows work on duration sensors too.density: compactacceptsbar_position: icon: the ring around the icon, the icon alone oncelayout: vertical.- Tile Feature:
min_value,max_valueandwatermarktake a Jinja template, like the Card.
🐛 Fixes¶
min_valueandmax_valuehint the range the bar uses in the editor: the entity's own (input_number,number,counter), else the card's default, instead of always 0 and 100.- A
binary_sensorwithdevice_class: lightno longer takes the color of a lit bulb. value_compactshows0on a value with no unit (or a hidden one) instead of failing to display it.- An unavailable
min_valueentity or a failed Jinja range no longer draws a wrong bar silently;alert_whenand a Jinjawatermarkno longer react to a 0 that is not a value. bar_position: backgroundwithbar_orientation: up: thecenter_zeroline,watermarkandpeak_markermarks and therainbow_fullmarker lie across the bar again instead of along it.
➡️ [Bug]: Center zero line is not rotated when bar_orientation is up #146 (@tomlevels)center_zerowith a percentage theme (critical_when_low,battery_adaptive, …): the positive arm shows the whole theme instead of its upper half, and the negative arm takes the first zone's color. Themes in raw units (temperature) are unchanged.hide: progress_barhides the ring ofbar_position: icontoo; the editor drops the ring options with it.bar_position: iconon aframelessor translucent card: the track past the value no longer shows the bar color through it.
➡️ [Bug]: Frameless affects segment dividers & gap #149 (@addit248)bar_position: iconwithmarginless: the ring is no longer cut at the card's edge.bar_position: backgroundwithbar_orientationupordown: thebar_effectgradients, glass and shimmer run along the bar instead of across it.custom_themewith one zone inside another: a value past the inner zone takes the outer zone's color, as documented.alert_whenhighlight: labelno longer draws its label under thetrend_indicatoricon while the alert is active.density: single_linewithbar_size: xlargekeeps the bar on the row, drawnlarge, instead of moving it below the text.
📚 Documentation¶
- The documentation has its own site, searchable, with light and dark themes: https://francois-le-ko4la.github.io/lovelace-entity-progress-card/; the card picker's documentation link opens it.
- README: badges for the documentation site and the development documentation.
- Cookbook: a Mushroom Template card hosting a Multi-Feature (printer ink levels).
- Docs images follow your theme: every cookbook, theme and README screenshot and animation has a light and a dark version, with transparent corners.
- Demo dashboard: a Mushroom Template card hosting the Feature.
- Cookbook: a
bar_ringrecipe (dial, segments, edge softness). - Cookbook: a
bar_effect: wavecapture. - Installing, testing an RC and rolling back with the Home Assistant Marketplace (2026.11+), next to HACS.
- New logo, in the README and on the documentation site.
- A clearer README: what the card is up front, a color example, help right after the guides, install steps that work on a tablet.
- Troubleshooting shows each message the card can display, what it means and what to do.
- The deprecated options table lists every migrated option,
text_shadowincluded. - Multi-Card / Multi-Feature: a row is a standard card, with a visual editor.
- Configuration: find an option from what you want to see, how to paste an example, and every option checked against the code.
- Theme Guide: the predefined themes side by side, custom themes, color names and CSS variables, with screenshots.
- Cookbook, Contributing and RC testing: shorter paths to the common tasks.
🧹 Under the hood¶
- The editor rebuilds its option labels only when the language changes.
- The issue report is built by the card itself, so the console can make it too.
scripts/screenshots/captures the docs' images and animations (cards, whole view, APNG) from the demo dashboard.
We care about getting the details right — but even so, something here might have slipped through. You don't need to be a developer to notice it. If something feels off, that's reason enough. Open a GitHub issue. Or say hi on Discord. We'd rather know than have you go looking for a workaround on your own.
➡️ Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.6.3...1.6.4
1.6.3¶
Richer on screen. Quieter underneath.
The transformation that began with 1.6.0 goes deeper. Every card does only the work that matters, in a fraction of the time, and ships lighter — built for the oldest wall tablet as much as the newest phone. More of it is tested automatically, on every change. Then comes the rest: a ring around the icon, bars that line up across cards, a Multi card where every row is a real card, an editor that speaks Home Assistant's own language, and a long run of refinements and fixes.
A couple of Multi options changed name along the way, fully backward-compatible, and a Multi row that never said what to show now shows more — see Breaking Changes below.
⚠️ Breaking Changes¶
🧹 Multi rows: two options renamed, more shown by default¶
You can update right away — no extra action needed on your part. A Multi row is a whole card now — see A Multi row is a whole card — and speaks its vocabulary:
show_valuebecomeshide,value_positionbecomesreverse_secondary_info_row. Existing configs keep working as they are; the editor's Migrate config button updates your YAML whenever you're ready.- A row that set neither
show_valuenorhideshows its icon, name and value now — the value only, on a Multi Feature. To keep the bare bars, addhide: [icon, name, secondary_info];EPB.doctor.audit()lists every Multi concerned.
✨ New¶
📏 density: single_line: the whole card on one line¶
A third value for density: icon, name, value and bar laid out as
four neighbours on a single row instead of a name/value block beside the icon.
The row reads as one sentence — the name takes the secondary info's own type,
the two are joined by the same · separator that already joins infos, and the
line truncates once at its end rather than each field cutting off inside its own
box. reverse_secondary_info_row flips the whole
row here: bar first, text after. It is the line every Multi row is drawn as, and
any card can use it.
📐 Bars that start at the same x¶
A Multi lines its bars up on its own again, as in 1.6.2: every row takes the
text column of its widest row, whatever each one prints — 9 % and 78 %,
900 W and 1600 W (bar_aligned, on by default; false turns
it off). Give it a name, and every card sharing that name lines up the same way,
across cards: a Multi and the cards beside it, a vertical-stack-in-card, an
auto-entities list. The column widens with the text at once and narrows only
once a shorter text has held for 30 seconds, so a changing value doesn't keep
moving the bars: no width to guess, no card_mod.
⭕ A ring around the icon¶
bar_position icon draws the bar as a ring around the icon,
on cards and badges alike. bar_size sets its thickness,
bar_orientation rtl turns it the other way, and it takes
the bar's colors and theme zones — bar_color_mode segment,
rainbow and rainbow_full included — along with watermark and
peak_marker marks. It fills from empty when the card appears,
like the bar. Badges can also be made frameless and
marginless from the editor now.
🧩 Both Multi cards get a visual editor¶
No more YAML-only. An entity list you can add to, reorder and delete from, and a pencil on every row that opens that row's entire configuration — the card editor itself, not a cut-down copy of it.
What the rows share moves up to the card on its own — see Shared settings, shorter YAML.
🪶 The visual editor loads when you open it¶
The editor used to ride along with every card, on every dashboard. It now ships
beside the card, in entity-progress-card-editor.js, and loads the first time
you open one — the way Home Assistant loads its own cards' editors. A dashboard
loads half the code it did in 1.6.2 and spends over a quarter less time
compiling it; the editor costs 23 KB compressed, once, when you need it.
HACS brings it down with everything else. Installed by hand, copy
entity-progress-card-editor.js next to entity-progress-card.js: without it,
Home Assistant offers its own YAML editor instead.
➡️ Most of the bundle is translations for languages nobody uses (~300 KB) #141
(@davidcoulson)
🐞 An issue report in one click¶
The bug icon at the top left of the card editor copies everything an issue needs: your environment — card, Home Assistant and browser versions — then the card's YAML, each deprecated option and option without effect marked. Paste it into a GitHub issue as it is.
EPB.doctor.audit(), in the browser console, lists every card on every dashboard — views you never open included — carrying a deprecated option or an option without effect, and every Multi whose rows now show more by default.EPB.doctor.dump()gives the browser's exact version and operating system on Chrome, Edge and Opera over HTTPS, and says where the visual editor loads from and whether it did. Both work on any dashboard, a card of ours on screen or not.EPBis the card's console helper now:EPB.version,EPB.help()for the list, andEPB.doctorfor the tools above.EPB_DIAG.dump()keeps working.EPB.doctor.cards()lists the cards on the page, numbered, andEPB.doctor.inspect(2)— orinspect($0)from the DevTools — shows one of them: the value and range its bar is drawn from, and the config it kept. Each card's config and entity get a state — ok, invalid, deprecated, no effect, not found… — with the exact findings beside it.
🧪 Test a release candidate beside your install¶
Copy an RC's files to www/test/ and add
/local/test/entity-progress-card.js?suffix=rc as a resource: every element of
that copy registers under an -rc name — custom:entity-progress-card-rc, … —
next to the cards HACS installed, with its own editor, language files and
EPB_RC. See RC testing.
🔧 Improvements¶
A Multi row is a whole card¶
It used to be a bare bar, with the aggregator printing a value beside it. Every
row of an entity-progress-multi-card and
entity-progress-multi-feature is now a real progress card in its own
right — icon, name, value and bar on one line — and accepts what a card accepts:
hide, unit, decimal, watermark,
alert_when, per-row Jinja, tap actions — the lot.
entity-progress-multi-feature keeps its rows tight (it still fits a single
42px tile row): everything scales with the row height, and its rows start with
hide: [icon, name], which you can lift with an explicit hide: []. A slice of
a 42px row has no corner to annotate and no frame to light up, so it also leaves
out trend_indicator, status_label, the
icon badge and alert_when.
bar_max_widthreaches a Multi row, and indensity: single_lineit pins the bar rather than only capping it: every row's bar starts at the same x whatever its text, and the text ellipses first on a card too narrow for both. The--epb-multi-value-widthCSS hook does the same from the text side.
Shared settings, shorter YAML¶
A setting most marks of a family, or most rows of a Multi, have in common is written once at the top, and only the exceptions stay below: the visual editor files it there for you, and the card reads it the same way. Your YAML is tidied the next time you edit; nothing changes on screen. Usable on:
watermark:type,line_size,opacity,colorandas, shared bylowandhigh.peak_marker:type,line_size,opacityandcolor, shared bymin,maxandaverage— therangeband takes theopacityandcolor.entity-progress-multi-cardandentity-progress-multi-feature: every row option, shared by the rows —entity,attribute,nameandiconstay each row's own.
The watermark and peak_marker panels drop their separate defaults block with it: each mark is set on its own, and a family value written in YAML still applies.
hide, all the way¶
A hide list (not a Jinja one) is settled before the card renders, so
what it hides is no longer built and then covered up — it simply isn't there.
Its settings leave the editor with it, on every card, not just the Multi:
[icon] takes the icon's color, its animation, its circular background and its
badge; [progress_bar] takes the bar's own appearance and its watermark/peak
marks; [name], [value], [unit] and [secondary_info] each take theirs. A
Jinja hide does neither — its result can flip on any state push, so the part
is only hidden and its fields stay reachable.
value_compact moves the scale into the unit¶
A sensor reading 25 W in the morning and 1500 W at night no longer forces you to
pick one unit and live with it: it shows 25 W, then 1.5 kW, then 1.5 MW,
and 500 mW below the unit. Units that have no SI prefix — %, °C, m³ —
are left untouched. Three significant digits are kept — 1.23K, 1.65 kW —
where the raw value's precision gave 1K.
counter and number: your range, not the device's¶
A counter or a number drew its bar on its own range — often a limit set by
the device's maker that your readings never come near, like an inverter rated
far above what it ever produces. min_value and
max_value now override it, as a fixed value, an entity or a Jinja
template, so the bar speaks to your everyday use. The entity's range stays the
default when you set none.
➡️ [Bug]: number sensors not supported #143 (@mathieucarbou)
More entities find their own value¶
A valve, a humidifier, a water_heater and a media_player now read their
position, humidity, temperature and volume without the attribute
option spelled out, and Home Assistant's entity-first card picker offers them
too. A battery comes up twice there: the plain card, and the same one under
battery_adaptive.
Card feature¶
entity-progress-featureandentity-progress-multi-featureregister through Home Assistant's newerisSupportedAPI (2025.6+), keepingsupportedfor older versions: a card that hosts features offers them even without an entity of its own, Mushroom's template card included.
Moving with time¶
state_content:last_changed/last_updatedcount live — they change the moment their text does, not only on a state change.- Running
timerin%,min,hord: it moves at each percent in%and each second otherwise, on the timer's own second, where it moved once a minute — a 5-minute timer in%jumped 20% at a time.
Thickness and reading mode per mark¶
watermark and peak_marker take line_size at
three levels now — the whole family, one side (low/high), or a single mark —
each falling back to the one above it. watermark's as follows the same three
levels, and peak_marker gains a line_size of its own, 1px unless you set it.
watermark:
line_size: 4px
low: { value: 20, line_size: 9px } # this side only
peak_marker¶
range: the band between the minimum and the maximum over its window, filled on the bar. The bar says where the value is now; the band says how far it has swung. It doesn't need the minimum and maximum marks themselves — a band alone is enough.- Shapes: a mark takes the same six as a
watermarknow —area,blendedandstripedfill a region besidesline,roundandtriangle. A filledmincovers everything below it, a filledmaxeverything above: the zones the value never reached. averageweighs each value by how long it held, as Home Assistant's own statistics do.
bar_position: background, polished¶
The bar fills the whole card, and the rest of the card keeps working around it:
- Hover and ripple: the feedback covers the whole card, icon included — it was painted under the bar and never showed.
- Circular background: one you asked for —
force_circular_backgroundor an icon action — sits on the card's own color and stays visible, where it vanished into the fill. - Icon: it no longer drowns in a fill that carries its own color — the
circular background comes out to protect it.
--epb-icon-shape-colorstill wins.
The visual editor¶
Home Assistant's own words, fetched when needed¶
About thirty labels — Entity, Attribute, Icon, Name, Theme, Unit, Minimum, Maximum, Color, the tap/hold/double tap behaviors, Position — are read from Home Assistant's own translation catalog instead of a copy shipped inside the card. They read exactly like the rest of your interface, in every language HA speaks, and they follow HA's own rewordings from then on without an update here. The card carries that much less: the translation table lost a fifth of its weight.
On a Home Assistant older than the one that introduced a given label, that whole group falls back to English rather than showing half of it translated — every other label stays in your language.
The editor's own labels are only needed when you actually open an editor, so
they no longer travel inside the card: they sit next to it as one small file per
language, fetched on demand. The card itself, error messages included, stays
fully translated and works offline exactly as before. Installed through HACS
there is nothing to do; installed by hand, copy the
entity-progress-card-<lang>.json files next to entity-progress-card.js.
- Wording: labels dropped what their own panel already said — "Show minimum" became "Minimum", "Bar below content" became "Below content" — in all 39 languages.
- Duration units show each language's own abbreviation, from the browser:
jin French,ggin Italian,天in Chinese.
Laid out like Home Assistant's own editors¶
One "Markers & Alerts" panel held a hundred options; there are four now — Watermarks, Peak markers, Indicators & Labels, Alerts — and a card only gets the ones it can use. Inside each, a mark's fields follow what it draws: the line thickness only shows for a mark drawn as a line and sits next to its type, the watermark's reading mode sits with the threshold it reads, and every greyed hint shows the value that mark inherits rather than a built-in default.
A field left alone on its row takes the whole width now instead of leaving a hole beside it — whatever the card, the layout, and whichever options your config happens to hide. The editor's spacing follows Home Assistant's own card editors too: 24px between rows, 8px between two fields sharing one, 12px inside a panel.
- Panels:
Layout & Sizingcomes last on every card now, and reads top to bottom as shape (layout,density), then size, then frame (frameless/marginless). - Rows: the decimal count sits beside the unit, the trend's up and down colors share a row, and an Icon heading separates the icon fields from the theme ones.
Only what works, and nothing forgotten¶
- Inert options leave the YAML: a setting a change leaves without effect —
text_shadowoffoverlay, a color mode once the theme is gone,multilineincompact, a bar size — is set aside for the session and comes back as it was if you undo the change. Migrate config shows for one already in your YAML, and sets it aside the same way. - Deprecated options: written next to its replacement, an old option is only
removed now — the new one wins, on the card and through Migrate config
(
additionsbesidebar_stack, a legacy watermark key beside its override object). - Emptied fields leave the YAML: clearing one removes its option instead of
writing
''. trend_indicatoris no longer offered next to astatus_labeltemplate, which takes its corner. Switched to Advanced, it arrives with awindowalready set — the one setting that changes what it measures; turn it off there to keep the point-to-point comparison.windowsliders: each unit stops where it stops meaning anything — seconds offered 604 800 positions, minutes 10 080.- Card size: unchecking it hands
min_widthandheightback instead of discarding them, and it opens on the card's own height. height: its custom mode and back keeps the height you had.peak_marker: hiding a mark leaves nothing behind in the YAML — the redundantmin: falseit used to write is gone. Existing ones keep working.colorandbar_color: their picker names the default instead of leaving the box empty — "State (Default)", the entity's own state color, which is what the card draws while neither is set. Picking that entry writes nothing into your YAML.
🐛 Fixes¶
Refreshes¶
- Every state change: a card refreshed on every state change anywhere in Home Assistant whenever its entity had no display precision — most entities. It refreshes only when one of its own entities changes now.
- Same-device status:
icon_animationwashing_machine/battery_chargingandthemebattery_adaptivecould lag behind the status entity on the same device; they follow it at once now. - Running
timer: analert_whenthreshold crossed while the timer ran stayed dark until its end, and so didstatus_label's color. Both follow the bar now. - Back and forth: a text or color that changed and changed straight back could stay on the in-between value until its next change.
Values and units¶
- Lights: one added through Home Assistant's own entity-first card picker filled its bar to about 39% at full brightness. It reads the real brightness now, and the setting behind it is swept the next time you edit the card — since 1.6.1.
unit_spacingauto: the space before%followed the number format instead of the language, so42%showed for anyone who had not changed that setting — sixteen languages get their space back. Andstook a space wheremsandμsdid not.state_content:last_changed/last_updatedread a second older than they were.
Watermarks and peak marks¶
watermark.line_size: the line-thickness slider had no effect — the editor saved the value in a place the card never reads, so the line stayed at its default. It lands in the right place now, and a leftover key from before is swept the next time you edit the card. Seewatermark.
➡️ Teams Benjamin D- Type: the editor left a mark's type empty whenever it followed its
family's value instead of carrying its own, and showed nothing at all for a
bare
watermark: {}. - Shared level: a value set the same way on every visible
peak_markermark never moved up to it, and editing one mark could switch a hidden one back on. - No
window: apeak_markerwritten without one drew nothing at all. It falls back to2hnow instead of dropping the whole block. - Long windows: on an entity reporting every few seconds,
peak_markerdrew no marks at all. Any number of recorded points works now — since 1.6.2. - Live marks:
peak_marker's marks were worked out once, from the history loaded with the card — later readings never counted, old ones never left the window. They follow the live value and slide with the window now — since 1.6.2.
trend_indicator¶
threshold: 0, the object form's own default, showed a downward arrow on a value that had not moved at all. It reads stable now.- Plain arrow: it fell back to flat at the next state change anywhere in Home Assistant; it holds until the entity moves again.
window, first arrow: it only appeared at the entity's next state change, which on a slow sensor is minutes away. It shows as soon as its history loads — since 1.6.2.window, back to flat: the arrow never went back to flat once the value stopped moving, and the same reading could count over and over. The window slides with time now, not only with new readings.
Rendering¶
framelessand cards embedded in an entities or vertical-stack card: a glass theme's::afterdecoration still painted over them. Both pseudo-elements are neutralized now, and a theme's!importantno longer wins.bar_segments: segmented bars drew opaque strips between the cells on a translucent card, and no visible gaps at all on a frameless one. The gaps let the card through now.- Icon size: a custom one (
--epb-icon-size, or any theme setting it) resized the icon's box but not the icon itself, which stayed at Home Assistant's own 24px. Both follow now. alert_whenhighlight: label: the label stayed on its grey fallback color instead of the alert's, on any card rendered before Home Assistant inserted it.- Icon badge: in
layout: vertical,badge_iconlost its top for everybar_positionbutdefault— since 1.6.1.
➡️ Discord @mooseBringer
Console messages¶
- Invalid option: its path reads
watermark.low.value, notwatermark,low,value. decimal: a refused value asks for a positive whole number, where it asked for "a valid decimal number".
📚 Documentation¶
trend_indicatornow says what it measures — the bar's own percentage, not the entity's raw state — and what eachbasiscompares:averageagainst the window's mean,edgeagainst its oldest sample,slopeagainst a line fitted through all of them. The three are identical without awindow, which wasn't written down anywhere either.- The Multi section says what a row actually accepts, announces both visual
editors, and
show_value/value_positionjoin the deprecated-options table with what replaces them. max_valuesays what acounterand anumberbring with them — their own range, used when you set no bounds — that an explicit bound overrides it, and which minimumcenter_zerokeeps there.- Feature hosts lists the cards
entity-progress-featureandentity-progress-multi-featurewere tested in: Home Assistant's Tile and Mushroom's Template card. - A new option map shows, for every option, which variant takes it, whether its visual editor offers it, and its default.
- The option tables of the cookbook and the reference list every option each
variant takes — 28 rows were missing — and the templates' table no longer
lists
bar_scaleandpeak_marker, which they never took. - A review of the documentation, with minor corrections.
Demo dashboards¶
- The demo dashboard splits in two:
demo-dashboard.yamlis the showroom,demo-dashboard-dev.yamlkeeps it plus the regression and deprecated-option benches. - Every card of
demo-dashboard-dev.yamltargets the development build — a badge and three cards still used the released one. - The demo dashboards are checked against the real schema now: every card must
survive the card's own validation without losing an option it declared. Six
options that silently did nothing — a missing
peak_markerwindow, asecondary_infokey that was never one,badge_iconon a badge that no longer takes it — are fixed. - The demo helpers gain a real
numberentity, from-50to10. - The showroom carries no deprecated option or option without effect anymore, and a test keeps it that way.
Washing machines¶
- The cookbook's washing-machine recipes build a complete card for each brand,
with
icon_animation: washing_machineon all three — no configuration needed, SmartThings included. icon_animationlists Samsung SmartThings among the integrations it recognizes as running.
🧹 Under the hood¶
⚡ What a card costs, 1.6.2 → 1.6.3¶
About these numbers: they come from a lab, not from a dashboard — 20 cards on a 3,000-entity instance, rendered in a virtual DOM (happy-dom) because it makes the bench simple to run, median of 200 runs per row, best of several runs alternated between the two versions. The script is public, so anyone can rerun it. Read them as a trend, not as a speed-up you will see or feel as such: the gain shows as less load on constrained devices — a wall tablet, an NSPanel — more than as a snappier card on a desktop.
| Per card, median (µs) | 1.6.2 | 1.6.3 | Gain |
|---|---|---|---|
| Another entity changes | 1,099 | 10 | ÷108 |
| Its own entity changes | 1,102 | 371 | ÷3.0 |
One tick of a running timer |
689 | 129 | ÷5.3 |
Measured with scripts/compare-hass-updates.js.
- The refresh tick re-reads only what time moves, and fires when what it shows
changes rather than on a fixed cadence: an hour-old
last_changedticks once an hour, not every minute. - A tile feature at the top or bottom of its tile no longer forces a style recalculation each time Home Assistant redraws the tile.
Lighter to load¶
| Bundle | 1.6.2 | 1.6.3 |
|---|---|---|
entity-progress-card.js |
648 KB | 328 KB |
| … compressed | 157 KB | 86 KB |
| … compiled by the browser (lazy) | 36 ms | 26 ms |
| … bytecode kept | 587 KB | 365 KB |
entity-progress-card-editor.js, on first opening |
— | 81 KB |
| … compressed | — | 23 KB |
Measured with scripts/compare-bundles.js. Half the size
and over a quarter less compiling, despite everything this release adds; compile
times come from Node's V8 — read the ratio, not the milliseconds.
Lighter in memory¶
- Translations: the translation table used to be nearly half the shipped file; what stays in it now is 4%. The editor's labels come from Home Assistant or from a small per-language file, loaded only when an editor opens.
- History samples:
trend_indicatorandpeak_markerkeep theirs in one circular buffer, trimmed to their window, instead of one object per reading. The longest window allowed, 7 days, on an entity reporting every 10 s (worst case scenario) takes 710 KB where it took 3.7 MB.
Code and tooling¶
- The Multi cards are validated by a real schema at last, like every other card type — an unknown option is dropped instead of quietly reaching the DOM.
- The card's default attribute per domain and the entity picker's own suggestions come from one shared table instead of two that had drifted.
- The percentage math now lives in a class of its own, behind 48 new tests.
- A deduplication sweep across the card, the editor and the shared utilities: close to thirty blocks that existed in two copies now have a single definition, and a few values the card recomputed on every render only to discard them are gone. Where each option has any effect, what it falls back to without one and what a density imposes are now one rule each, shared by the card's validation and its editor.
- Debug logs name a card by its element tag rather than its class.
- The release build rejects class
static {}blocks on their own, the one newer syntax Chrome 92 lacks. - The i18n tooling reads the generated block on a CRLF checkout, and
.gitattributespins the working tree to LF.
➡️ fix: support CRLF checkouts in i18n tooling #142 (@dajiaohuang) - The test suite checks what the editors show and write, the refresh tick, Jinja subscriptions, history requests and the light bundle, and can no longer hang on a card left mounted.
- The editor is built into a file of its own that reads the card's modules instead of copying them: the build fails if one ends up in both files.
- 732 automated tests run before every push: 545 on the card's logic, 187 mounting real cards and editors in a virtual DOM. The documentation is checked against the schema too — its YAML examples, defaults, compatibility badges and option tables — and a test fails when the option map falls behind the code.
scripts/compare-hass-updates.jsmeasures what a hass update and a tick cost per card, between two bundles.- The console helper answers for the bundle it came from — a dev build installs
itself as
EPB_DEV— and the dump reports the two tile features' version.
We care about getting the details right — but even so, something here might have slipped through. You don't need to be a developer to notice it. If something feels off, that's reason enough. Open a GitHub issue. Or say hi on Discord. We'd rather know than have you go looking for a workaround on your own.
➡️ Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.6.2...1.6.3
1.6.2¶
This release finally gives your bars a memory — and your alerts a brain.
Another big one: alert_when gains a Jinja-driven trigger, trend_indicator
and the new peak_marker finally get a real history-backed memory instead of
comparing against whatever was on screen a moment ago, bar_segments gets
rebuilt from the ground up — real cells, real gaps, and working correctly with
center_zero for the first time — and the Tile Feature finally gets a full
visual editor of its own, no more YAML-only. Documentation gets a full overhaul
too — a new Cookbook of copy-paste recipes, every --epb-* CSS hook finally
documented and tested, and all 12 built-in themes get a real screenshot. A
couple of config shapes changed along the way (watermark.low/.high,
icon_animation: none), fully backward-compatible — see
Breaking Changes below.
⚠️ Breaking Changes¶
🧹 watermark.low/.high reshaped¶
You can update right away — no extra action needed on your part.
low_color/high_color/disable_low/disable_high and low_as/high_as are
gone. Both sides now live on low/high directly: false hides a side, a
plain value shows it with the default look, and
{ value, as, type, opacity, color } overrides just that one side. Old configs
keep working exactly as before — auto-migrated for the session (console-warned)
— use the editor's Migrate config button to update your YAML permanently
whenever you're ready, no rush. See watermark.
🧹 icon_animation: none retired¶
Nothing to do — already migrated for you. An unset icon_animation has
meant "no animation" since 1.6.1; the explicit none value has done nothing
since then except linger as a documented no-op. It's no longer accepted —
auto-migrated for the session (console-warned), use the editor's Migrate
config button to update your YAML permanently whenever you're ready, no rush.
✨ New¶
🎯 alert_when goes Advanced: trigger it from a Jinja condition¶
A new Simple/Advanced chip in the editor switches alert_when between the
static above/below thresholds and a single jinja condition that replaces
them entirely — polymorphic like status_label/badge_icon: return a plain
true/false to trigger the alert with its existing
color/highlight/animation/label, or an object with any of those four
keys to override just that push, falling back to the static value for whatever's
left out. See alert_when.
alert_when also reaches Template and Badge Template for the first time —
Jinja-only there (no above/below, no static fields to fall back to), so the
object return is the only form worth using.
🎨 The full CSS styling API, finally documented and tested¶
All 60 --epb-* CSS custom properties are documented now, each with its own
demo-dashboard card isolating exactly what it does. See
CSS hooks.
New this release: --epb-icon-shape-opacity and — Card and Template —
hide: [shape] remove the circular shape behind the icon, replacing the
card_mod override that broke in 1.6.1. --epb-icon-color/
--epb-icon-shape-color recolor the icon and its background independently;
--epb-icon-shape-hover-color sets a clickable icon's hover color straight from
a theme. --epb-ping-color/--epb-ping-spread set the color and the reach of
the ping ring burst, shared by alert_when's border and label modes and by
icon_animation: ping.
➡️ [Feature]: Configuration possibility for the icon background visibility #136
(@RkcCorian)
🛡️ Better Jinja protection¶
A half-typed template is no longer reported as an error while you edit a card,
and an unfinished one ({{ x with no closing }}) never reaches Home Assistant
at all. A template HA rejects isn't re-sent until it changes, and the console
now names the field and the reason, in the same shape as the deprecation
notices.
🔢 Three new ways to format the displayed value¶
All opt-in, Card and Badge: value_compact abbreviates large
numbers (1250000 → 1.3M, locale-aware, decimal caps the digits without
forcing trailing zeros); unit_position moves the unit before
the value for currency-style display ($100); value_sign forces
an explicit +/-, handy on center_zero/bar_stack: { mode: net } deltas.
📈 trend_indicator finally has a real memory¶
Backed by a real sample buffer now, instead of just comparing the last two
readings — no more flipping on a single tick of sensor noise, or resetting to a
meaningless "flat" on every reload. window ('5min', '2h', '1d'…) sets
how far back to look, basis picks average/edge/slope, and threshold
sets a dead zone in percentage points; eligible entities (sensor/number, no
attribute override) seed the window from Home Assistant's own history on load.
colored: true tints the arrow with the icon's current color;
up_color/down_color/flat_color override per direction. The plain
trend_indicator: true boolean still works exactly as before, now with a small
built-in dead zone. See trend_indicator.
🎯 peak_marker: min, max, and average, right on the bar¶
Born from the same history read as trend_indicator above: marks the minimum,
maximum, and average value observed over a window directly on the bar — reads
at a glance where the current value sits relative to its own recent history, no
separate helper or template needed. min/max/average are each opt-in:
true for the default look, a color string as shorthand, or
{ type, opacity, color } to override just that one mark, falling back to
peak_marker's own top-level type/opacity for the rest. Same eligibility as
trend_indicator's history seeding (sensor/number, no attribute, not
timer/counter), Card and Tile Feature only. See peak_marker.
🧹 watermark cleaned up, inspired by peak_marker¶
Building on the reshape above, type/opacity/color are now also top-level
watermark defaults — the same shape peak_marker just introduced: whichever
side doesn't set its own falls back to them, and once both sides have their
own value for one of these three, the shared default quietly drops out of the
config (nothing reads it anymore). The editor's "Show low"/"Show high" toggles
replace the old disable switches, with per-side Type/Opacity/Color fields
alongside the existing per-side value/unit ones. See watermark.
🎛️ The editor never looked this close to native Home Assistant¶
- Editor: the main mode toggles are now segmented pills instead of separate
chips or a plain switch, styled straight from Home Assistant's own design
tokens instead of one-off colors. Found along the way:
icon_animation's own toggle had never been translated correctly — every language showed the literal placeholder "Trigger via template". - Editor: interactions get a "+ Add interaction" picker — HA's optional
actions are now revealed one at a time instead of a "show all" toggle, the
same picker
ha-form's ownoptional_actionsfield offers.
🧩 The Tile Feature gets its own visual editor¶
Previously YAML-only, entity-progress-feature now has a full visual editor —
entity, min/max value, appearance, watermark, and now peak_marker too. Its
entity field is optional: leave it blank and the feature automatically shows
whichever entity the parent Tile card is already using.
🔧 Improvements¶
- Editor: placement and width of several appearance fields are more consistent now (Card, Badge).
status_labelaccepts a plain string — shorthand for{ jinja: '...' }, covering most cases, same patternbadge_icon/badge_coloralready use. The Map form works exactly as before wheneverposition/color_sourceare also needed. Seestatus_label.bar_segmentsnow works properly withcenter_zero: each arm segments independently (bar_segments: 10gives both the positive and negative side their own 10-cell breakdown, meeting cleanly at zero) instead of sharing one set of dividers across the whole bar. Not available together withbar_color_mode: rainbow_fullorbar_stack— both now clearbar_segmentsautomatically instead of a meaningless combination.density: compactnow works withlayout: verticaltoo: previously it only narrowed the column in horizontal — vertical has no equivalent narrow shape, so compact instead hidesname/secondary_infoand shrinks the card to a single row (icon and a thin bar only). The editor reflects this:name/secondary_infoshow as forced-hidden under Hide once compact is on, andvalue/unitdrop out of the Hide picker entirely.
➡️ [Bug]: Misaligned icon #139 (@RkcCorian)
🐛 Fixes¶
bar_color_mode: rainbow_full's marker size could ignore your chosenbar_sizewhen the bar was positioned at the top or bottom (alsooverlay/backgroundon Card) — always looked like the largest size instead.- Changing the bar's position could leave an invisible, unused size setting behind in your saved configuration — cleaned up automatically.
- Template/Badge Template never migrated
watermark.low/.high's legacy forms (bare entity-id string,low_as/high_as/low_color/high_color/disable_low/disable_high) — an entity-sourcedwatermark.highsilently ignored the entity, despite a console warning claiming it had been migrated. Now shared by every variant.
➡️ [Bug]: watermark.high renders at the wrong position when set to an entity, correct when hardcoded #140 (@Gunth) status_label's own Jinja pill stayed permanently hidden oncealert_when.highlight: 'label'was configured, even while the alert itself was inactive — the pill is now handed back tostatus_labelwhenever the alert isn't currently triggered.- The editor's "Alert" toggle used to wipe the whole
alert_whenconfig (including a typedalert_when.jinjatemplate) every time it was switched off — now preserves a draft, likestatus_label's own toggle already did. - Same bug on the "Markers" toggle: switching it off used to permanently discard
the whole
watermarksetup (type, thresholds, colors, …) instead of just hiding it — now preserves a draft too.bar_max_width's toggle had the milder version of the same issue (lost a custom value, fell back to the 300px default) — fixed the same way. - Editor field labels are now translated in all 39 supported languages — several had silently stayed in English since the day they shipped, invisible to the usual checks. The short Jinja field hints ("Returns String…") are still English-only for now.
theme: critical_when_low's editor label listed "disk" as an example alongside battery — misleading: the disk sensor most people actually have (disk_use_percent, % used) belongs tocritical_when_highinstead, already listed there. Removed fromcritical_when_low, across all 39 languages anddocs/theme.md.layout: verticalwithbar_position: top/bottom/backgroundand a hiddenname/secondary_infocould squeeze the icon into whatever space was left over under a small explicitheight:, instead of centering it.
➡️ [Bug]: Misaligned icon #139 (@RkcCorian)bar_segments: a marker (watermark, peak marker, or the zero mark) landing on a segment boundary is no longer hidden.
➡️ Discord @RKT62watermark/peak_markerwithlow_as/high_as: 'percent'could land on the wrong side ofcenter_zero's midpoint (Template/Badge Template: always, values are shaped that way there) — now lands on the same side as the value it represents.- Several editor fields showed with no label at all (the free-text fallback
under
min_width/height/watermark's line thickness, and the status-pill text input underalert_when) — labelled now, across every language. - A handful of editor labels stayed on outdated English wording in every language but English, left behind after the English text itself was later reworded — corrected across all 38 non-English languages.
decimal's editor label now uses Home Assistant's own wording, "Display precision", translated in 36 languages.layout: horizontalno longer carries a "(default)" suffix in the editor, across all 39 languages.- Round watermark and peak marks sat 1px low, flush with the bar's bottom
edge at
bar_size: xsmall— exactly centered now. - Editor labels named the wrong thing in 15 languages. Swedish, Danish,
Norwegian, Indonesian, German and Ukrainian called the progress bar a drinks
bar, a toolbar strip or a panel; Swedish, Estonian and Latvian called an
entity a device, an object or a unit; Macedonian's unit label read as "unity";
Bengali and Hindi left
attributein English mid-sentence. Czech, Slovak, Slovene and Greek each used two different words for the bar in the same editor — one each now.
➡️ Discord @mooseBringer show_valueignored the entity's own display precision in Multi-Card and Multi-Feature, always showing two decimals. It now followsdisplay_precisionlike a standalone card, and shows none for timer, counter and duration entities or for a percentage.
📚 Documentation¶
- New: a Cookbook (
docs/cookbook.md) — copy-paste YAML recipes for every visual effect, layout option, and card variant, each with a screenshot and a companion demo-dashboard card. - New:
Value shapes & shortcuts in
configuration.md's Conventions — names, once, the value/entity/Jinja shape shared bymin_value/max_value/alert_when/watermark's value, and explains whywatermark's andpeak_marker's one-word mark shorthand each stand for something different (a value vs. a color) rather than looking like an inconsistency. Each option's own section now links back to it instead of re-deriving the pattern. - The release notes' and CHANGELOG's own
graphic-effects-compatibility.htmllinks now point throughhtmlpreview.github.ioinstead of GitHub's raw blob view, so the page actually renders instead of opening as source code. configuration.mdgainshide'sshapeoption,alert_when's Advanced mode with new examples,value_compact,unit_position, andvalue_sign.hide: [shape]'s editor label translated across all 39 languages + template — a descriptive phrase ("Icon's circular background") rather than the bare English word, matching how the option is described inhide.- All 12 built-in themes now have a real screenshot in
docs/theme.md— 7 were text-only before. Every theme (pluscustom_theme/bar_color_moderight after) follows the same shape now too: image, description, collapsible YAML, collapsible ranges table, note — matching the Cookbook's own visual-effect entries. - Corrected a stale claim in
docs/theme.md:bar_color_modewas documented as having no effect undercenter_zero— it does, andrainbow_fullspecifically was built withcenter_zeroin mind (each arm keeps its own always-full gradient, marker crossing the visual center at zero). docs/theme.md's DOM reference gainspeak_marker's own mark elements (.peak-min/.peak-max/.peak-avg), missing since that feature shipped above; theViewCore.minGridRowsdescription updated for the new single-row case (layout: vertical+bar_position: top/bottom/background+name/secondary_infoboth hidden).docs/troubleshooting.mdupdated: a version that still looks old right after updating usually means HACS is lagging behind — use ⋮ → Redownload.
➡️ Configuration Error on mobile devices #137
🧹 Under the hood¶
- Badge's own schema silently accepted
hide: [shape]even though Badge has no shape to hide in the first place (Badge Template already excluded it) — now consistently blocked for both. - More duplicated code across the card and editor internals was consolidated (CSS repaint, Jinja-pushed-number handling, Badge/Badge Template's shared schema, stylesheet selectors, several editor toggle/mode-picker fields).
- Editor translation keys are organized more consistently, and a handful nothing in the editor ever actually read were removed.
- A handful of editor fields that happened to carry the exact same label as a
neighboring one (
bar_position/unit_positionboth said "Position",alert_when_mode/icon_animation_modeboth said "Trigger mode") now share a single, shorter label instead of two redundant copies. - A new automated test suite now runs on every change (schema validation, progress-bar math, theme color resolution, number/duration formatting, legacy-config migration) — nothing user-facing changes, but a regression in this internal logic gets caught automatically now instead of only during manual testing.
- Internal config defaults (watermark, peak marker, trend indicator, action buttons) are now read directly from the validation schema itself instead of a separate hand-maintained table that could silently drift out of sync with what actually validates.
- The visual editor's internal code was simplified and de-duplicated in several places (mode-toggle fields, field-update logic) — no visible change, just less code to maintain.
- Various internal code cleanup and performance optimizations — no visible change.
- The
pingring animation collapsed from six keyframe variants to one shared keyframe, andbar_stack's four internal render variables moved off the public--epb-*prefix. - Editor dropdowns and
hide's chip list read their allowed values off the schema that validates them, instead of a parallel list per variant. - Duplicated logic consolidated across the card, schema and editor — no visible change.
- The Tile Feature's validation schema is derived from the Card's instead of being written out separately — a new option reaches every variant the same way.
- A DOM test suite now mounts every card, badge, feature and editor on each release build, and CI builds the shipped bundle on every push.
We care about getting the details right — but even so, something here might have slipped through. You don't need to be a developer to notice it. If something feels off, that's reason enough. Open a GitHub issue. Or say hi on Discord. We'd rather know than have you go looking for a workaround on your own.
➡️ Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.6.1...1.6.2
1.6.1¶
A bigger release than it looks: combine several bars into one card, themes and
per-icon animations reach Template, status_label/badge_icon can drive their
own color from a single Jinja condition, a proper keyboard/screen reader pass,
and a handful of layout options that couldn't quite do what people needed yet.
Fully backward compatible — nothing to change in your existing dashboards.
⭐ Highlights¶
📊 Combine several bars into one card or Tile feature¶
entity-progress-multi-card / entity-progress-multi-feature stack several
full-featured progress bars (each with its own colors, state and tap actions)
into a single card or a single Tile feature row, instead of one card per entity
— handy for printer ink cartridges, a set of batteries, or any group of related
sensors. A new, thinner bar_size: xsmall helps fit more of them in a tight
space.
A small bar is enough on its own for something like a printer cartridge, but not
when the number itself matters. Set show_value: true to show each entity's own
value right next to its bar.
See multi and show_value.
➡️ [Feature]: Multi-bar card/feature #126 (@EDelsman)
📐 A more compact layout: bar_position: compact_below¶
name and the value now share one row (value right-justified), freeing the
progress bar to use the card's full width on its own row underneath — instead of
the bar and the value fighting for the same narrow space, or the value sitting
in empty, unused room. See bar_position.
➡️ [Enhancement]: Display value above bar #123 (@davidcoulson)
🎬 Trigger icon animations from a template¶
icon_animation now accepts a Jinja condition ({ effect, jinja }) instead of
relying only on automatic entity-state detection. See icon_animation.
➡️ [Enhancement]: template/condition to trigger the icon animation directly #125 (@FoxP)
🏷️ Status label pill¶
status_label draws a small rounded status pill in the card's corner
({ jinja, position, color_source }) — colored automatically from whatever
color the progress bar currently shows by default (color_source: icon to
follow the icon instead), or set your own color directly by returning
{label, color} from the template instead of plain text.
alert_when.highlight: 'label' reuses the same pill to flash a fixed alert
label instead of tinting the border or background. See status_label and
alert_when.
🎫 One template, both badge icon and color¶
badge_icon can now return a {icon, color} object instead of just an icon
name — one condition drives both at once.
See badge_icon.
🌈 A hue-picker style bar: bar_color_mode: rainbow_full¶
The track always shows the theme's complete gradient end to end — not just the
filled portion, like rainbow already does — with a small marker sliding along
it to show where the current value sits, closer to a hue-picker strip than a
traditional progress bar. Works with center_zero too, each arm showing its own
half of the gradient in full.
See bar_color_mode.
⏱️ Smarter countdown refresh (and a fix for stalled Template timers)¶
A Template card's now()-driven countdown (e.g. a secondary: line ticking
down a timer) could freeze after its first render — Home Assistant only pushes a
fresh now()/utcnow() value once a minute on its own. Add
fast_refresh: true to opt that Template card into a forced per-second refresh
instead. Not automatic (it re-subscribes every second), and standard
cards/badges/features don't need it — they already self-correct on their own.
See fast_refresh.
🎨 A friendlier theme picker¶
The built-in theme list is reordered for readability: battery_adaptive (the
one most people reach for) comes first, and each Critical when X/
Optimal when X pair now sits together instead of being split into two separate
groups.
🎯 A center_zero-aware "Critical when extreme" theme¶
theme: critical_when_extreme_center brings critical_when_extreme's "danger
at both ends, safe in the middle" shape to
center_zero — green at zero, red at both
extremes, one continuous -100%/100% scale. Handy for a net power flow or a
deviation from a setpoint that can swing either way. See
theme.md.
🖌️ Theme support for Template¶
entity-progress-card-template / -badge-template can now pick a built-in
theme instead of writing your own color Jinja by hand — the icon and bar color
follow your percent: value automatically. bar_color_mode
(segment/rainbow/rainbow_full) is available too, for a gradient look
instead of a flat color.
📏 A hardened height¶
Card sizing got a real pass end to end: the min-height-as-a-floor protection
(never clip text when the OS/browser text-size accessibility setting is scaled
up) now applies consistently everywhere a card can live — Sections, Masonry, or
embedded in another card. An explicit height: now always wins outright as a
real, exact size everywhere too, instead of just another floor tall content
could still outgrow. See height.
➡️ [Bug]: Some parts of the card are not visible on Android #131 (@zkurzyns)
🧹 Consistent hide: behavior¶
Hiding a field (hide: [icon, name, secondary_info, progress_bar]) now always
gives its reserved space back, the same way, in every layout — previously each
field followed its own inconsistent rule. An empty value/unit row now
collapses too, whatever made it empty. See hide.
📶 Sturdier bar_segments¶
bar_segments: N's divider lines are real elements now, not a CSS gradient/mask
trick — all N segments are the same width now (the two end ones used to read
wider), and divider thickness can scale with the bar's own length instead of a
fixed size, tunable via --epb-bar-segment-gap hook. See
bar_segments.
📱 A compact density¶
density: compact shrinks the card to the smallest a complete card (icon,
name, value, bar) can be in a Sections grid, in one toggle — instead of
hand-tuning layout/bar_position/multiline yourself. Flipping it on through
the visual editor also pins the card's size outright, restored automatically if
you switch it back off. See density.
🃏 Show up when you pick an entity, not just when you search for a card¶
Home Assistant 2026.6 added an entity-first card picker: pick an entity, and
compatible cards show live previews right there instead of you having to search
for this card by name first. The Card and Badge now opt in — pick a compatible
entity (a numeric sensor, a cover, a light...) and they show up under
"Community" with a working config already filled in. Template/Badge Template
don't suggest themselves — they need a hand-written Jinja percent: to render
anything meaningful.
✍️ More inline styles for Jinja-rendered text¶
name/secondary/custom_info templates now also accept font-size,
font-weight, text-align, width, display, position and z-index (on
top of the existing color/background-color) — enough to build simple
multi-column layouts directly in a template.
➡️ [Enhancement]: JINJA Should accept more STYLE tags #129 (@emartoni)
♿ Better keyboard and screen reader support¶
The card and its icon (when either has its own tap action) are now properly reachable and understandable for keyboard and screen-reader users, not just mouse/touch:
- Tab reaches the card, and separately the icon if it has its own distinct
action (
icon_tap_action) — each now announces something meaningful (the entity's name and current value for the card, "Icon action" for the icon) instead of a bare, unlabeled "button". A badge, where only the card itself is ever clickable, no longer exposes its icon as a confusing extra stop. - Enter/Space activates each one, same as a mouse click.
- Tabbing to the card or the icon now shows a clear, colored outline (matching the entity's own color, following the card's rounded corners properly) instead of the browser's plain default rectangle.
- Fixed a structural issue where the card and its icon were both marked as "buttons" nested one inside the other — some screen readers and touch navigation handle that inconsistently. They're independent controls now, side by side rather than one inside the other.
🔧 Improvements¶
- The visual editor now remembers a field's value across a mode toggle
(standard/entity/Jinja) instead of resetting it to blank — switch
min_value/max_value/watermark.low/.high/alert_when.above/.below,badge_icon/badge_color,bar_effect,hide,icon_animation, orstatus_labelaway from Jinja and back, and your template is still there. - Jinja-capable fields in the editor now show a short hint under the field for what the template is expected to return (a number, a boolean, a string, or an object with specific keys) instead of leaving you to guess from the docs.
- Several fields in the editor's theme panel (
icon/color,bar_orientation,bar_size,bar_segments,bar_scale,bar_color_mode,interpolate) could end up alone in their row instead of sharing it with their usual neighbor, depending on which other options were active — all paired up correctly now.
🐛 Notable fixes¶
- The card could fail to load entirely on some older or embedded browsers (kiosk
panels), even though 1.5.x worked fine there.
➡️ [Browser Support]: #128 (@Slomo5) - A renamed device (Settings → Devices → rename) wasn't reflected in the card's
name.
➡️ [Bug]: Friendly name is not used #130 (@zkurzyns) bar_size: xlarge(orbar_position: below) with the icon hidden could get squeezed into too small a space, cutting the bar off.
➡️ [Bug]: Card not rendering correctly with xlarge bar and icon hidden #133 (@Ascathon)alert_whenwithanimation: pingandhighlight: backgroundsilently stopped ringing.- The bar could render as one flat color instead of the expected gradient with
certain themes (
bar_color_mode: segment/rainbow, real-value themes liketemperature/voc/pm25,custom_theme, andcenter_zero's negative half) — several related scaling bugs, all fixed. center_zerowith athemeandbar_color_modeset could leave a gap in the fill instead of a clean edge, for any value pastmax_value(or belowmin_value) — the two arms' own gradient size wasn't capped at 100% the way the fill itself already is.- The value/unit text next to the bar stayed capped at a narrow width with
bar_position: below,overlayorbackground, even though the bar wasn't actually sharing that row anymore. - A Jinja-templated countdown on a Template card could freeze after a few
seconds instead of ticking — add
fast_refresh: trueto get it ticking every second again (see the highlight above for why).
➡️ Reported alongside [Bug]: "Run" status not catched #127 (@annaoskarson) - A conditional
badge_icon/badge_color(only showing while some state holds) could flicker back on right after correctly hiding — any unrelated dashboard update was enough to force it back, ignoring the template's own current result. - A Template card with an empty
percent(e.g. still waiting on the entity it depends on) never painted its icon/bar/theme at all — now falls back to a plain 0% render instead of staying blank. - Hiding
nameorsecondary_infoon a horizontal card left an empty gap instead of the card shrinking to fit.
➡️ Follow-up to [Enhancement]: JINJA Should accept more STYLE tags #129 (@emartoni) icon_animationsilently never triggered on a Template card, even with a condition that always matched.- On a narrow horizontal card, the progress bar could shrink to an invisible sliver while the text next to it never gave up any of its own space.
- Text could get clipped when the OS/browser font-size accessibility setting was
scaled up (e.g. Android's system "Font size" option).
➡️ [Bug]: Some parts of the card are not visible on Android #131 (@zkurzyns) - A percent sensor with
custom_themezones extending past 100% (used on purpose as a color safety margin) could stop the bar from ever filling all the way, even at a real 100% reading.
➡️ [Bug]: JINJA Should accept more STYLE tags #129 (@emartoni) - Better height handling generally,
type: gridandtype: entitiesincluded (both had a hardcoded ~44.8px row-height guess — wrong the momentsecondary_infoisn't shown — now gone, replaced by real content-driven sizing; an explicitheight:now wins outright there too,square: falsefor grid) — see the 📏 A hardenedheighthighlight above.
➡️ Discord @RKT62 - The badge's
nametext could get its descenders (the tails on g, q, j, y) visually clipped — its line-height was pinned to exactly the font-size instead of leaving the same accessibility-safe margin the rest of the card's text already follows (issue #131). Unrelated to font size itself — purely a line-height/clipping bug. - The editor's Migrate config button never appeared for a config using the
legacy bare-entity-string
watermark.low/watermark.high(with alow_attribute/high_attributesibling key) — it was already auto-migrated and console-warned like every other deprecated option, but the button's own detection check was missing those two specifically, so there was no one-click way to actually rewrite the YAML. See Deprecated Options. - The editor's
bar_positiondropdown still offered "Compact bar below" withlayout: vertical, even though it only has a distinct effect withlayout: horizontaland silently reverts todefaulton save - it's no longer in the list oncelayout: verticalis selected, instead of being offered only to be quietly rewritten away. hide: value/hide: unitnever actually worked as a Jinja template — only the statichide: [value, ...]array form did. The template's live result was tracked correctly foricon/name/secondary_info/progress_bar(each has its own CSS class), butvalue/unithide by leaving text out of the assembled string instead, and that check only ever read the static config shape - silently blind to a Jinja result. Present sincehideitself first accepted a Jinja template.- The "nothing left to show, collapse the row" check for a
secondary_infodriven bycustom_info(or a Template'ssecondary) relied on:has()(Firefox 121+), past this card's documented 94+ floor — silently left a small empty gap on an older browser instead of collapsing the row. Replaced with a JS-computed check, so it now degrades correctly all the way down to the documented floor instead of quietly depending on a newer one. Present sinceicon_animation's washing-machine/battery-charging modes shipped. bar_segments: N's divider lines relied onround()(Chrome/Edge 114+, Firefox 118+, Safari 16.4+), well past this card's documented 94+ floor — the whole divider layer silently failed to render at all below that, invisible dividers with no console warning or visual clue anything was wrong. Rebuilt withoutround(); see the 📶 Sturdierbar_segmentshighlight above. Present sincebar_segmentsitself shipped.- A horizontal card that doesn't need the bar's own width (e.g. icon+name/value
only) still reported a Sections grid minimum sized for a full card with a bar
— see the 📱 A compact
densityhighlight above.
➡️ [Enhancement]: Set minimum width to 3 #134 (@FoxP) - Clicking the icon lit up the whole card too — fixed by rebuilding the click-feedback layering, modeled on Home Assistant's own native Tile card.
bar_effect: gradient/gradient_reverse, the alertblinkanimation, andicon_animation/alert_when'spinganimation could each fail on an older browser (Chrome/Edge < 111, Firefox < 113, Safari < 16.2 — see issue #128) — a flat, un-lightened bar for the first, a glitchy mid-cycle color for the second, not starting at all forping; all degrade gracefully now. The icon's circular background had the same issue, fixed by simplifying it to a technique that needs no fallback at all. See graphic-effects-compatibility.html for a full side-by-side of what changes on an older browser and how to test it yourself.- Template's
watermarklow/highin{ jinja: ... }mode never actually resolved — no subscription was ever wired for it, so the mark just silently never appeared (entity/plain-number modes were unaffected). Present since Template'swatermarkoption shipped. bar_color_mode: rainbow_full's marker didn't mirror withbar_orientation: rtl— the fill visually flipped, the marker stayed put and ended up on the wrong side of it. Present sincerainbow_fullitself shipped.theme: humidity's comfort zone (40–60%) used to split into a washed-outgreen/tealband instead of one solid color, and a 95% reading (mold/ condensation risk) landed ondeep-purple— a color that doesn't read as "alert" the way a 15% reading'sreddoes, understating the actual risk on the humid end. Ranges rebalanced to a symmetric 10/10/10/20 spread on each side of one solid green comfort zone. Seetheme: humidity.- The editor's watermark-related labels used the internal option name
(
Watermark,Low/High watermark source) instead of the everyday term for what they actually mark on the bar — relabeled toMarkers/Low/High marker source. Thewatermark:YAML key itself is unchanged. round/trianglewatermark markers didn't center precisely on their configured value — same pixel-rounding fixbar_segments's own dividers already got.- The visual editor's
heightfield had no way to switch from the slider to a free-text value (e.g.auto,calc(...)) — that mode only ever activated if the config already held one, set through YAML. A toggle now exposes it directly. bar_position: overlay'sname/secondary_infotext ran flush against the card's right edge, unlike the 7px of breathing room it already had on the left — now matches with 10px on the right too.- A Jinja-driven
icon_animation: { effect, jinja }could briefly fall back to automatic entity-based detection instead of staying off, right after the template's own result changed but before the next push resolved. Present sinceicon_animation's Jinja mode shipped in1.6.1-rc2. - Jinja-driven
badge_icon/badge_color/icon_animationfields could get visually stuck on a value that never matched the final, settled state — a multi-step script/automation (e.g. turning on a helper, then picking an option) makes Home Assistant push one intermediate template result per entity change, not just once for the final state, since the entities anandcondition depends on don't change atomically. Now debounced so only the last, settled result is ever rendered.
➡️ [Bug]: Cached / invalid Jinja result? #135 (@FoxP) climate/weatherentities used without an explicitattribute:rendered as a flat 0% — the card now defaults to the setpoint temperature forclimateand the ambient temperature forweather, each shown with the correct unit (climate: the system's configured °C/°F;weather: the unit that specific attribute reports).- Clearing
themein the editor could leave it silently stuck — it wrote an empty value instead of removing the key, which could wedgebar_size/bar_segments/bar_color_mode/interpolateas if a theme were still active, even on a config that was already saved that way. - A
bar_effect/hidechip that became incompatible or hidden while still selected (e.g. after changingbar_color_mode) stayed selected in the saved config with no way to remove it from the editor — it's dropped automatically now.
🧪 Try it: demo dashboard¶
docs/demo-dashboard.yaml is now a comprehensive,
interactive showroom covering essentially every option in this changelog, plus a
regression-test view (one card per closed issue) and a "README examples" view
reproducing the README's own recipes live. Import it with
docs/demo-dashboard-helpers.yaml as a drop-in
homeassistant: packages: file, and move the sliders to see everything react
live.
📚 Documentation¶
Wondering how any of this degrades on an older or embedded browser? The
graphic-effects-compatibility.html page is a standalone side-by-side of every
graphic effect (gradients, ping/blink animations, rainbow_full, …) at both
its modern and fallback tier — rendered live, open it directly in the browser
you want to check.
The docs got a pass of their own alongside the code this cycle:
docs/development.md gains a Quick start chapter (clone,
install, build, where to actually see your change), a clearer explanation of why
the build targets es2021, and a couple of stale claims corrected;
docs/troubleshooting.md's Browser Compatibility
section moved up front and got its own heading instead of being buried mid-page;
and docs/configuration.md/
docs/contributing.md were brought back in sync with
everything this release actually shipped.
Thanks to everyone who reported, tested and contributed 🙏
➡️ Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.6.0...1.6.1
1.6.0¶
The biggest release yet for the Entity Progress Card: it now lives inside Tile cards, taps feel native, the bar can be styled straight from your theme, and there's a whole set of new coloring, layout and alerting options — plus more built-in themes and eleven new languages. Almost all of it can be set up straight from the visual editor.
⚠️ Known issues (fixed in the upcoming 1.6.1 stable release)¶
- The card can fail to load entirely on older/embedded browsers (Chromium-based
kiosk panels) — fixed in 1.6.1-rc1.
➡️ [Browser Support]: chromium 92.0.4515.98 / After upgrade to 1.6.0 it stopped working on chromium #128 (@Slomo5) bar_size: xlarge(orbar_position: below) with the icon hidden can get squeezed into too small a space, cutting the bar off — fixed in 1.6.1-rc2.
➡️ [Bug]: Card not rendering correctly with xlarge bar and icon hidden #133 (@Ascathon)- Countdown Jinja templates on Template cards can freeze after a few seconds
instead of ticking — fixed in 1.6.1-rc2 (new
fast_refresh: trueoption).
➡️ Reported alongside [Bug]: "Run" status not catched #127 (@annaoskarson)
All three fixes are already merged and will be part of the 1.6.1 stable release. In the meantime, you can test them ahead of time via the 1.6.1 pre-releases — see the safe testing guide for how to try a release candidate without disrupting your main dashboard.
⭐ Highlights¶
🧩 Put a progress bar inside a Tile card¶
The card now works as a native Tile feature: add it to any Tile card, or anchor it to the top/bottom edge as a slim overlay. See Card types.
➡️ [Feature]: Adding the progress bar as a feature in a card #95 (@Gunth)
🖱️ Taps and gestures feel native¶
Tap, hold and double-tap now use Home Assistant's own gesture system — same behavior as official cards, on every device.
🎨 Style it from your theme¶
Friendly --epb-* style variables you can set from your theme or via card_mod
— no hacks needed. See the Theme Guide.
🌈 New bar coloring styles¶
With a theme active, choose how the bar is painted: distinct blocks (segment),
a smooth gradient (rainbow), or keep the current look (auto). Both segment
and rainbow now also pair with center_zero, theming each arm on its own half
of the range. See bar_color_mode.
🧘 Breaking Changes (Don't Panic)¶
A few options have a new, clearer syntax. Your dashboards keep working as they are — the card understands the old syntax and converts it on the fly. You'll just see a gentle reminder in the browser console; update your YAML whenever you feel like it.
max_value: <entity id>/max_value_attribute→ folded into max_valuedisable_unit→ folded into hideadditions→ renamed to bar_stack
Prefer not to wait? Open the editor and a Migrate config button rewrites your YAML for you. See Deprecated Options.
🚀 New Features¶
🔋 Battery-style segmented bar¶
Display the bar as separate blocks — like battery cells or signal bars. See bar_segments.
📊 Bar stack: combine several entities in one bar¶
bar_stack (formerly additions) combines several entities into one bar, with
three modes, per-entity colors, and center_zero support. See bar_stack.
🌀 Animated icons¶
Eight styles are now available (spin, pulse, bounce, shake, ping,
reveal, washing_machine, battery_charging). Most are active-state only,
but washing_machine and battery_charging also auto-detect a same-device
entity when entity itself doesn't carry the signal — e.g. Tesla Fleet's
separate sensor.<car>_charging_state, or a Home Connect/Miele appliance where
entity is the progress % and the running state lives on another sensor.
battery_charging's fill sweep even self-adjusts when the shown icon is a
battery-charging*/battery-bluetooth* MDI variant, so it lines up with that
icon's own glyph instead of assuming a plain mdi:battery. See
icon_animation. Displaying a real progress percentage for these appliances
(Home Connect, Miele) has its own recipe under max_value.
🎨 More built-in themes¶
Beyond the existing presets, 1.6.0 adds a family of generic threshold themes
— critical_when_low, critical_when_high, critical_when_extreme — for
anything where only the low end, the high end, or both extremes are a problem
(battery / free disk space, CPU/RAM usage, tank levels, deviation from a
setpoint…). There's also a virtual battery_adaptive theme that switches on
its own between critical_when_extreme while charging (li-ion batteries age
faster held at 100%, so the safe zone is the 30–70% middle) and
critical_when_low once unplugged — reusing the same charging detection
icon_animation: battery_charging relies on, with no extra entity to configure.
And a new light theme rounds things out, with its own palette and a lightbulb
icon that brightens as the value climbs. See the Theme Guide.
🚨 Get alerted at a glance¶
Have the card call for attention when a value crosses a limit — a pulsing border
or a tinted background, in the color of your choice, with a static / blink /
ping animation. The threshold itself can be a fixed number, another entity, or
a template. See alert_when.
➡️ alert_when Function #120 (@AndyDann)
📉 Dynamic min & max¶
The bar's range no longer has to be fixed numbers: min and max can each follow another entity or a template. See min_value / max_value.
🎯 Center the bar on any value¶
center_zero can now center the bar on a nominal value other than 0, and
display the deviation as a percentage. See center_zero.
➡️ [Feature]: Add a possibility to set a zero value #115 (@aremishevsky)
💧 Simpler watermarks¶
Set low/high thresholds directly in the sensor's own unit, follow a template
like min/max, or point them at another entity — using the same
{ entity, attribute } shape as min_value/max_value, rather than a bare
entity id paired with a separate attribute key. See watermark.
➡️ [Enhancement]: Support number entities for watermark low/high values #111 (@Gunth, @GauthierDumont)
📈 Logarithmic bar scale¶
bar_scale: log maps the value to the bar's width on a log scale instead of
linear, for sensors spanning several orders of magnitude. See bar_scale.
🫥 Hide elements dynamically¶
hide now also accepts a template, so parts of the card can appear and
disappear based on conditions. See hide.
➡️ [Feature]: Allow dynamically hiding/showing the progress bar #112 (amaurylam)
📐 Better layouts¶
- Overlay mode (text on the bar) looks much better, especially on vertical cards.
- New
backgroundposition: the bar fills the whole card. - The card automatically matches your theme's corner roundness.
📝 Two-line secondary info¶
Add multiline: true and insert a <br> in custom_info (or secondary on
Template cards) to split it across two lines instead of one — name and progress
bar layout stay untouched. See multiline.
🎨 A friendlier visual editor¶
Almost every option can now be configured without touching YAML:
- clear mode chips for min/max values (Fixed value / Entity / Template),
- custom color zones (
custom_theme) — previously YAML-only — now have their own row editor, with a chip switch between Preset and Custom theme, - an Interactions panel that shows what the default action actually is, and keeps rarely-used actions out of the way until you need them,
- a more native Home Assistant look & feel throughout.
🩺 Something wrong? Ask the card¶
Run EPB_DIAG.dump() in your browser console: it prints everything useful for a
bug report (versions, browser, common installation problems) — and it even
detects on its own whether the card is accidentally installed twice.
🧪 Try it: demo dashboard¶
Import docs/demo-dashboard.yaml and move the sliders to
see the features live.
♿ Accessibility¶
The card now exposes its progress bar using proper ARIA attributes, while decorative elements are hidden from assistive technologies. Screen readers can navigate directly to the card and announce progress values correctly.
🌐 New Languages¶
This release adds eleven new languages: ca, es-419, et, hu, lt, lv, pt-BR, sk, sl, zh-Hans, and zh-Hant — contributions welcome!
🛡️ Fixes¶
Compatible with Home Assistant 2026.2+. The notable fixes over 1.5.2:
- No more crashes with unusual entities (template sensors without an ID, timers restoring after a Home Assistant restart, sensors with odd units, timers longer than 24 h…) — the card shows a clear message instead of a red error screen.
- Tapping a card no longer fires its action twice after navigating between views.
- Badge icon and color no longer flicker during state changes.
- A
fanon a dynamic preset (e.g.auto) showed the same grey color as a stopped fan — the default color now follows the entity's actual state instead of its percentage attribute, which a fan can report as0while genuinely on. - Trend arrows no longer get stuck on template cards.
- A timer card with a watermark configured used to freeze entirely, the bar never updating — the combination now works.
center_zerowith nomin_valueset used to leave the negative half with no range at all — nothing could ever show there. It now defaultsmin_valueto-max_valueautomatically.
➡️ [Bug]: wrong watermark positions in center_zero mode #114 (@aremishevsky)- Ripple effect on template cards.
➡️ [Bug]: Ripple effect for hover and tap animations doesn't work on the template card. #110 (@WarC0zes) - Color mappings updated for the built-in themes.
➡️ Merge pull request #116 (@vemboy200) - The card respects your number format setting (e.g. Swiss format).
- Noticeably faster and lighter on dashboards with many cards.
- Text formatting from templates keeps working, but scripts can no longer be injected through entity names or media titles (see Supported HTML).
- Badge
min_widthgiven as a percentage no longer overflows and overlaps neighbouring badges — on a badge,%is now relative to the badge's default width (120%= 1.2× the normal size). Cards and templates keep the standard CSS%. (Existing badge%values change meaning — they rendered broken before.)
➡️ [Bug]: Bug with minimum width #124 (@vemboy200) - Changing a sensor's display precision now updates the card immediately, instead of only taking effect after a full browser reload.
- The card now loads correctly even when its resource is registered as a classic
"JavaScript" type instead of "JavaScript Module". That deprecated type
could stop the card from loading and freeze pop-ups opened by browser_mod; the
card is now safe either way, and prints a console warning when it detects the
classic type so you can switch it to "JavaScript Module".
➡️ [Bug]: freeze on webawesome / browser_mod pop-ups #108 (@LiMEntal)
🧹 Under the hood¶
- The redundant "(overlay)" hint was dropped from several option labels
(
bar_orientation: up,bar_single_line,text_shadow,bar_position: top/bottom) across all 39 languages — the editor already only shows them in the relevant context. - The editor gained two more panels — "Markers & Alerts" (watermark + alert_when) and "Layout & Sizing" (frameless / marginless / height / min_width / layout) — carved out of "Look & Feel", which had grown to hold most of the card's options. Collapsing an unrelated panel now actually skips re-evaluating its fields on every keystroke, instead of the whole editor re-walking every field regardless of which panel is open — noticeably snappier on large configs.
- The single-file
entity-progress-card.jsmonolith is gone. The card is now built from a proper module tree undersrc/(utils/card/editor) and assembled byscripts/build.js(esbuild bundle + CSS-in-JS minification) into the same shipped output — no behavior change intended; card/badge/feature registration and the console banner are unchanged. src/is now TypeScript, which caught a handful of latent bugs at compile time before they could ever ship.- The release process is sturdier: a
build:prodmode that forces every dev/debug flag off regardless of source state (guarded bynpm run check:release-flags), auto-formatting and linting on every commit (Prettier + a pre-commit hook), and HACS distribution served purely from the tagged release asset — the same pattern larger HACS plugins use.
Thanks to everyone who reported, tested and contributed 🙏
➡️ Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.5.2...1.6.0
1.5.2¶
What's new¶
A lot has changed under the hood — and on the surface. From a fully WebAwesome-compatible editor to live watermarks, smoother animations, and cleaner docs, this release makes the card feel right at home in any Home Assistant setup.
I would have loved to include more features in this release, but the WebAwesome migration forced me to prioritize and ship this update sooner than originally planned.
🧩 WebAwesome Compatibility¶
Starting with HA 2026.2.x, Home Assistant introduced significant changes as part of the migration to Webawesome. With 2026.3.x, the select component in the visual editor is broken — options can no longer be selected. Cards/badges are not affected by this Home Assistant update. The visual editor has been updated to use the latest Home Assistant UI components, fully compatible with the new WebAwesome framework introduced in recent HA versions.
What this means for you:
- The editor now looks and feels consistent with the rest of Home Assistant's UI
- Fields respond correctly to your HA theme (light/dark mode, accent colors)
- Full compatibility with both the old and new HA frontend architecture
➡️ [Bug]: Cannot select a theme from the dropdown #109 (@Ascathon)
⚡ Faster Tap Response¶
Immediate action on single tap ! Previously, every tap was delayed by 300ms to wait for a potential double tap — even when no double_tap_action was configured. This caused a noticeable lag when opening more-info or triggering any tap action. The card now detects at startup whether a double tap action is configured. If not, tap actions fire immediately with no delay, matching the responsiveness of native HA cards.
✨ Smoother Interactions¶
Better click & tap feedback: The card now uses Home Assistant's native ripple effect for hover and tap animations.
The effect can be disabled with card_mod:
card_mod:
style: |
ha-ripple {
display: none;
}
➡️ [Feature]: Make the hover effect configurable to be able to deactivate #102 (@RkcCorian, @WarC0zes)
🎨 Smooth Color Transitions¶
New interpolate option for custom themes: When using a custom_theme, you can
now enable smooth color transitions between steps. Instead of jumping abruptly
from one color to the next, the icon and progress bar will gradually blend from
one color to the other as the value changes.
➡️ [Enhancement]: Smooth color interpolation between custom_theme ranges #96 (@diegocjorge)
✨ New Bar Effects: shimmer_reverse and gradient_reverse¶
Two new visual effects are now available as companions to the existing shimmer
and gradient effects.
shimmer_reverse— same shimmering animation as shimmer, but running in the opposite direction.gradient_reverse— same color gradient as gradient, but fading in the opposite direction.
These new effects are independent from bar_orientation — you can combine them
freely to achieve the exact visual result you want.
💧 Dynamic Watermarks: Compare your entity against another sensor¶
Watermark values (low and high) can now be set to any HA entity instead of a fixed number. This means you can, for example, display your indoor temperature as a progress bar and mark the current outdoor temperature as a reference line — updated live as conditions change.
watermark:
low: sensor.outside_temperature
high: sensor.target_temperature
Optionally, you can read from a specific attribute:
watermark:
low: sensor.weather_station
low_attribute: temperature
➡️ [Enhancement]: Make watermark accept a dynamically updating value. #62 (@YamanKoudmani)
📏 Progress Bar Max Width (bar_max_width)¶
Control the width of your horizontal progress bars ! You can now cap that width to keep bars more compact or visually balanced.
type: custom:entity-progress-card
bar_max_width: 120px
➡️ Discord @RKT62
🛠️ Other improvements¶
-
Fix text ellipsis overflow
-
Refactor bar effect
-
Add Watermark and bar effect on vertical layout and style improvements
➡️ [Feature]: bar position #80 (@NfxGT)
-
Clean space when a text slot is empty, better space management for the badges
➡️ [Bug]: Unable to have secondary info and progres bar at the same time in Template Badge #97 (@peyn)
➡️ [Bug]: Incorrect styling when secondary info hidden from badge #107 (Ascathon)
-
Better police management on overlay layout
➡️ [Bug]: When Bar_position is set to Overlay the overlaid text ends up fuzzy.
99 (@bengy70)¶
-
Better card background color management to avoid issue with "glass" theme
➡️ [Feature]: Make the hover effect configurable to be able to deactivate #102 (@RkcCorian)
-
Better badge lifecycle management
➡️ [Bug]: Badge not cleared #103 (@tieskuh)
-
Fix Temperature theme
➡️ [Bug]: Temperature theme not always applied #105 (@sgofferj)
-
Fix
last_updated/state_contentinformations➡️ [Bug]: last_updated/last_changed is declared unknown in state_content #106 (MatzeKitt)
-
refactor badge styles
🌍 Multilingual support: Easier to contribute¶
All translations have been moved to dedicated JSON files under
./translations/. If you'd like to add a new language or fix an existing
translation, you no longer need to touch any code — just edit or create a simple
JSON file and submit a pull request.
➡️ Want to help translate the card into your language? Check out the
contributing.md guide for instructions.
💥 Breaking change¶
Some users reported fuzzy text in overlay mode caused by theme-related issues (light/dark). In certain cases, the shadow was not helpful and could actually degrade readability.
The text shadow now follows the light/dark theme and is no longer applied by default, giving users full control over this visual effect.
To re-enable the text shadow, add the following to your YAML configuration:
type: custom:entity-progress-card
...
bar_position: overlay
text_shadow: true
📚 Documentation¶
- update documentation
➡️ Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.5.1...1.5.2
1.5.1¶
What's new¶
This release is a quick patch based on user feedback. Version 1.5.0 brought major improvements, and thanks to our testers’ hard work, most issues were caught—but a few minor glitches still slipped through.
- Improved card styling for better integration with built-in Home Assistant cards.
- Fixed background, box-shadow, borders, padding, and margins for a cleaner look.
- Enhanced support for frameless and marginless cards.
- Prevented text overflow in top, bottom, and overlay sections.
- Minor visual tweaks for smoother display in various layouts.
➡️ Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.5.0...1.5.1
1.5.0¶
What's new¶
Better, faster, clearer: new features, enhanced usability, and a full docs overhaul to make setup and customization effortless.
🆕 New Feature¶
- Badge Template: Added
➡️ [Feature]: Entity Progress Badge Template #79 (@Pulpyyyy) -
Progress Bar Positioning
New parameter:bar_positionwith the following options:default: standard positiontop: at the top of the cardbottom: at the bottom of the cardoverlay: overlaid on top of the content
➡️ [Feature]: Add option to show progress bar along bottom (or top) border of card #73 (@Valdorama)
➡️ [Enhancement]: Style for XL bar #76 (@yduke)
➡️ [Feature]: bar position #80 (@NfxGT) (soon!) -
bar_effect: added support forcenter_zero(effect: 'radius', 'glass', 'gradient') -
Single-Line Mode for Overlay Bars
New parameter:bar_single_line(for overlay mode bars only) -
Trend Indicator New parameter: trend_indicator (boolean) Displays trend icons:
- mdi:chevron-up-box: upward trend
- mdi:chevron-down-box: downward trend
- mdi:equal-box: stable trend Automatically positioned at the top right of the card
➡️ [Feature]: trend indicator #82
-
Enhanced validation system added:
- YAML is fully analyzed and failback applyed.
- Many new error messages have been introduced to handle cases such as:
- Missing properties,
- Invalid types (string, number, boolean, array, object),
- Malformed entity IDs,
- Discontinuous or inconsistent ranges (min > max),
- Invalid theme, icon, or state contents,
- Automatic application of default values.
- deprecated parameters: Warn in JavaScript console when using deprecated parameters.
-
Multilingual support: Extended and fixed
- Extended: All new error messages have been translated into over 20
languages, including now
- 🇻🇳 Vietnamese (vi)
- 🇷🇺 Русский (ru)
- 🇹🇭 Thai (th)
- 🇮🇩 Indonesian (id)
- 🇺🇦 Ukrainian (uk)
- 🇮🇳 Hindi (hi)
- 🇨🇿 Czech (cs)
- 🇧🇩 Bengali (bn)
- Fix Small/Medium/Large translation
- Extended: All new error messages have been translated into over 20
languages, including now
- Card Template: Added the
force_circular_backgroundoption in the template
➡️ [Feature]: Add force_circular_background: true in the template card options #83 - Editor: Added new
xlargesize option for the bar. - Accessibility: respects the “Reduce Motion” setting (iOS/macOS, Android, Windows) to limit animations and prevent dizziness, migraines, or distractions.
🎨 Style Improvements¶
Major CSS Refactoring¶
- Complete CSS reorganization: Restructured the entire stylesheet with clear section headers and improved organization
- CSS Custom Properties migration: Converted hardcoded values to CSS custom properties for better maintainability and theming
- Modular approach: Split CSS into logical sections (Base Card, Main Container, Progress Bar, etc.)
Enhanced Layout System¶
- Flexible container system: Introduced variables for dynamic layout control
- Improved vertical/horizontal layouts: Better separation of concerns between orientation-specific styles
- Responsive design improvements: Enhanced responsiveness across different card types and sizes
- Enhanced center_zero support: Improved bar effects (radius, glass, gradient) compatibility with center_zero mode
- Effect rendering: Better handling of gradient and glass effects for both positive and negative progress values
Performance¶
- Optimized CSS: More efficient CSS structure with reduced redundancy
- Better rendering: Improved layout calculations and rendering performance
🐞 Bug Fixes¶
- Fixed [Bug]: icons not loading in the application #86 (@jarzebski)
- Fixed [Bug]: Card shows “Configuration error” when conditionally re-displayed via visibility and input_text helper #87
- Fixed [Bug]: Icon container not found for _showIcon #88 (@golles)
- Fixed duplicate registration error during upgrade: Resolved "Failed to execute 'define' on 'CustomElementRegistry': the name has already been used" by adding existence check before registration
- Improved error handling: Added null safety check to prevent "Cannot read properties of null (reading 'addEventListener')" errors
📚 Documentation¶
- migrate
doc/todocs/ - Improved Navigation:
- New simplified table of contents
- Clearer titles and structure throughout
- Description + Features → Description & features
- All card types (Standard, Template, Badge) now live under one section
- YAML options now shown in smart tables
- Collapsible sections to keep things clean
- Added: 🙏 Credits
- Added: Theme documentation -
docs/theme.md - Added: Full Configuration Reference -
docs/configuration.md- full update with conventions, matrix, description to use it efficiently
- Added: Troubleshooting Guide -
docs/troubleshooting.md - Added: Contributing guide -
docs/contributing.md - Added: Release Candidate Guide -
docs/rc-testing.md - Added: Code of Conduct -
docs/code_of_conduct.md - Update README.md by @jam3sward in https://github.com/francois-le-ko4la/lovelace-entity-progress-card/pull/84
- typo fix: optionnal > optional by @blobberbun in https://github.com/francois-le-ko4la/lovelace-entity-progress-card/pull/90
This docs update dramatically improves usability:
- Easier for newcomers
- More maintainable
- Looks great across all devices
➡️ Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.4.12...1.5.0
1.4.12¶
What's new¶
This release includes support for Jinja templates in bar_effect, bug fixes related to the editor, and several internal refinements to prepare the upcoming 1.5 release.
🆕 New Feature¶
Jinja support for bar_effect (card, badge and template card)
- You can now use Jinja2 templates in the
bar_effectconfiguration. - This allows for dynamic visual effects based on entity states or conditions.
Example:
bar_effect: |-
{% if states(xxx) | float > 22 %}
shimmer, gradient
{% else %}
gradient
{% endif %}
🐞 Bug Fixes¶
- A test was incorrectly adapted during the refactor in version 1.4.11, leading to a bug in the editor UI where the max_value field was not handled properly. This has now been fixed and validated.
🧼 Code Refactoring¶
- Minor refactors around conditional checks and effect rendering functions.
- Prepare the 1.5 version ^^
📚 Documentation¶
- Updated README.md to reflect the new Jinja capability for bar_effect, with usage examples.
- See: https://github.com/francois-le-ko4la/lovelace-entity-progress-card
➡️ Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.4.11...1.4.12
1.4.11¶
What's new¶
🆕 New Features¶
-
Zero Marker (
zeroMark) forzero_centermode
Visually marks the center point (zero) on the progress bar.
Especially useful for cards configured withzero_centerlayout. [Feature]: Centered Zero Point (@Rijswijker) -
Support for
entity_picturein template cards
Template-based cards can now properly display entity pictures, improving customization and context. [Feature]: Add entity picture option (@WarC0zes) -
Enhanced Jinja templating support
The Jinja rendering context now includesentityautomatically.
Icon rendering via Jinja is more robust with improved error fallback on first load. [Feature]: template card; add entity variable (@golles)
🎨 UI/UX Improvements¶
-
CSS refactor using
:is(...)and cleanup
Simplified and maintainable CSS with better browser compatibility and fewer redundant selectors. -
Unified progress bar sizing
-
Improved layout behavior
Better alignment and spacing in both vertical and horizontal orientations.
Enhanced readability in compact or dynamic configurations.
🐞 Bug Fixes¶
-
Fixed graphical glitches in certain layouts or edge cases. [Bug]: Bar Effect: Radius, doesnt apply to lower corner on small and medium bar size (@Duncan1106)
-
Resolved icon rendering issues with some template-based entities. [Bug]: Icon - Priority of entity icon higher than specified onebug (@nicknol)
-
Removed unused or outdated visibility-related styles.
-
Fixed fallback behavior when a Jinja-rendered icon is invalid or missing.
📚 README Updates¶
- Content Updated
➡️ Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.4.10...1.4.11
1.4.10¶
What's new¶
This version introduces numerous visual, technical, and functional improvements for greater display flexibility and enhanced stability.
✅ New Features¶
- Progress Bar XL Size A new parameter value (
bar_size= xlarge) for the progress bar provides enhanced visual clarity. ➡️ The progress bar can now be displayed below the main content, especially in horizontal layout. ➡️ The card automatically adjusts its size to fit this new layout seamlessly.
🛠 Improvements¶
center_zeroEnhancement Whencenter_zerois enabled, the defaultmin_valueis now-100, offering a clearer and more intuitive display.- Icon Support Improved rendering of entity icons and support for custom images. [Bug]: Icon - Priority of entity icon higher than specified onebug (@nicknol)
- Data Handling Better compatibility with various data types (string, number, etc.) for more robust configuration.
- Design & Responsiveness ➡️ Smoother and more adaptive layouts, especially in vertical orientation. ➡️ Refactored for greater flexibility and future-proofing.
- Code Optimization Cleaner structure, reusable utilities, and improved maintainability.
🐞 Fixes¶
- Card Height Fixed an issue where the card height didn’t adjust correctly due to a CSS typo.
- Badge Resolved visual glitches in the badge editor preview and badge rendering.
- WebSocket to restart update process Improved initialization and management for enhanced stability.
📚 README Updates¶
- Content Updated — refreshed documentation on
bar_sizeandmin_value -
Update browser compatibility matrix [Bug]: Chrome WebView 92.0.4515.105 on Android 10 ReferenceError: structuredClone is not defined (@WarC0zes)
Platform Browsers 




Home Assistant Chrome Edge Firefox Safari Opera 2024.0+98+98+94+15.4+84+
➡️ Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.4.9...1.4.10
1.4.9¶
What's new¶
This nightly update brings useful improvements and important fixes to enhance stability and customization.
✨ Improvements¶
- height: added. Sets the height (e.g., 120px, 10em, 30%) for the card. Useful for ensuring consistent layout in horizontal stacks or grids.
🐞 Bug Fixes¶
- Fix warning on Chrome: mouse event / passive: true
- [Bug]: Secondary info cannot be a sensor value (@vogtmh)
- [Bug]: disable_unit: true messing up custom theme (@nicknol)
- [Enhancement]: Changing the height of the card (@DaN660)
- [Bug]: blank dashboardbug (@Cptkex82, @awlobo, @vogtmh)
Thank you @mooseBringer for your help on discord.
📚 README Updates¶
- Content Updated — refreshed documentation for better clarity and accuracy.
- Reorganized Structure — improved layout for easier navigation and understanding. Update README.md by @Duncan1106 in https://github.com/francois-le-ko4la/lovelace-entity-progress-card/pull/69
🚀 New Contributors¶
- @Duncan1106 made their first contribution in https://github.com/francois-le-ko4la/lovelace-entity-progress-card/pull/69
➡️ Documentation: entity-progress-card GitHub repo ➡️ Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.4.8...1.4.9
1.4.8¶
What's new¶
This update brings a cleaner look, smarter layout options, and more control through new YAML parameters. Small tweaks, big impact—your cards just got more powerful and more flexible.
✨ Improvements¶
- Zero-centered progress bars (card/template) Easily display values that move
around zero—perfect for showing deltas, gains/losses, or directional trends.
Watermarks have been adjusted to support center_zero mode. 🔧 New YAML option:
center_zero📄 [Feature]: Centered Zero Point #50 (@Rijswijker) -
Multiple entities support (card) Group several entities into a single card, complete with auto-totaling and dynamic gradient coloring to visualize each contribution. 🔧 New YAML option:
additions📄 [Enhancement]: Visualization of Total and Partial Values in Single Bar #61 (@jam3sward)- Multiline secondary info (template) Support for line breaks in secondary info using
brtag, letting you display richer, clearer context. 📄 [Enhancement]: Multiline Secondary for entity-progress-card-template #60 (@Duncan1106)- Marginless mode (template/card) Remove vertical padding for a more compact look. 🔧 New YAML option:
marginless📄 [Enhancement]: Changing the height of the card #64 (@DaN660)
🐞 Bug Fixes¶
unit_spacing: regression fixed Units are now correctly spaced next to values again.- Custom minimum width (template/card/badge) Set a minimum card width to ensure
consistent layouts. 🔧 New YAML option:
min_width📄 [Bug]: hiding the name hides the bar #63 (@dougyip) - 💅 Minor CSS refinements for better alignment in vertical layouts.
➡️ Documentation:
entity-progress-card GitHub repo
➡️
Full Changelog:
https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.4.7...1.4.8
1.4.7¶
What's new¶
🌈 New Visual Effects for Progress Bars¶
outer border-radius¶
Normalized outer border-radius based on component size (small, medium, large).
Visual Styles for Progress Fill¶
You can now customize the look of the progress bar using new visual styles:
radius– rounded cornersglass– frosted glass effectgradient– soft color gradientsshimmer– animated shimmering
👉 Enable with the new bar_effect option.
➡️ Documentation:
the bar_effect docs
💧 Redesigned Watermarks¶
New watermark types provide more visual flexibility:
blended(default): A subtle colored overlay that merges with the bar’s colors for a more integrated look.area: A soft transparent shape placed over the bar, without blending into the bar's colors.striped: Diagonal stripes for a patterned effect.triangle: Triangle shapes as a watermark.round: Rounded shapes applied as a watermark.line: Vertical lines pattern (like a hatch effect).
👉 Cleaner and more dynamic rendering.
👉 Request:
➡️ Documentation: the watermark docs
🧩 Technical Improvements¶
🏗 Full Refactor¶
- Modular rewrite for both cards and badges
- New config system with automatic validation
⚙️ Better Maintainability¶
- Reduced code duplication
- Dynamic CSS class handling for flexibility
- Foundation laid for future features
🔧 Migration Notes¶
No changes required to existing configurations.
To use new effects, add this to your card config:
type: 'custom:entity-progress-card'
entity: sensor.battery_level
bar_effect:
- shimmer
- radius
➡️ Documentation:
entity-progress-card GitHub repo
➡️
Full Changelog:
https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.4.6...1.4.7
1.4.6¶
What's new¶
🎨 Editor Improvements¶
- Cleaned the editor logic with proper separation of rendering methods.
- Improved accordion sections animation
- Improved behavior of toggle switches and dynamic
hidelogic in the config editor.
🏷️ Badge Component¶
- Standardized dimensions (width/height),
- Improved icon and text alignment,
- Better visual consistency in compact layouts.
🐞 Bug Fixes¶
-
56 Text on Badge is nearly unreadable (@sphings79)¶
- Resolved potential duplicate event listener issues in the editor.
➡️ Documentation:
entity-progress-card GitHub repo
➡️
Full Changelog:
https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.4.5...1.4.6
1.4.5¶
What's new¶
🚀 Improvements¶
🎨 entity-progress-card¶
If the entity has an entity_picture attribute then a picture is shown, instead of an icon.
-
55 Allow image instead of icon (@netsoft-ruidias)¶
🎨 entity-progress-card & template¶
reverse_secondary_info_row: added. Reverses the order of the progress bar and
the secondary info when using a horizontal layout.
-
52 add options to display values on right side and adjust font size¶
(@jamesvert)
📖 Extended support for frameless¶
- Enhanced documentation now details compatibility with various card types (entities, vertical-stack, etc.).
- Clearer guidance on when this option needs to be explicitly set.
⚙️ CSS Optimizations¶
- Improved vertical layout handling:
- Adjustments to margins, heights, and alignments.
- Centered and responsive display.
- Renaming from formats like hide_icon → hide-icon for better consistency.
- Refactoring of CSS variables (--epb-*) for improved clarity and customization.
- manage all ellipsis with the same methodology
➡️ Documentation:
entity-progress-card GitHub repo
➡️
Full Changelog:
https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.4.4...1.4.5
1.4.4¶
What's new¶
🚀 Improvements¶
🎨 Enhanced Frameless Mode Integration:
- Better compatibility with
entitiesandvertical-stack-in-cardcards when using frameless mode. - Automatic detection with
entitiescard and aligned look & feel - Shadow has been removed to avoid glitch [Feature]: Add entity_row option - frameless #45
🎨 Major CSS Optimizations
- Complete CSS reorganization
- Enhanced entity support
- Better orientation handling
- Optimized transitions
- Improved accessibility
✏️ Editor Improvements
- Redesigned user interface 💫 with a more modern design
- Centralized CSS variables 🎛️ for easier maintenance
- Bug fixes 🐛 (typo align-item → align-items)
- Better organization 📁 of accordion styles
⚡Performance Optimizations
- Advanced throttling system 🚦 to limit frequent updates
- Enhanced resource management 🔧 with optimized ResourceManager
- Reduced unnecessary re-renders 🎯 through better change tracking
🔄 CI/CD Configuration
- Added GitHub workflow 🔄 for automatic stale issue management
- Automatic closure after 15 days of inactivity with reopening capability ⏰
🐞 Bug Fixes
- [Bug #53] Fixed an issue where custom theme icons were not displaying correctly.
- Improved Jinja processing 🔧 for templates During the copy-paste operation, the embedded template card displayed the Jinja syntax rather than the rendered output.
- Better validation ✅ of configuration fields
- Fixed demo mode handling 🎮
✅ Take away
- Enhanced user experience 😊 in the editor
- Better compatibility 🤝 with different Home Assistant card
- Improved performance 🚀 through throttling and optimized resource management
- Easier maintenance 🔧 with clearer CSS structure
➡️ Documentation:
entity-progress-card GitHub repo
➡️
Full Changelog:
https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.4.3...1.4.4
1.4.3¶
What's new¶
This update brings you more control and clarity under the hood:
- Updated internal code documentation for better clarity and maintainability.
- Changed logging strategy in development mode for enhanced debugging.
🧪 Feature Enhancements
- Performance improvements: finer tracking of state changes before triggering updates. Added a ChangeTracker class to detect and handle changes in the hass state efficiently.
- Reworked theme and color management with a cleaner, more dynamic ThemeManager. Vertical layout icons with hidden icons now support a single-line display. This new feature may cause automatic resizing if your layout is not fixed and you intend to maintain two or more rows without icons. Don't panic! You can adjust your grid setup to your requirements in the card editor. request: @Lemonadel #47
🎨 UI/UX Improvements
- Added structured comments, emoji tags (🛠️, 📦, ✅), and well-documented class sections (// === SECTION ===) to improve readability.
- Improved the configuration editor (EntityProgressCardEditor) with:
- Better event handling
- Clear mapping of editor fields
- Automatic updates and validation
- Introduced demo mode for templates (EntityProgressTemplate), simulating entity values for preview.
🔄 CI/CD Configuration
- Updated the release.yaml workflow to:
- Automatically clean up .js files from logger/debug-related patterns.
- Enforce code style (e.g., removing trailing spaces).
➡️ Documentation:
entity-progress-card GitHub repo
➡️
Full Changelog:
https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.4.2...1.4.3
1.4.2¶
What's new¶
Transform your dashboard experience with the latest Entity Progress Card – where beautiful design meets powerful functionality, giving you the tools to create interfaces that truly reflect your vision.
🎯 New "Badge" Mode¶
A more compact version of the card is now available: perfect for badge-style views (e.g., in previews or condensed dashboards). It displays key information in a smaller, cleaner format.
- request: @peyn #43
- Documentation: the entity-progress-badge docs
🖼 "Frameless" Option¶
frameless: added You can now enable a frameless mode without borders and background (frameless) for even smoother integration into your existing card.- request: @davidlb #45
- Documentation: the frameless docs
🎨 Extended Color Customization¶
Custom themes can now handle separately: added
- icon color (icon_color)
- progress bar color (bar_color)
- background color (color)
- request: @LeCreepyboy #49
- Documentation: the custom_theme docs
💅 Visual Improvements
- Better color management with transparency support
- Icon is now better positioned and more visible
- Shrink card if icon is hidden and layout is vertical
- request: @Lemonadel #47
⚙️ Performance and Reliability
- Faster and smoother rendering thanks to optimized DOM management
- Better compatibility with Home Assistant dynamic updates
- Improved error handling (standard error + network)
- bug: @mooseBringer #48
To enjoy all these new features, remember to clear your browser cache if necessary after the update. Need help or a configuration example? Check out the updated documentation or ask questions!
➡️ Documentation:
entity-progress-card GitHub repo
➡️
Full Changelog:
https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.4.1...1.4.2
1.4.1¶
What's New¶
We're excited to roll out a new update for the Entity Progress Card Template, continuing our mission to make your dashboards more flexible, expressive, and visually refined.
🌈 Improvements¶
This release brings several key enhancements:
- Improved display in the card gallery Your card now integrates more smoothly into the card selector interface, with a cleaner, more informative preview.
-
New standard parameters support We’ve introduced additional layout and style customization options to better fit your UI needs:
Variable Description bar_orientation Define the direction of the progress bar (e.g., ltr, rtl) bar_size Customize the size or thickness of the progress bar layout Adjust the overall layout (e.g., horizontal, vertical)
Stay inspired, and keep building ✨
➡️ Documentation:
entity-progress-card GitHub repo
➡️
Full Changelog:
https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.4.0...1.4.1
1.4.0¶
What's new¶
🆕 New Card: Entity Progress Card Template
We’re excited to introduce a powerful new addition to our card library: the Entity Progress Card Template.
This card is designed to handle more advanced use cases that aren't fully supported by the base card. It avoids the need for custom helpers by allowing you to implement your desired mathematical modeling directly through templating.
🧠 Why Use This Card?
This card is ideal for situations where:
- You want to show calculated progress (e.g., level, usage, battery life)
- You need to apply dynamic logic or math modeling directly in the card
- The base card doesn't offer the required level of customization
➡️ Documentation:
the entity-progress-card-template docs
➡️
Full Changelog:
https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.3.14...1.4.0
1.3.14¶
What's new¶
Small improvements to prepare the future.
- Code optimizations across the application.
- Fixed a side effect introduced by a previous optimization that affected select fields.
- Preparation for version 1.4 to support upcoming changes.
1.3.13¶
What's new¶
Some users have reported issues with toggle components not behaving as expected in certain cases.
🔧 update to enhance the stability and reliability of toggle functionality across the interface. 🔧 reduce DOM update during YAML edit
This improvement addresses inconsistencies and ensures a smoother, more predictable user experience.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.3.12...1.3.13
1.3.12¶
What's new¶
min_value Strikes Back
Turns out, min_value went undercover due to a sneaky little typo. It almost
got away with it too—until we caught it red-handed in the middle of a bug
report.
Apologies to anyone who tried to set a minimum value and got a maximum headache instead.
1.3.11¶
What's new¶
🛠️ Bug Fix
- Default Icon Handling: Fixed an issue where, in certain cases, the displayed icon no longer matched the entity when its state changed.
- Default name Handling
- Minification
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.3.10...1.3.11
1.3.10¶
What's new – Clicks Under Control¶
This patch release fixes the click chaos introduced in 1.3.8. Turns out, one misbehaving variable caused a few taps to go on strike.
🐛 What was broken in 1.3.8/1.3.9¶
icon holddidn’t hold upicon double tapdouble-failed- regular
double tapgot confused
All thanks to a variable that thought it was smarter than it really was.
🔧 What’s fixed¶
- Corrected the logic to properly fallback to the card-level action when icon
actions are set to
noneor not defined.
🕵️♂️ Special thanks¶
Big thanks to @Duncan1106 for catching the
issue
before it spiraled further.
My tests clearly need a caffeine upgrade. ☕
Back to clicking with confidence!
1.3.9¶
What's new¶
Crafted, tested, tuned, and rethought...
🔢 Improved Attribute Handling¶
Better support for attributes containing numeric values, including strings that represent value.
🛠️ Accordion (Editor) – Smoother Animation¶
Refined animation behavior with adjusted speed and removal of visual glitches.
📚 Documentation Update¶
Updated final card for the advanced guide: “Cracking a Complex Case with a Simple Helper.”
⚙️ General Optimization¶
Code cleanup and performance improvements.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.3.8...1.3.9
1.3.8¶
What's new¶
Bringing clarity, consistency, and control — this update refines the experience from card display to editor behavior, introduces smarter defaults, and empowers developers with targeted debugging tools. Let’s dive into what’s new.
🚀 Features & Improvements¶
- 🗺️ Card
- Ellipsis: fixed only one ellipsis is now displayed in the information section.
- Font / Font Size: uses global variables to ensure consistent styling across the interface.
- 🛠️ Editor
- GUI Update from YAML: fixed deletions made in YAML are now correctly reflected when switching to the graphical editor.
- Attribute Selection: disabled for Counter, Number, Timer, and Duration entities.
- YAML to entity-progress-card Conversion: fixed no more errors, and the graphical editor is correctly generated.
- Accordion: improved more natural opening behavior.
- 🔢 Number: added added support for number value.
- 📈 max_value: Improved now properly supports Counter, Number, and Duration entities.
- 🎯 xyz_action: defaults added
- tap_action:
more-info - hold_action:
none - double_tap_action:
none - icon_tap_action:
toggleif the entity is alight,switch,fan,input_boolean, ormedia_playernoneotherwise
- icon_hold_action:
none - icon_double_tap_action:
none
- tap_action:
📚 Documentation¶
- Added new section: "Percentage Calculation"
- Added advanced example: Don't Let It Expire!
- Added new section: "Token Color"
- Simplified option descriptions
- Standardized typing using Home Assistant conventions
- Replaced color definitions with token color
- Minor cosmetic adjustments
⚙️ Optimization¶
- More robust handling of default values
- More reliable editor updates
- Debug mode: can be selectively enabled for card, editor, or resource manager
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.3.7...1.3.8
1.3.7¶
What's new¶
This release focuses on improving visual consistency, usability, and performance, with better icon support, refined animations, enhanced configuration handling, and updated documentation.
🚀 Features & Improvements¶
-
Entity Icon Handling
- Improved icon retrieval: certain MDI icons previously not displayed correctly are now fully supported when defined in Home Assistant.
- Enhanced clickable area: better interaction zone around the icon.
-
decimal Handling Anticipates formatting needs without requiring manual configuration.
-
Editor: Accordion Animation Refined animation for a smoother and more natural transition.
-
Editor: Select Fields
Fixed display and behavior of select fields in the card editor.
⚙️ Optimization¶
- Simplified internal icon handling logic.
- Improved code syntax for better readability and maintainability.
- Removed unused variables.
- Optimized conditional checks for performance.
📚 Documentation¶
- Updated content to reflect recent changes and improvements.
- Refreshed screenshots to match the latest UI and features.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.3.6...1.3.7
1.3.6¶
What's new¶
We’ve added a new configuration option: unit_spacing, allowing you to control the presence of a space between numeric values and their units (e.g., %, °C, €, etc.).
This enhancement gives users more flexibility and control over how numeric units are formatted — whether you want to follow locale standards or override them explicitly.
unit_spacing: 'auto' | 'space' | 'no-space'
auto(default) — Automatically applies the correct spacing based on the user’s locale (e.g., 80 % in French, 80% in English-US).space— Always adds a space between number and unit (e.g., 80 %), regardless of locale.no-space— Always removes the space (e.g., 80%), even if the locale normally includes it.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.3.5...1.3.6
1.3.5¶
What's new¶
🌱 A Fresh Breath for a Growing Card
As this card continues to evolve and gain more features, it became clear that a bit of housekeeping was long overdue. With every added function, keeping the codebase clean, efficient, and aligned with Home Assistant standards is essential—not just for performance, but for maintainability and user experience. This release is a step in that direction.
🧾 Improved Unit Formatting¶
The separator between the value and its unit now uses a standard space instead of a non-breaking space, aligning the display behavior with Home Assistant’s native cards for a more consistent look.
🧩 Refined Accordion Effect¶
The accordion animation and behavior have been optimized for a smoother, more polished interaction experience.
🧹 Code Quality Boost (ESLint + DeepSource)¶
- Function Splitting & Performance Optimization A function that had grown too complex over time was split into smaller, more manageable parts. This structural change not only improves current performance but also lays a safer foundation for future releases.
- Significant code clean-up and optimization have been carried out. To maintain a high-quality codebase, we use ESLint locally during development and we've integrated DeepSource for static analysis. DeepSource now performs an additional validation step upon each commit, helping prevent bugs before any release process begins.
1.3.4¶
What's new¶
This release focuses on performance refinement and intelligent memory management, making your interface lighter, faster, and more responsive. With an internal resource manager now steering the card's behavior, we aim to future-proof its evolution while keeping it lean.
🚀 Improvements¶
-
Memory Optimization – Enhanced The progressive addition of new concepts now requires a dedicated internal resource manager. This change significantly optimizes how resources are handled, resulting in better performance and lower memory usage.
-
Icon Detection – Smarter Automatic icon selection has been improved for several device classes:
curtain,blind,garage,gate,shutter,window,door,shade, anddamper. These now visually reflect their real-world state with greater accuracy.
🐞 Bug Fixes¶
-
Precision Regression – Fixed Addressed a regression that affected the accuracy of displayed values.
-
Color Handling – Resolved Fixed a bug causing incorrect color rendering in certain states.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.3.3...1.3.4
1.3.3¶
What's new ?¶
A smarter, more human, and more intuitive card.
This version marks a major step toward a card that’s easier to configure, more aligned with Home Assistant standards, and richer in features. We worked to make it "speak your language" — less manual setup, more intelligence by default, and an ever-stronger attention to detail.
Thank you all for your feedback and support! 🚀
🔥 New Features¶
-
state_content: Added- Allows you to add Home Assistant attributes before the main value directly through a simple YAML description.
- Complements the
custom_infofield by offering a quick, native method.
-
Duration: Added
- Displays durations in a human-readable format, e.g., 3h 4min instead of 11,040s. (@mill1000 feature request #33)
-
Unit Typography : Fixed
- Automatically adds the correct typographic space between the value and unit (5 s instead of 5s).
- Respects local conventions according to Home Assistant's language settings. If you notice any issues, please let us know via Discord or GitHub!
🔄 Improvements¶
- Hide
- Added the ability to hide both the value and the unit when
state_contentorcustom_infois enough. - Enables customized displays without redundancy.
- Added the ability to hide both the value and the unit when
- Timer
- Default behavior updated to avoid manual configuration:
- Reverse countdown (
reverse= true) is now the default to match the "Tile" style. - Progress bar orientation is now RTL (right-to-left) by default.
- Reverse countdown (
- Default behavior updated to avoid manual configuration:
- Unit
- Unit detection improved:
- Counter:
unitdisabled by default to avoid unnecessary clutter. - Duration: support for timer and flexTimer. (@mill1000 feature request #33)
- Timer: now displays by default in flexTimer, with an inactive state instead of showing 0 s.
- Counter:
- Unit detection improved:
- Error Messages
- Lighter DOM by default for better performance.
- Home Assistant color codes are now used for visual consistency.
📚 Documentation¶
- Added all the new parameters (state_content, etc.).
- New advanced guide: "Washing Machine example" (@erikgeurts) to show how to use it with multiple entities.
- Clarified unit management between automatic and manual modes.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.3.2...1.3.3
1.3.2¶
What's new¶
“Details matter. It’s not just what it looks like and feels like. Design is how it works.” – Steve Jobs
This release focuses on giving you more control over the look of your card and flexibility in how your data is presented — all while keeping the card clean and intuitive.
🎨 Color Parameter Support¶
You can now customize the bar's background color using theme-aware color variables:
--epb-progress-bar-background-color
This allows for:
- Deeper theme integration
- Better readability with custom Theme
- More consistent appearance across your dashboard
🏷️ name_option Parameter¶
A new name_option parameter is introduced to control how the entity name
is rendered. It’s ideal for:
- Appending dynamic context via Jinja
- Displaying a more descriptive label
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.3.1...1.3.2
1.3.1¶
What's new¶
Small details make great experiences.
The badge option has been split into two distinct and more flexible parameters:
badge_icon– Defines the icon to display (e.g. mdi:battery), supports Jinja templating.badge_color– Controls the background and icon color, also supports Jinja and CSS color values.
This change brings the configuration closer to the standard used by cards like Mushroom Template, ensuring more consistency and customization freedom.
✅ You can now:
- Dynamically adjust the icon based on entity state
- Define custom background/icon colors for better visual feedback
Example:
badge_icon: >-
{% if is_state('binary_sensor.piglet_charging','on') %}
mdi:battery-charging
{% endif %}
badge_color: >-
{% if is_state('binary_sensor.piglet_charging','on') %}
green
{% else %}
gray
{% endif %}
(@erikgeurts feature request #26)
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.3.0...1.3.1
1.3.0¶
What's new¶
Express More, With Less Effort !
As this card continues to evolve, the mission remains the same: simplicity first, flexibility when you need it. With version 1.3.0 and beyond, we’ve opened the door to greater expressiveness—without sacrificing ease of use.
🚀 This release introduces new capabilities designed to offer more control and customization right where you need it most: the visual layer.
✨ Say hello to:
disable_lowanddisable_highfor watermarks (@erikgeurts feature request #31)- The
custom_infooption for dynamic inline text (@pterisaur feature request #25) - The
badgeoption for icon overlays driven by real-time state (@erikgeurts feature request #26)
These new options empower you to present context-sensitive data beautifully and meaningfully, while keeping your card configuration clean.
🙏 Big shoutout to everyone dropping feature requests and steady feedback on github/discord — you're the real MVPs making this card smarter, slicker, and better every version! 💪✨ Special thanks to: @meoller, @mill1000, @Ascathon, @harmonie-durrant, @nortuzar, @Jezza34000, @hanfreakingsolo, @Duncan1106, @pterisaur, @ond000, @meirlo, @afkdk, @c4weddell, @saya6k, @erikgeurts, @FrankJaco, @ripvega, @poiromaniax 🙌
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.2.8...1.3.0
1.2.8¶
What's new ?¶
🚀 Features & Improvements¶
- 🎨 Improved color blending for watermark overlays (@erikgeurts feature request #28) Enhanced visual mix between the progress bar and watermark zones for better clarity and aesthetics.
- 🧩 Added "simple line" style for watermark (@erikgeurts feature request #28) New visual option to display threshold zones using clean vertical lines.
🐛 Bug Fixes¶
- 🔧 Fixed attribute handling logic (@hanfreakingsolo issue #30) Corrected an issue where non-numeric attributes could interfere with rendering or calculations.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.2.7...1.2.8
1.2.7¶
What's new ?¶
Watermark¶
The entity-progress-card just got smarter with a new update to the
watermark feature! 🎉
You can now define low and high watermark thresholds using either:
- ✅ Absolute values (e.g., 3.7 for volts)
- ✅ Percentages (e.g., 20%)
Thanks to automatic unit detection, the card intelligently interprets your thresholds depending on the entity’s native unit.
- If the entity unit is V or °C, absolute values like 3.7 will be interpreted directly.
- If you use a %, it’ll be treated as a percentage of 0–100.
This makes the card way more flexible:
- 🔋 For battery sensors, use percentages (20%, 80%)
- 🌡️ For temperatures or voltages, use real-world values (18°C, 3.7V, etc.)
📦 This update enhances readability and customization while keeping your config intuitive and powerful.
🧹 Bonus: Cleaner Build for Production¶
The build process now automatically removes debug calls that aren't used & needed in production, making the file lighter and cleaner.
Enjoy the boost! 🚀💚
(@erikgeurts feature request #28)
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.2.6...1.2.7
1.2.6¶
What's changed ?¶
We're excited to introduce watermark support in entity-progress-card!
This feature adds visual threshold indicators directly into the progress
bar, making it easier to understand when a value is outside of a recommended
range.
🔧 YAML Configuration¶
watermark:
high: 80
high_color: red
low: 10
low_color: yellow
🧩 What it does¶
- 🎯 Highlights the low zone (e.g., <10%) and high zone (e.g., >80%) directly on the bar.
- 🎨 Fully customizable colors for each zone.
- ✨ Brings visual awareness to optimal operating ranges — especially useful for batteries, sensors, and more.
✅ Example Use Case¶
For a battery:
- 🔻 Under 10%: background turns yellow → needs charging!
- 🔺 Over 80%: red overlay → avoid charging further to preserve battery health.
This makes it super clear where the value stands at a glance!
(@afkdk feature request #21)
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.2.5...1.2.6
1.2.5¶
What's changed ?¶
Full Support for All User Actions on Cards 🎉
We're excited to announce that in this update, all user actions on cards are now fully supported! 🥳 Every possible interaction is covered, offering complete flexibility to customize card behaviors to fit your needs. Here’s a quick overview of the actions now fully available:
tap_action: 🎯 Defines the action when a user taps the card. Perfect for quick interactions!double_tap_action: 👆 Double tap for a distinct action, allowing for even more interaction possibilities.hold_action: ⏳ Trigger an action when the user holds down on the card. A great way to enable long-press functionality.icon_tap_action: 🌟 Tap the icon on the card to trigger a special action. Customization at your fingertips!icon_double_tap_action: 💥 Double tap the icon to perform a unique action. More options, more fun!icon_hold_action: ✋ Hold the icon to execute an action. For those who like to press and hold!
All these actions can now be configured to do awesome things like:
- Displaying more info 📚
- Navigating to different pages 🚀
- Executing custom commands ⚡️ ...
This update boosts the customizability and rich interactions of your cards, so you can personalize your experience like never before! 🔧🔮
(@Duncan1106 feature request #27)
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.2.4...1.2.5
1.2.4¶
What's changed ?¶
This patch fixes an issue affecting the icon_tap_action behavior in the previous version.
🐞 Bug Fix: icon_tap_action Handling (@Duncan1106 issue #27) The previous version only triggered the more-info action, regardless of the configured icon_tap_action. Despite thorough testing, this bug slipped through and went unnoticed until now. It has been fully resolved, and custom tap actions are now handled as expected.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.2.3...1.2.4
1.2.3¶
What's changed ?¶
We’re excited to announce a new release focused on code quality improvements and enhanced user interaction. This update marks an important step toward industrializing the package for more efficient distribution and maintenance, while also improving usability.
🏭 Package Industrialization¶
- Code Minification: The source code is now minified, resulting in faster load times and a more optimized deployment.
- Automatic Code Deployment: The latest code is now automatically published, streamlining the release process and reducing the risk of inconsistencies.
🖱️ Mouse Handling Fix¶
- Improved Mouse Support: Enhanced mouse handling logic to better cover a wider range of user interactions and edge cases. (@Duncan1106 issue #27)
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.2.2...1.2.3
1.2.2¶
What's changed ?¶
This release brings significant improvements in interaction customization, visual consistency, and language support. It also aligns with the latest Home Assistant 2025.3 standards while simplifying configuration for both users and developers.
🆕 New Interactions¶
- New interaction options offer more flexibility in how the card responds to
user input:
- hold_action – Defines the behavior when the card is long-pressed. (@meirlo feature request #22)
- icon_tap_action – Defines the behavior when the icon is tapped. (@meirlo feature request #22)
🎨 Look & Feel Enhancements¶
Visual improvements bring the card in line with Home Assistant’s current design standards:
- 🌈 Default use of Home Assistant color names, making them easier to integrate. (@pterisaur feature request #24)
- 🔵 The circular background behavior now matches HA 2025.3's updated visual norms.
- 🌀 force_circular_background – New property that forces a circular icon background, helpful to override Home Assistant's automatic behavior. (@pterisaur feature request #24)
🌍 Language Support¶
Eight new languages have been added to improve accessibility and localization:
- 🇹🇷 Turkish (tr)
- 🇰🇷 Korean (ko)
- 🇸🇦 Arabic (ar)
- 🇨🇳 Chinese (zh)
- 🇯🇵 Japanese (ja)
- 🇬🇷 Greek (el)
- 🇫🇮 Finnish (fi)
- 🇷🇴 Romanian (ro)
📚 Documentation Updates¶
The documentation has been expanded and improved:
- Includes new properties: hold_action, icon_tap_action, and force_circular_background.
- Clear explanations of behavior and configuration options.
- Updated examples and visuals reflecting the new look and features.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.2.1...1.2.2
1.2.1¶
What's changed ?¶
This update introduces several improvements to the card component, enhancing
user interaction, visual design, and integration with Home Assistant's features.
Key improvements include better handling of colors, improved spacing between
components, streamlined code for easier maintenance, and more comprehensive
support for tap_action events. Below is a detailed breakdown of the changes.
🎨 Color & Bar Color: Improved¶
- ✅ Added Reset (✕) button to revert to the default color.
- ✅ Display of current color (live preview).
- ✅ Support for YAML-defined colors: displayed when specified.
- ✅ Improved dropdown placement and size for a smoother user experience. (@erikgeurts issue #20)
📐 Space Between Components: Improved¶
- ✅ Consistent spacing between all components.
- ➕ Enhanced readability and overall layout.
👆 tap_action: Improved & Complete¶
- ✅ Full Home Assistant action support:
- 💡 Proper handling of tap action. (@meirlo feature request #22)
🧹 Unnecessary descriptions: Removed¶
- ✅ Cleaned up the GUI.
- 🔍 Improved readability through clearer and more descriptive labels.
🧹 Code cleanup and improvement¶
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.2.0...1.2.1
1.2.0¶
What's changed ?¶
Please, read this release note before upgrade...
🚀 Important Change: tap_action Replaces navigate_to and show_more_info¶
Why ?¶
This update brings significant improvements (@meirlo
feature request #22),
allowing for:
✅ Better scalability for future enhancements
✅ A more natural user experience, reducing confusion
✅ Easier migration from another card to this one
We have merged the functionalities of navigate_to and show_more_info into
tap_action. As a result, these two options are now deprecated,
disabled, and will no longer be maintained in future updates.
🔄 Impact on Updates¶
This change requires updating any configuration that currently uses
navigate_to or show_more_info to instead use tap_action.
Default behaviors remain unchanged—by default, tap_action will still show
the more_info dialog.
⚠️ To ensure a smooth transition, we recommend updating your configuration
as soon as possible after upgrading.
If you want to keep all features intact, you can add the tap_action parameter
before the upgrade. You’ll find all the necessary details in the README.
This update required a lot of time and testing to make sure you'll enjoy it!
🎉
If you encounter any issues, feel free to open a request on GitHub or join
the Discord community for discussions.
🎨 Theme Management¶
We've improved the decision criteria for selecting the appropriate theme
behavior (based on value or percentage).
This allows for greater flexibility and better coverage of various use
cases—without requiring complex setup! (@ond000
feature request #23)
❓ FAQ¶
Q: Why wasn’t this done from the start? / Why make this change now?¶
Originally, there were fewer features to manage. However, as the card
evolved far beyond my initial expectations, it became clear that a deeper
overhaul was needed.
The complete revamp of the card editor now allows for better functionality
coverage and more efficient configuration management.
Q: What’s the concrete impact if I update?¶
The old configuration parameters are now deprecated and no longer usable
in this version.
The best solution is to use the editor to update your settings easily after
the upgrade or through the YAML editor before the upgrade.
Q: What happens if I don’t update my configuration?¶
If your configuration still contains navigate_to or show_more_info, it will no longer work after this update.
Q: How do I migrate from navigate_to to tap_action?¶
If your previous configuration used:
navigate_to: /lovelace/view
You should replace it with:
tap_action:
action: navigate
navigation_path: /lovelace/view
Check the README for more migration examples!
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.1.11...1.2.0
1.1.11¶
What's changed ?¶
Enhancements
- Field Select Sizing We have adjusted the dimensions of select fields to ensure they have reasonable sizes on screen. This prevents any clipping or overflow, providing a better user experience, especially across various screen resolutions.
Removals
- Removal of "battery", "cpu", and "memory" themes in the graphical editor The "battery", "cpu", and "memory" themes have been removed from the graphical editor. This change helps streamline the interface and eliminates redundant elements that are no longer used in the current version of the product. if you are still using this themes, the card will automatically select the right theme to avoid breaking change.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.1.10...1.1.11
1.1.10¶
What's changed ?¶
🔢 Intelligent Number Formatting
Numbers are displayed based on your regional preferences (@erikgeurts feature request #20), using:
- Your selected language settings (auto)
- Your specific format (manual selection)
- Or the system-defined format from your Home Assistant user profile (system/browser language)
By default, the card uses standard Arabic numerals (0-9) for maximum compatibility.
This modification ensures that all needs are covered.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.1.9...1.1.10
1.1.9¶
What's changed ?¶
This update improves the way numbers are formatted by taking into account both the language and number format preferences set in Home Assistant. Previously, only the language setting was considered, which could lead to inconsistencies in numerical displays.
Now, the system dynamically applies the correct number format based on the user's locale settings, ensuring a more accurate and localized experience. (@erikgeurts feature request #20)
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.1.8...1.1.9
1.1.8¶
What's changed ?¶
We enhanced the efficiency of theming by introducing two generic themes that cover more use cases while simplifying customization. Instead of defining multiple specific themes (e.g., battery, CPU, memory), we now provide with 1.1.7:
optimal_when_low→ Best when values are low (e.g., CPU/memory usage).optimal_when_high→ Best when values are high (e.g., battery charge).
These new parameters allow for a more flexible and scalable way to define themes, reducing redundancy while improving user control over the look and feel of the card. (@erikgeurts feature request #20)
📌 Support for Entities Without a Unit is live now !
In addition to these optimizations, we now extend theme compatibility to entities without a unit of measurement. This means that even entities that do not report a percentage or specific unit can still benefit from the new optimal_when_low and optimal_when_high themes, ensuring broader support across various Home Assistant entities.
✔️ Entities without a unit of measurement (e.g., status indicators, counters). ✔️ Entities where the unit is disabled (giving users more control over their display).
These improvements make the card more adaptable, efficient, and user-friendly while maintaining backward compatibility. 🎨🚀 (@erikgeurts feature request #20)
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.1.7...1.1.8
1.1.7¶
What's changed ?¶
This update focuses on improving the visual customization of the card by introducing new theme parameters. These changes are aimed at providing users with more flexible and generic theme options, making it easier to manage the appearance of the card across different scenarios. By adding these new theme options, we aim to simplify the customization process and offer themes that can cover a broader range of use cases, especially for devices or entities like battery, CPU, and memory.
New Parameters¶
optimal_when_low: A new theme parameter indicating that the optimal state occurs when the value is low (e.g., for memory or CPU usage, where lower values are better).optimal_when_high: A new theme parameter indicating that the optimal state occurs when the value is high (e.g., for battery, where a higher charge is better).
These new parameters replace the previous, more specific themes (e.g.,
battery, cpu, and memory), allowing users to define themes with less
redundancy and more flexibility. (@erikgeurts
feature request #20)
Modifications to the README¶
- Introduction of New Parameters: The README has been updated to reflect the
introduction of the new
optimal_when_lowandoptimal_when_highparameters. These changes were made to improve the explanation of the theme system and highlight the benefits of using these more general parameters. - Updated Example Code: The README now includes updated example code demonstrating how to use the new parameters in the configuration. This makes it easier for users to see how to implement the new themes in their setups.
- Icon Handling Clarification: We clarified that icons are automatically
retrieved from the entity but can be overridden using the
iconparameter. This allows users to customize the icon based on their preferences, providing greater flexibility in the visual presentation.
Deprecations¶
battery,cpu, andmemorythemes: These themes are now deprecated and should no longer be used. While these parameters are still valid, they must be replaced byoptimal_when_loworoptimal_when_highin future implementations.- Reason for Deprecation: The introduction of
optimal_when_lowandoptimal_when_higheliminates the need for multiple, specific theme definitions. These new parameters are more versatile and can handle a wider range of use cases, simplifying the overall theme system.
1.1.6¶
What's changed ?¶
As part of ongoing improvements, several key optimizations and fixes have been implemented to enhance code quality, maintainability, and performance.
- decimal: Improved. Default value for timer is now 0. Because, well… it probably should have been from the start! 😆
- Glitch fixes:
- Standard entity errors (Unknown, Not Found, Unavailable): Handle ellipsis for better readability.
- Parameter errors (max_value, entity required...): Adjust vertical layout
- Code optimization
- Test optimization to secure the code
- Strengthened encapsulation to support future evolution
- Changed tab size from 4 to 2 characters to reduce file size
- Overall cleanup
- README: Updated.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.1.5...1.1.6
1.1.5¶
What's changed ?¶
This update brings several visual and functional enhancements to optimize the user experience and streamline management within the editor. The following changes have been added or improved:
- Cosmetic glitch: Fixed.
- Updated the documentation link to ensure a consistent appearance (light mode).
- Smoothened accordion animation for better transitions.
- Improved element layout when one of the elements is hidden.
- New Editor Features:
hide: Added. This feature allows elements to be hidden within the editor, providing more flexibility in content management.disable_unit: Added. This option enables the disabling of specific units in the editor, offering greater control over the displayed.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.1.4...1.1.5
1.1.4¶
What's changed ?¶
- Auto
attribute/max_value_attribute: Added. The default attribute is now automatically selected based on the defined entity. - Cosmetic glitch: Fixed. Updated the accordion background, color, and border radius for a consistent appearance.
decimal: Fixed (regression). When the decimal value was set to 0, it would not properly override the default HA value. (@Ascathon issue #7)
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.1.3...1.1.4
1.1.3¶
What's changed ?¶
🌟 New Editing Interface with Integrated Accordions
I have completely redesigned the editing card by introducing an accordion system to group options more efficiently and intuitively. 💡 Benefits:
- 📌 Closer to "tile" cards: The appearance and organization are now more consistent with other "tile" style cards.
- ✅ Easier to use: The interface is clearer, and settings are more accessible.
- 📈 Improved scalability: This new system is designed to facilitate adding new options in the future without compromising the user experience.
The code has been entirely rethought and optimized to provide an even more efficient user experience. 🚀
max_value_attribute: Added - (@saya6k feature request #18)attributelist: Fixednull issue: Fixed - (@c4weddell issue #19)
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.1.2...1.1.3
1.1.2¶
What's changed ?¶
We’re rolling out this update to the error messages on the cards to reflect the new style. This change brings a cleaner, more consistent look that aligns with the latest updates in Home Assistant 2025.3. You’ll notice updated error messages for cases like "unavailable," "not found," and "unknown" now presented in a more compliant manner.
- Specific message (decimal error...) remains the same.
- “Unavailable”, “Not Found”, and "Unknown" states follow the design policy.
This is just another step in making your experience with this card more polished and consistent!
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.1.1...1.1.2
1.1.1¶
What's changed ?¶
decimal: Fixed. When the decimal value was set to 0, the Editor did not update correctly and displayed an empty string (''). Additionally, the decimal value was not properly applied to the card.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.1.0...1.1.1
1.1.0¶
What's changed¶
🥳 We are finally moving to version 1.1.0 (about time!) since the core features planned for this card have been developed, and now we're diving into more advanced features and use cases. It also marks the shift to the new Home Assistant 2025.3 look & feel, with support for multiple entities: battery, cover, timer, counter, fan, sensor... basically, if it exists, we probably support it. 😉
Default action:more infonow works by default!Shape: Fixed. Aligned with the shiny new Home Assistant tile policy.Default color/default icon: Improved forbattery,cover,timer,counter,fan,sensor...Default bar color: Matches the default icon color, because consistency is classy.
The result (entity-progress-card / tile):
FAQ¶
- Is there a breaking change? No, none at all. All functionalities remain intact.
- If I update, will my settings be ignored? Nope! I’ve put a lot of effort into refining the default settings. The look has subtly evolved to be more consistent, but everything is still fully customizable through your color/icon settings.
- Great, but if I update, I want my setup to match the example. How can I do that? To match the example, you need to adjust the tap action configuration and set it to the default to enable standard shape handling. If you want to use the default colors/icons, you’ll need to remove your custom settings, allowing the card to decide and then fine-tune based on your needs.
- I actually prefer having the shape all the time. How can I achieve that? According to the new policy, the shape is meant to indicate interaction. For instance, using more_info will ensure the shape is displayed.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.52...1.1.0
1.0.52¶
What's changed¶
From the very beginning of this card, one of the core principles was to align as closely as possible with the look & feel of HA cards. Since the latest HA version 2025.3, there have been numerous valuable changes. One seemingly minor change is the way icon shapes are handled: a shape will now be displayed around the icon if it has a clickable action assigned. To stay aligned with the HA look & feel while maintaining compatibility with previous versions, this update handles the following cases:
- If HA < 2025.3 → No changes
- If HA ≥ 2025.3 → The shape will be visible if you define a click behavior
(
navigate_to,show_more_info).
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.51...1.0.52
1.0.51¶
What's changed¶
- bug fix: fix a null value with unavailable entity
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.50...1.0.51
1.0.50¶
What's Changed¶
disable_unit: Fixed. (@erikgeurts issue #15)
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.49...1.0.50
1.0.49¶
What's Changed¶
disable_unit: Added. (@erikgeurts issue #15)- Disables the display of the unit when set to true. If not defined or set to false, the unit will be shown.
update documentation
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.48...1.0.49
1.0.48¶
What's Changed¶
hide: Added Defines which elements should be hidden in the card. The array can contain any of the following values:- icon → Hides the entity's icon.
- name → Hides the entity's name.
- secondary_info → Hides secondary information related to the entity.
- progress_bar → Hides the progress bar display.
update documentation
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.47...1.0.48
1.0.47¶
What's Changed¶
Timer support: Improved. (issue #14)- add
bar_orientation: Allows the progress bar to be displayed from right to left, useful for timers.
- add
hover effect: Added.- The background color now changes when the mouse hovers over the card, dynamically using the icon's color.
- This effect applies only if the card has a
navigate_toorshow_more_infoparameter, ensuring a visual cue for interactive elements.
documentation updatecode cleanup
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.46...1.0.47
1.0.46¶
What's Changed¶
Timer support: Improved. (issue #14)- fix timer display
icon: Improved. Better default icon management.documentation updatecode cleanup
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.45...1.0.46
1.0.45¶
What's Changed¶
-
Timer support: Improved. (request from @FrankJaco,issue #14) - unit management -
%: show the ratio -s: show the seconds -timer: show HH:MM:SS (standard) -flextimer: same than timer but truncate the display according to the current value -Documentation update
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.44...1.0.45
1.0.44¶
What's Changed¶
Timer support: Improved. (request from @FrankJaco here: issue #14)unit: % or s. (fix ms issue)Badgemanagement: Added. Play/Pause icon according to the timer state.reverseparameter: Added. reverse parameter to allow a countdown.
Documentation update
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.43...1.0.44
1.0.43¶
What's Changed¶
Timer support: Added. Manage the timer entity state and animate the bar accordingly. (request from @FrankJaco here: issue #14)CSS: Improved. Remove hardcoded values using parametersDocumentation update
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.42...1.0.43
1.0.42¶
What's Changed¶
Multi-Language Support:- Added. 🇭🇷 🇵🇱 🇳🇱 🇲🇰 🇵🇹 🇩🇰 🇳🇴 🇸🇪
- The language selection, previously handled in the server configuration, is now managed in the user configuration to support multilingual usage.
Card height: Fixed. Occasionally appears "squashed" with @poiromaniax. (see issue #12)Code cleanup:- Reorganize parameters for better structure.
- Remove duplicate or unnecessary code.
- Refactor class for improved readability and understanding.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.41...1.0.42
1.0.41¶
What's Changed¶
icon: Added flexibility. Default icon is also selected with device_class Order of Priority for the Icon:- Theme/Custom Theme: The icon derived from the theme or style applied to the item.
- Icon Parameter: A custom icon specifically defined for the item.
- Icon Associated with the Entity: The icon directly linked or representative of the entity.
- Icon Associated with the Entity's device_class: temperature, humidity...
- Default: The icon used by default if no other is specified.
-
badges: Improved. The badge system has been enhanced for better handling of three distinct states:-
Description:
-
Unavailable:
- Badge Color: Orange
- Icon Color: Grey
- Additional Info: Secondary information displayed.
-
Not Found:
- Badge Color: Red
- Icon Color: Grey
- Additional Info: Secondary information displayed.
-
Unknown:
- Badge Color: None (no badge shown)
- Icon Color: Blue
- Additional Info: Secondary information displayed.
- Example
-
-
-
Code optimisation
1.0.40¶
What's Changed¶
icon: Added flexibility. TY @Jezza34000icondefined in custom_theme is now optional Order of Priority for the Icon:- Theme/Custom Theme: The icon derived from the theme or style applied to the item.
- Icon Parameter: A custom icon specifically defined for the item.
- Icon Associated with the Entity: The icon directly linked or representative of the entity.
- Default: The icon used by default if no other is specified.
discord server: Created. Link in the README
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.39...1.0.40
1.0.39¶
What's Changed¶
Vertical Layout: Fixed a minor regression (on 1.0.38) affecting the vertical layout styling.Theme Selector: Improved. Better design for a better experience.CSS Optimization: Added a dedicated icon class in the CSS (editor) to minimize unnecessary DOM modifications and improve styling consistency.Code Cleanup: Enhanced code readability and maintainability:- Reformatted arrays for consistency.
- Removed unecessary comments
- Removed last hardcoded values to improve flexibility.
- Resolved minor syntax issues for cleaner execution.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.38...1.0.39
1.0.38¶
What's Changed¶
-
Entity Statuses: Added handling forunavailableandunknownstatuses.- Displays the status text instead of the percentage when the entity is unavailable or unknown.
- Icon is greyed out, and an orange badge with an exclamation mark is shown for unavailable entities.
-
Error Message Style: Fixed- Fixed an issue where error messages were difficult to read in themes other than dark mode.
-
CSS: Improved styling by using more dynamic CSS rather than relying on JavaScript. -
Performance:- Offloaded more responsibilities to CSS, reducing unnecessary HTML DOM modifications.
- Optimized stored objects to reduce RAM usage.
- Added additional checks to determine if HTML updates are needed, improving efficiency.
-
Code Cleanup: Improved code for better readability and maintainability.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.37...1.0.38
1.0.37¶
What's Changed¶
custom_theme: Fixed. Under rare (and slightly amusing) circumstances, the evaluated value could exceed the theme's defined limits, or your custom theme's min/max intervals could have accidentally become incorrect, breaking your theme's interval continuity. 😅- Validation that
min<max: No more topsy-turvy intervals—each range must make logical sense now! - Validation of
min/maxcontinuity: Everymaxmax should flow seamlessly to the next min without any annoying gaps or overlaps. - Graceful boundary handling: If the evaluated value falls below the theme's defined intervals, we’ll gracefully default to the lowest definition. Similarly, values exceeding the theme will align with the highest definition.
- Validation that
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.36...1.0.37
1.0.36¶
What's Changed¶
- Vertical/Horizontal
Layout: Fixed. Simplified styles and minor bug fixes for better consistency. - Horizontal
Layout: Fixed. Now more aligned with a tile-based theme. Percentage: Fixed. Negative percentages previously caused some fun but unexpected visual behaviors, which have now been fixed.Performance: Improved. Optimizations for improved efficiency on bar animation.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.35...1.0.36
1.0.35¶
What's Changed¶
theme: Added temperature range (temperature theme) to get a beter color management between -50°C and 8°C.cleanup
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.34...1.0.35
1.0.34¶
What's Changed¶
custom_theme: Added. Anticipating every possible theming need is unrealistic. While predefined themes cover common use cases, some scenarios require greater flexibility. To accommodate this, I have introduced this option for advanced use cases, enabling users to define custom themes tailored to their specific requirements.Vertical layout: Fixed. Fine-tuned to manage the vertical layout using CSS mechanisms.JS vs CSS: Improved. Now handles component visibility (Show/Hide) using CSS, reducing JavaScript execution, improving performance, and enhancing maintainability by leveraging native browser rendering optimizations.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.33...1.0.34
1.0.33¶
What's Changed¶
- Mouse pointer fix: Fixed a bug where the pointer incorrectly indicated that the card was clickable regardless of the configuration.
- Error handling: Added an error message when an attribute is incorrect.
- Code and performance improvements:
- Enabled Shadow DOM for the editor to prevent style conflicts.
- Improved CSS for better readability and maintainability.
- Optimized some checks to speed up processing.
- Removed the last hardcoded values.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.32...1.0.33
1.0.32¶
What's Changed¶
Theme: Added CPU/RAM themes. Feature requested in "Consumption theme / battery inverse colors" by @nortuzar (see issue #9)
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.31...1.0.32
1.0.31¶
What's Changed¶
- Performance: Avoid DOM updates when values remain unchanged.
- Customization: Added bar_size parameter.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.30...1.0.31
1.0.30¶
What's Changed¶
Theme: Added support for°Fin thetemperaturetheme.Unit: Added automatic unit configuration based on entity attributs.Documentation: Updated and enhanced.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.29...1.0.30
1.0.29¶
What's Changed¶
Theme:- Improved Temperature/Humidity themes
- Added VOC/PM 2.5 themes
Documentation: updated and improved
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.28...1.0.29
1.0.28¶
What's Changed¶
Language support: Fixed Italian language 🇬🇧 🇪🇸 🇩🇪 🇮🇹 🇫🇷Theme: Added Temperature/Humidity theme
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.27...1.0.28
1.0.27¶
What's Changed¶
Language support: Added Italian 🇬🇧 🇪🇸 🇩🇪 🇮🇹 🇫🇷Attribute support: Added attribute support for cover, light, fan, climate, humidifier, media_player, vacuum, device_tracker, and weather.Code optimization: Perform code cleanup to enhance readability, remove redundant code, and optimize performance.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.26...1.0.27
1.0.26¶
What's Changed¶
Editor:Language support: Added translated labels for Theme choices to support multiple languages 🇬🇧 🇪🇸 🇩🇪 🇫🇷Documentation: Added a direct link to access the documentation.
Themeimprovements:- Fix the color scheme to match the existing battery theme.
- When the entity provide a
battery*icon, we use the device's charging icon to display its current charging status. This will provide a more visually informative representation of the battery level.
CardImprovements: Adjust the card's corner radius to align with the standard Home Assistant card radius for a consistent look and feel.Error Handling: Implement more robust error handling to catch and manage potential errors effectively.Code optimization: Perform code cleanup to enhance readability, remove redundant code, and optimize performance.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.25...1.0.26
1.0.25¶
What's Changed¶
Language support: Added translated labels for color choices to support multiple languages 🇬🇧 🇪🇸 🇩🇪 🇫🇷Icons for Layout Options: Added meaningful icons (mdi-) for layout choices to improve user experience.Code optimization
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.24...1.0.25
1.0.24¶
What's Changed¶
Fix: Resolved the issue described in "Card editor does one update and nothing else unless opened again" by @harmonie-durrant (see issue #8).- Split configuration management to enhance safety and prevent conflicts.
- Simultaneous update management
Code Optimization: Improved overall code performance and reduced complexity.Debug mode
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.23...1.0.24
1.0.23¶
What's Changed¶
navigate_to: fix a security-related issue when using navigate_to with an external URL (e.g., http://example.com/).
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.22...1.0.23
1.0.22¶
What's Changed¶
YAML Editor: Dynamically refresh the visual editor with accurate parameters sourced from the YAML editor.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.21...1.0.22
1.0.21¶
What's Changed¶
Editor: Reorganized configuration settings for better clarityEditor: Consolidated all settings within the visual editor, including:- Added
min_value - Added
max_value - Added
decimal - Added
unit
- Added
README: Updated to reflect the changes accordingly
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.20...1.0.21
1.0.20¶
What's Changed¶
navigate_to: add this parameter to specifie a URL to navigate to when the card is clicked.decimal: ⚠️ default value as been changed. ⚠️- Why? The default values for decimal have been carefully chosen to balance both functionality and aesthetics, ensuring the card remains visually appealing and easy to read in most cases. For percentage-based measurements, such as battery levels, the default is set to 0, as it is rarely meaningful to know the battery level down to a tenth of a percent (e.g., 82.3% vs. 82%). This avoids unnecessary precision, keeping the display clean and focused. In contrast, for other units like temperatures (°C) or energy consumption (kWh), the default is set to 2 to provide more detailed information where it might actually be relevant or actionable (e.g., 23.45 kWh). This distinction ensures that the data displayed aligns with typical expectations and practical usage, while allowing users the flexibility to customize the precision if their specific use case requires it.
- Impact? No real impact if you use the decimal or HASS precisision
parameter. The default value can be override with
decimalparameter to change and customize it.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.19...1.0.20
1.0.19¶
What's Changed¶
min_value: add this parameter to define the minimum value to be used when
calculating the percentage
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.18...1.0.19
1.0.18¶
What's Changed¶
More info: Added the ability to click on the card to display additional
information. (discussion with @mill1000 & @Ascathon in
https://github.com/francois-le-ko4la/lovelace-entity-progress-card/issues/5)
Animation: Expose the ha-icon and ha-shape elements to enable proper card
animation.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.17...1.0.18
1.0.17¶
What's Changed¶
decimal: fix this parameter to define the number of decimal places to display for numerical values. Discussion with @Ascathon in https://github.com/francois-le-ko4la/lovelace-entity-progress-card/issues/7
Defines the number of decimal places to display for numerical values. The decimal value will be determined based on the following priority:
- Display Precision from the entity (if defined in Home Assistant).
- decimal setting in the YAML configuration.
- Default Value (if no other value is set).
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.16...1.0.17
1.0.16¶
What's Changed¶
decimal: add this parameter to define the number of decimal places to display for numerical values. Discussion with @Ascathon in https://github.com/francois-le-ko4la/lovelace-entity-progress-card/issues/7code cleanup: rebuild internal check to improve the scalability
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.15...1.0.16
1.0.15¶
What's Changed¶
CSS: fix Extra padding around card when placed in section with width of 2 or more in https://github.com/francois-le-ko4la/lovelace-entity-progress-card/issues/6Language support: translate the layout choice 🇬🇧 🇪🇸 🇩🇪 🇫🇷Theme: merge the logic btwBatteryandLightand make it scalablecode cleanuprepository cleanup
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.14...1.0.15
1.0.14¶
What's Changed¶
Unavailable status: Check the current entity/entities status and display an unavailability message if the entity/entities is unavailableBug fix: Fix the Theme logic to avoid issue with max_valueBug fix: Fix custom unit by @harmonie-durrant in https://github.com/francois-le-ko4la/lovelace-entity-progress-card/pull/4README: Add README images by @harmonie-durrant in https://github.com/francois-le-ko4la/lovelace-entity-progress-card/pull/4README: Improve parameter descriptionCode cleanup
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.13...1.0.14
1.0.13¶
What's Changed¶
max_value: use another entity to define dynamically the max_value requested in https://github.com/francois-le-ko4la/lovelace-entity-progress-card/issues/3unit: we are able to change the default unit - '%' -> 'XYZ' (nice suggestion from @harmonie-durrant)error message: logic improvementREADME: Enhance the README by providing a clearer explanation of the parameter types and their expected values.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.12...1.0.13
1.0.12¶
What's Changed¶
Language Support: Added German 🇩🇪 to the interface.Editor Enhancements: improved error messages.Optimization: Improved logic to eliminate unnecessary refresh.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.11...1.0.12
1.0.11¶
Bug fix¶
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.10...1.0.11
1.0.10¶
What's Changed¶
- Language: take current language information from HA config 🇬🇧 🇪🇸 🇫🇷
- Percentage label: Limit 2 digits digits after the decimal point. TY Hypfer !
- max_value: to manage a stndard value and build a percentage.
- New theme: Add light theme 💡 by @harmonie-durrant in https://github.com/francois-le-ko4la/lovelace-entity-progress-card/pull/2
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.9...1.0.10
1.0.9¶
What's Changed¶
- Automatically adapts to the user's language for error messages and descriptions, ensuring a localized experience. 🇬🇧 🇪🇸 🇫🇷
- HACS better support by @harmonie-durrant in https://github.com/francois-le-ko4la/lovelace-entity-progress-card/pull/1
New Contributors¶
- @harmonie-durrant made their first contribution in https://github.com/francois-le-ko4la/lovelace-entity-progress-card/pull/1
TY!
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.8...1.0.9
1.0.8¶
What's New and Improved¶
CSS: Resolved CSS issues for the vertical layout, ensuring better display and functionality.Layout size: SynchronizedgetCardSize()andgetLayoutOptions()to ensure the layout size dynamically adapts to the selected layout for improved consistency and accuracy.Enhanced README Documentation: Added a YAML example demonstrating how to configure the vertical layout for easier implementation.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.7...1.0.8
1.0.7¶
What's New and Improved¶
-
Added layout Parameter: Now you can customize the arrangement of elements within the card! Choose between ahorizontalorverticallayout to match your design preferences and create visually appealing displays. Whether you prefer a side-by-side layout or a stacked configuration, the choice is yours. -
Enhanced README Documentation: We've expanded the README with practical use cases and detailed examples to help you get the most out of the card. Whether you're new to Home Assistant or a seasoned user, these additions will guide you through configuring and customizing your card effortlessly.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.6...1.0.7
1.0.6¶
What's New and Improved¶
- Editor: Enhanced YAML management, automatically removing empty keys.
- Entity (Editor): Use ha-entity-picker for a smoother user experience.
- Theme (Editor): Added a theme selection dropdown.
- Theme: Improved theme management for better flexibility.
- Size: Improved the default card size for better appearance and usability.
- Code Cleanup: Refined code structure and removed redundancies.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.5...1.0.6
1.0.5¶
What's New and Improved¶
- Introduced a Battery Theme: Simplifies creating a battery dashboard by automatically applying appropriate iconography and colors without requiring Jinja2 coding.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.4...1.0.5
1.0.4¶
What's New and Improved¶
This version introduces significant changes aimed at improving performance, error handling, and code readability. Below are the key updates:
Centralized DOM References: Introduced the _elements property to store references to DOM elements. This allows for more efficient and organized updates to the card's components.Optimized Card Construction:- Added the _isBuilt flag to prevent unnecessary card reconstruction after the initial configuration.
- The card's content is only built once, even during successive updates.
Dynamic Element Updates- New _updateDynamicElements method to dynamically update card elements (icon, name, progress bar, percentage, etc.) based on the entity state.
- New _updateElement method to centralize and simplify the logic for updating individual elements.
Improved Error Handling: Added a ha-alert component to display user-friendly error messages if the specified entity is not found in the configuration.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.3...1.0.4
1.0.3¶
Improvements and Enhancements¶
This release introduces significant improvements to the codebase and user experience:
Code: Cleanup and refactoringEnhanced Editor Interface: Added a color list to pick a standard color. Improved performance with fragment strategy.Browser console: This module creates an info event to log the card's status, providing feedback on its version and README access.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.2...1.0.3
1.0.2¶
Improvements and Enhancements¶
This release introduces significant improvements to the codebase and user experience:
- Code Cleanup: Streamlined the code by removing redundancies and improving structure for better maintainability and performance.
- Less Aggressive Rendering: Optimized the rendering process to reduce unnecessary refreshes, ensuring smoother performance.
- Enhanced Editor Interface: Updated the editing interface for a more responsive and natural user experience, improving usability and efficiency.
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.1...1.0.2
1.0.1¶
- improve the README
- clean the code
- add hacs.json
Full Changelog: https://github.com/francois-le-ko4la/lovelace-entity-progress-card/compare/1.0.0...1.0.1
1.0.0¶
Full Changelog: https://github.com/francois-le-ko4la/hass-entity-progress-card/commits/1.0.0