Required Options
A list of one or more Home Assistant calendar entity IDs to display. This is the only truly required field — every other option has a sensible default.
The title displayed in the card header.
Core Options
The view shown when the card first loads. Accepted values:
month— traditional monthly grid.weekorweek-compact— compact weekly overview where each day is a column with stacked events. The card normalizesweektoweek-compactinternally.scheduleorweek-standard— timed weekly grid with days as columns and hours as rows. Events are positioned as blocks by their actual start and end times. The card normalizesscheduletoweek-standardinternally.agenda— scrollable day-by-day list of upcoming events, rolling forward from today.
The day the week starts on, expressed as a number where
0 = Sunday, 1 = Monday, and so on through 6 = Saturday.An array of day numbers (0–6) to include in week and schedule views. Omitting a day hides it entirely from those views. Defaults to all seven days:
[0, 1, 2, 3, 4, 5, 6].Use [1, 2, 3, 4, 5] to show Monday through Friday only.The language used for all UI strings — day names, month names, button labels, and more. Supported values:
en, fr, de, nl, es, ca, da, sv. When omitted, the card automatically detects the language set in your Home Assistant profile.A BCP 47 locale string (e.g.
en-US, de-DE, fr-CA) that overrides the default locale associated with the selected language. Use this when you want, for example, German UI strings but Swiss date formatting (de-CH).Controls light/dark mode for the card.
auto follows the Home Assistant theme, light forces a light appearance, and dark forces a dark appearance.A unique string used as the browser-storage key for saving the user’s current view, hidden calendars, and other per-session preferences. When you have multiple Daylight Calendar Cards on different dashboards, give each one a different key so their preferences do not overwrite each other.
People & Calendar Mapping
A map of calendar entity IDs to Home Assistant The key must be a calendar entity ID that is already listed under
person.* entity IDs. When configured, the card reads each person entity’s current location state and displays a small avatar or badge on the calendar to show where household members are. This is especially useful on a family dashboard where you want to see at a glance that a family member is at school, at work, or home.entities. The value must be a valid person.* entity ID tracked by Home Assistant’s Person integration.Example
The YAML below shows a complete basic configuration that covers the most commonly used options:The visual editor covers all of these options — and many more — through a point-and-click interface. Open the card editor in Home Assistant, click the card, then select Edit to access it. You only need to write YAML manually if you prefer or if you are managing your configuration in version control.
