Release list

v4.0.0 Latest

Latest

github-actions released this 18 Aug 18:46

v4.0.0

f522678

Calendar Card Pro v4.0.0

This is a big one. 🎉

Two days after this card's first public release, someone opened #14 and asked whether the days could sit side by side instead of stacked on top of each other. That was March 2025. It was asked again in June, again in July, and again in November — the most-requested thing in this project's history, and the one I never had a good answer for. Last year did not leave me the time this card deserved, and some of you waited a lot longer than you should have for it.

So I gave this release the time instead: 560 commits, and the kind of polish I would want if I were the one installing it. 🗓️ Column view is here — the same agenda you already have, rotated, with your events and colors carrying over exactly as they are. And because a layout with its own defaults, its own per-view overrides and its own density rules needs an editor that can actually express them, ⚙️ the visual editor is rebuilt from the ground up: nine panels, a search box that reaches any of 119 settings in a keystroke, and a filter that hides everything you have never touched.

Here is the part I am proudest of, though. Both of those are opt-in — most cards will never set view or open a form — so this could easily have been a big release for a few people and nothing much for everyone else. It is not. ⚡ Moving the editor into a file that loads only when you open it leaves a card file 41% smaller to download on every single dashboard, whether or not you ever touch either feature. 🐛 And behind that sit twenty-three fixes that reach further than any feature does: week numbers wrong for one date in seven outside UTC, a twelve-hour clock handed to 33 of the 64 languages Home Assistant ships, and a first_day_of_week: system that quietly answered Monday to every user on earth.

A card that does not set view keeps the list it has always had. But a few things change whichever layout you use, so they come first. 👇

⚠️ Breaking Changes

Manual Installation Now Copies Two Files - The card is no longer a single file. A release ships calendar-card-pro.js and editor.js, and the card fetches the editor by URL the first time someone opens it. HACS handles this and needs nothing from you. If you install by copying files into www/, download both and put them in a folder of their own, such as www/calendar-card-pro/ — copying only calendar-card-pro.js leaves a card that renders normally but reports a missing file when you open the visual editor, and /config/www/ itself is shared with every other hand-installed card, where a second editor.js can take the name. Only calendar-card-pro.js is registered as a Lovelace resource; see Manual Installation
event_icon_vertical_alignment Now Defaults to top - It previously defaulted to middle. The option is invisible until a row wraps, and middle then centers the icon against the whole wrapped block — a clock or map-marker floating level with neither line of a two-line address. Column view wraps routinely, and the list view wraps on a long location or description, so the default moved to the alignment that reads correctly in both. Set event_icon_vertical_alignment: middle to keep the old behavior; see Spacing & Alignment
first_day_of_week: system Now Follows Home Assistant - system is the default, and the editor labels it Follow Home Assistant, but it returned Monday for every user on earth. Two faults produced it: the branch never read the First day of week setting in the Home Assistant user profile at all, and its language fallback tested for en-US, en-CA or es-US in a string that has always been lowercased before it arrives, so it could not match anything. The setting is now resolved the way Home Assistant resolves it — an explicit weekday in the profile wins, and only when that is left at Auto does the language decide. Upgrading therefore shifts week numbers, week separators and the start_date: start_of_week anchor for anyone whose profile or language implies a week that does not begin on Monday — nineteen of the 64 languages Home Assistant ships, seventeen starting on Sunday and Arabic and Persian on Saturday. Set first_day_of_week: monday to keep the old behavior; see Week Numbers & Visual Separators
Weather Badges Are Styled Through Custom Properties - The weather icon and text carried their font size and color as inline style attributes, which no theme could override. Those attributes are gone, and the six --calendar-card-weather-* properties the card was already emitting are now read by the stylesheet instead, making them a real override surface. Two things follow. Card-mod rules that targeted the inline-styled elements need updating — the properties are listed under Weather Custom Properties. And weather.date.color / weather.event.color no longer carry a default. They did in 3.x, but it never reached a card that showed weather: setConfig merged only the top level, so any weather: block replaced the whole default sub-tree. The rendered color came from a fallback in the renderer either way — primary for the day header, secondary for the per-event badge — and both fallbacks now live in the stylesheet with the same values, so the badge looks as it did

🎉 New Features

🗓️ Column View

See the week at a glance instead of scrolling through it. view: column lays the days out side by side, one column each, instead of stacking them — the same agenda the list layout already shows, rotated. Your events, labels and colors carry over exactly as they are; only the date moves, from the left of each row to the top of each column. The default is still list, so nothing changes until you ask for it (#377, #14, #263, #253)

It Falls Back on a Phone - Columns need width, so a card too narrow to give every day a readable one — column.min_day_width, 140 pixels — simply renders as a list instead. The same card can be columns on a desktop dashboard and a list on a phone, with no second card and no conditional wrapper. That is also why the editor annotates list-only options rather than hiding them: hiding a control would remove it for the layout that same card uses on a phone
Or Sheds a Day Instead - If you would rather keep the columns, column.min_days_to_show lets a narrowing card drop trailing days one at a time before it gives up on the layout. It defaults to days_to_show, which leaves the behavior off, because a card quietly showing four of seven days looks exactly like a card configured for four. column.min_days_fallback: cramp keeps every day and lets the columns go narrower still
Different Values in Columns Than in the List - A size tuned for a full-width row is usually wrong in a 140px track, so a nested column: block holds the values that apply only when the card renders as columns; anything it does not mention keeps its top-level value. It works in both directions, so an option switched off at the top level can be switched back on for columns. Only presentation options may go there — anything deciding which events are loaded has to hold one value in both layouts, since the card switches between them as the dashboard resizes (see Overriding Options in Column View)
Two Options Start From a Different Default - show_empty_days and split_multiday_events both default to true in column view and do not inherit the top-level value. A list reads perfectly well with the blank days left out; a row of columns does not, because dropping the empty ones stops the columns corresponding to consecutive days. The same reasoning covers a multi-day event — a column is a day, so an event spanning three of them belongs in all three (see Options That Start From a Different Default)
Separators Rotate into the Gutter - Day, week and month separators keep their existing options and become full-height vertical rules between the columns, with month taking precedence over week and week over day. A column-only rule can also run under each day header — column.day_header_separator_width and _color — off by default like every other separator in the card. Switching it on centers it inside the space column.day_header_gap already reserves, rather than shifting the layout
A Header Per Column - Week numbers move into each column's header instead of taking a full-width row, and the today indicator becomes a leading marker on the weekday row so it stays unambiguous at any column width — the default 15% 50% position is calibrated for the list view's narrow date cell and would land inside the day number on a full-width column header
Room for the Progress Bar - A countdown and a progress bar never appear on the same event, so each now gets the treatment it needs instead of one compromise suiting neither. The countdown stays on the time row as trailing text after a middot, breaking at an ordinary word boundary when the column is too narrow; the bar moves to a row of its own under the title, spanning 80% of the column
One Click From the Card Picker - Adding a card by entity and picking a calendar.* entity now offers two starting points under Community: _Calendar Card...

Contributors

wsw70, fugazzy, and 5 other contributors

Assets 4

v3.6.0

github-actions released this 14 Aug 08:46

v3.6.0

44ccfe9

Calendar Card Pro v3.6.0

A documentation site of its own, and six fixes for defects that made the card look broken rather than merely wrong. Everything that used to be buried in a very long README now lives at calendar-card-pro.alexpfau.com, with a page per feature and a complete configuration reference. Alongside it: a card that no longer disappears behind a red error box because of one stray line of YAML, per-calendar settings that take effect when you change them instead of whenever a cache happens to expire, and text that stops vanishing mid-word.

🎉 New Features

📚 A Documentation Site

calendar-card-pro.alexpfau.com - The full manual is now a searchable site rather than a README you scroll through: a page per feature, a complete configuration reference listing every option with its type and default, a usage guide that starts from a working card, and ready-made examples. The README is now a landing page that points at it, so installation and a first working card are the first things you see

🐛 Bug Fixes

Reliability

One Stray Line of YAML Took Down the Whole Card - A bare - in the entities: list, left behind while editing or written as entities: [~], parses to null. The config normalizer accepted it and then read a property off it, throwing before the card rendered — so Home Assistant replaced the entire calendar with a red error box. Malformed entries are now discarded, which is what the surrounding code always intended (#389)
Per-Calendar Settings Ignored Until the Cache Expired - Events were cached after processing, but the cache key described only what had been fetched — the calendars and the time window. Every other option the processing step reads was invisible to it, so editing a per-calendar label, colour or toggle appeared to do nothing until the entry aged out. The cache now stores the raw calendar payload and reprocesses it on every read, so edits apply immediately; per-calendar event limits were also silently degrading on a cache hit and no longer do

Appearance

Titles Ellipsised When Nothing Had Been Truncated - Event titles showed a trailing … at certain card widths even though no characters had been dropped, and at slightly narrower widths the ellipsis ate one or two real characters before the title finally wrapped. The card offers no title-truncation option, so that ellipsis could only ever announce a truncation that had not happened
Words Disappeared Mid-Character in Descriptions and Locations - The description, location and time rows could shrink below the width of their own longest word and clip it mid-glyph, with no ellipsis to indicate anything was missing — measured on a 300px card, a 179px word in a 167px box painted 12 pixels of its last character and dropped the rest. Long words now wrap instead of being cut off

Countdown

Multi-Day Countdowns Disagreed From Row to Row - With split_multiday_events enabled a multi-day event renders one row per day, and each row was counted differently: the first measured wall-clock time and lost a day after midday, the middle rows counted calendar days, and the last counted to a midnight that exists only because of the split. A holiday four days out read in 3 days / in 5 days / in 6 days / in 6 days. Every row now counts whole calendar days to its own date, so the sequence reads consecutively; this also fixes countdowns vanishing from just the middle rows when show_countdown_allday was off (Thanks @Scooshie and @BalooDK, #344)

Configuration

Options Removed in v3.0.0 Were Ignored in Silence - Five options dropped in the v3.0.0 cleanup — max_events_to_show, vertical_line_color, horizontal_line_width, horizontal_line_color and row_spacing — were discarded without comment for anyone configuring the card in YAML: the value vanished, its replacement took the default, and nothing anywhere said so, which reads as "the update changed my styling". Each removed option is now reported in the browser console together with the option that replaces it. The visual editor already offered a one-click upgrade; this closes the gap for everyone who never opens it

🔧 Under the Hood

The renderer's leaf elements and the event presentation model moved into modules of their own, and whether an all-day event shows a time row is now decided by the formatter instead of by substring-matching the string it had just produced — a test that had no margin in the eight languages whose "until" translation is two characters long. The list view's rendered DOM is byte-identical throughout, now pinned by a test suite so that stays true.