Skip to main content
The Month view renders a classic calendar grid — one row per week, one column per day — giving you an at-a-glance picture of the entire month. Events appear as colored chips on each day cell, and you can tap any chip to open the event detail panel. Use the arrow buttons in the card header to move between months, or swipe left and right directly on the grid.

​
Activating Month View

Set default_view to month in your card configuration to open the card on the monthly grid by default: 
type: custom:daylight-calendar-card
default_view: month
Users can still switch to other views using the view selector buttons in the card header. To hide those buttons and lock the card to Month view, add hide_view_selector: true.

​
Configuration Options

​
show_all_events_month
boolean
default:"false"
Used by Month only.By default, day cells truncate their event list and show a +N more overflow label when there are more events than fit in the cell. Set this to true to expand every day cell and display all events without truncation. This increases the row height dynamically, so the card will grow taller on busy weeks.
​
show_all_details_month
boolean
default:"false"
Used by Month only.When true, each event chip in the month grid includes the event start time and any additional detail text alongside the event title. This is also the flag that enables show_event_location / use_short_location rendering in Month — otherwise location is omitted from Month event chips.
​
show_week_numbers_month
boolean
default:"false"
Used by Month only.Adds an ISO week-number column on the left edge of the grid (e.g., W 23). Handy for work or project planning where teams reference week numbers.
​
rolling_weeks
number
default:"null"
Used by Month only.By default, Month view snaps to a full calendar month — every cell from the 1st to the last day of the current month, padded with neighboring days to fill complete weeks. Set rolling_weeks to a positive integer to switch to a rolling N-week window that always starts on the current week and looks forward N weeks.For example, rolling_weeks: 4 renders four week rows: this week plus the next three. Navigation arrows shift the window one week at a time instead of one month.
​
first_day_of_week
number
default:"0"
Used by Month, Week Compact, and Schedule. In Week Compact and Schedule, only affects normal week mode — it is ignored in rolling-days mode.The day number (0–6) that anchors the left edge of the grid. Set to 1 to start each row on Monday.
​
shorten_event_times
boolean
default:"false"
Used by Month, Week, Schedule, and Agenda.When true, event time labels are abbreviated — for example 10 AM instead of 10:00 AM. In Month, time labels only appear on event chips when show_all_details_month is enabled.
​
use_24hr_schedule
boolean
default:"false"
Used by Month, Week, Schedule, and Agenda. Despite the name, it is used by the shared event-time formatter, not only the Schedule view.When true, event times use 24-hour format (e.g. 14:00) instead of 12-hour format with AM/PM.
​
show_event_location
boolean
default:"false"
Used by Week, Schedule, and Agenda. Also applies to Month only when show_all_details_month is enabled — it does not affect normal Month event chips.When true, the location field of each event is displayed below the event title.
​
use_short_location
boolean
default:"false"
Used by Week, Schedule, and Agenda. Also applies to Month only when show_all_details_month is enabled. Has no visible effect unless show_event_location is also enabled.Truncates long location strings to a shorter form so they don’t push event chips taller.
​
hide_times_for_calendars
array
default:"[]"
Used by Month, Week, Schedule, and Agenda.An array of calendar entity IDs whose events should not display time labels. Useful for all-day-style calendars where exact times are noise.
​
past_event_mode
string
default:"none"
Used by Month, Week, Schedule, and Agenda. Controls how events that have already ended are handled across the card. Accepted values:
  • none — past events look identical to upcoming events (default).
  • muted — past events are rendered at reduced opacity so today’s and future events stand out.
  • hide — past events are not rendered at all.

​
Example Configuration

The following configuration activates Month view with week numbers, full event lists, and muted past events: 
type: custom:daylight-calendar-card
default_view: month
show_all_events_month: true
show_all_details_month: false
show_week_numbers_month: true
past_event_mode: muted

​
Tips

If you place the Daylight Calendar Card inside a panel or grid dashboard layout where the card is expected to fill a fixed container, add compact_height: true. This makes the card match its parent container’s height exactly instead of expanding to fit all content, preventing layout overflow on busy months.
Combine show_all_events_month: false (the default) with past_event_mode: muted for the cleanest month view: upcoming events pop visually while past events fade into the background without disappearing entirely.