HACS Default Store — Pending Approval · Install as custom repo now
Every Event.
One Timeline.
A timeline card for Home Assistant that merges calendars, cameras, door sensors, and APIs into one view.
A timeline card for Home Assistant that merges calendars, cameras, door sensors, and APIs into one view.
Merge events from any source — calendars, cameras, sensors, APIs — into a single, unified timeline view.
4 built-in adapters pull events from calendars, REST APIs, WebSocket commands, entity state history, and static YAML — all merging into one view.
150+ built-in keyword rules match event titles to Material Design icons and colors. "Dog detected" → 🐕, "Door opened" → 🚪. Works out of the box.
Clusters rapid-fire events into expandable groups. 10 motion alerts in 2 minutes become one collapsible entry.
Full GUI configuration right inside the HA dashboard editor. Add sources, tweak appearance, configure filters — no YAML required.
Camera snapshots, Frigate images, or any URL render inline as event thumbnails with media URL caching.
Auto-detects your HA locale. Override manually if you prefer.
Each adapter connects to a different type of event source. Mix and match freely — they all merge into one timeline.
Point Chronicle at any Home Assistant calendar entity and it pulls events automatically. Works with local calendars, Google Calendar, CalDAV, and more.
calendar.create_eventConnect to any REST API or HA WebSocket command. First-class Frigate support via WebSocket — see camera events with thumbnails in your timeline.
callApiConverts raw state changes into human-readable timeline events. A binary_sensor with device_class "door" becomes "Front Door Opened" / "Front Door Closed" automatically.
state_map to override any labelDefine events directly in your card configuration. Perfect for scheduled reminders, maintenance tasks, or any manually curated entries.
Add a chronicle card to any dashboard with a minimal YAML config. Icons, colors, grouping, and layout are handled automatically. Or use the built-in visual editor instead.
A few examples of how Chronicle Card works across different setups.
Track every door, lock, motion sensor, and alarm event. Filter by severity to focus on what matters.
Frigate detections flow in via WebSocket with thumbnails. Person, vehicle, pet — all auto-categorized.
Combine calendars, cameras, sensors, and static events into one unified timeline view.
Switch to a scrollable card grid for a compact, media-rich view.
Click any event to see full metadata, camera snapshots, and source info.
Configure sources, filters, grouping, and appearance — no YAML needed.
HACS Default Store approval pending — install via custom repo for now.
https://github.com/KadenThomp36/chronicle-card
/hacsfiles/chronicle-card/chronicle-card.js
For those who prefer full control.
chronicle-card.js from the latest release/config/www/chronicle-card.js/local/chronicle-card.js
Yes! Chronicle has first-class Frigate support via the REST/WebSocket adapter. It connects to Frigate's WebSocket API, maps detection events to timeline entries, and renders camera snapshots as inline thumbnails. See the examples in the documentation for a ready-to-use Frigate config.
No! Chronicle includes a full visual config editor that lets you add sources, configure appearance, set up filters and grouping — all through the HA dashboard editor GUI. YAML is available for advanced users but never required.
Chronicle Card requires Home Assistant 2024.1.0 or newer. It uses modern HA APIs for calendar access, history queries, and WebSocket communication that are available from that version onward.
Absolutely. You can add as many sources as you like — mix calendars, Frigate cameras, door sensors, and static events in a single card. Everything merges into one chronological timeline with proper grouping and filtering.
Chronicle uses virtual scrolling to only render visible events, debounced fetching to minimize API calls, and a media URL cache (3-hour TTL) for thumbnails. It handles hundreds of events smoothly even on lower-powered devices.