[Card] Automations Overview Card — Yesterday / Today / Tomorrow timeline of your automations

Share your Projects! Dashboards & Frontend
1

Hi everyone,

I built a custom Lovelace card that shows a Yesterday / Today / Tomorrow timeline of your automations: what triggered each run, what actions actually executed, and why a run was skipped when a condition wasn’t met. It reads directly from automation traces, so it reflects what actually happened, not just the automation’s YAML.

Repo: GitHub - Lunaticasylum67/Automations-overview-card: Lovelace card for Home Assistant showing a Yesterday/Today/Tomorrow timeline of automation runs — triggers, actions and skip reasons. · GitHub

EN-Legend & Filters
EN-Legend & Filters1647×387 12.1 KB

EN-Main
EN-Main1674×1138 48.3 KB

EN-NOW
EN-NOW1676×1123 39.3 KB

Why I built it

I wanted a single place to see, for every automation, “did it run, what did it do, and why didn’t it run when I expected it to” — without digging through Traces one automation at a time.

Features

  • Timeline per automation entity, grouped by day (yesterday / today / tomorrow), with day navigation.
  • For each run: the trigger that fired it, the action(s) actually executed, or the reason it was skipped.
  • Status color-coding: done, skipped, no action, error, running, planned, conditional.
  • A “planned” lane predicting upcoming time / sun / time-pattern triggers for tomorrow, plus a flag for triggers whose next run can’t be predicted.
  • Collapsible list of automations that only have unpredictable (conditional) future triggers.
  • Per-status filters and a legend.
  • Toggle between friendly names and entity IDs.
  • Resolves device_id-based action targets (e.g. camera.snapshot targeting a device) back to a readable entity name.
  • Built-in French / English UI, auto-detected from your HA profile language, with a manual override.

Requirements

You need to be logged in as a Home Assistant administrator to see the card’s data — it reads the device/entity registries and automation traces, both of which require admin-level access.

Installation

HACS (custom repository):

  1. HACS → “⋮” → Custom repositories.
  2. Add https://github.com/Lunaticasylum67/Automations-overview-card, category Dashboard.
  3. Install “Automations Overview Card”.

Manual: copy automations-overview-card.js to <config>/www/, add it as a Lovelace resource (module), and add the card. Full instructions in the README.

Usage

type: custom:automations-overview-card
title: Automations

All config options (language, filters, excluded entities, etc.) are documented in the README.

Feedback, bug reports and PRs are welcome — it’s still a young project. Let me know what you think!

1 Like
2

YAML change suggested:

type: custom:automations-overview-card
title: Automations Overview Card << This

It might get a bit lost if combined with other cards.

The English version also shows the time followed by a French word “maintenant”

Doesn’t show any system automations?

3

Thanks for the feedback, really helpful!

1. Good point on the title — updated the README example to `title: Automations Overview` and added a note that it’s worth picking something distinctive if you run this alongside other cards.

2. That’s a real bug — the French word “maintenant” was hardcoded in the timeline’s “now” marker regardless of language. Fixed, pushing the update shortly.

3. This is most likely not a bug but a UX trap: any automation whose trigger isn’t a simple time / sun / time-pattern trigger (which covers most state-based automations, including many “system” ones) doesn’t show up in the main timeline unless it actually ran today/yesterday/tomorrow — instead it’s listed in the collapsible **“Conditional automations”** section at the bottom of the card, which is collapsed by default. Can you check if that section (with the small arrow/expand control) shows them when you open it? If it’s still empty even there, let me know which automations specifically and I’ll dig further — there might be a real filtering issue I’m missing.

4

Thanks.
I clicked on the bottom one and none of the system ones I’m expecting are there. Your code may be working well but maybe I’m expecting the wrong things? Things like maintenance tasks etc.

5

Good catch, let’s narrow it down. Two possibilities:

1. By default the card hides **disabled** automations (`include_disabled: false`). This applies to the whole card, including the “Conditional automations” section — a disabled automation won’t show up anywhere. Can you check in Settings → Automations whether the ones you’re expecting are toggled on? If they’re off, try adding `include_disabled: true` to the card config and see if they appear.

2. If they’re already enabled and still missing: what exactly are these “maintenance tasks” — are they `automation.*` entities you can see under Settings → Automations, or are they something else entirely (e.g. scheduled backups, update checks)? The card can only ever show entities in the `automation.` domain — if these aren’t automations in HA’s own sense, that’s not something the card can pick up.

Let me know which one it is and I’ll take it from there.

6

I tested this on a honeypot virgin spinup that has no manual automations coded, so this may be expected functionality as you describe.

7

That explains it — a fresh/virgin Home Assistant install has zero automation.* entities out of the box. HA doesn’t ship any built-in “system” automations by default, so there’s nothing for the card to show. This is expected behavior, not a bug on the card’s side.

Thanks for testing it through, and glad points 1 and 2 are sorted!

1 Like