> ## Documentation Index > Fetch the complete documentation index at: https://docs.daylightcalendar.com/llms.txt > Use this file to discover all available pages before exploring further. # Daylight Calendar Card: Troubleshooting Common Issues > Fix common problems with the Daylight Calendar Card including missing events, blank cards, event editing errors, weather not showing, and layout issues. The Daylight Calendar Card is designed to work out of the box with any Home Assistant calendar integration, but a few common configuration issues can cause unexpected behavior. This page walks you through the most frequently encountered problems and how to resolve them. Work through the section that matches your symptom, and if nothing here helps, see the bug report guidance at the bottom of this page. This error means Home Assistant has not loaded the card's JavaScript file as a dashboard resource. The card UI will not render at all until the resource is registered. **Steps to fix:** 1. In Home Assistant, go to **Settings → Dashboards → Resources** (you may need to enable Advanced Mode in your profile first). 2. Check that `skylight-calendar-card.js` is listed and its type is set to **JavaScript Module**. 3. If the entry is missing, add it manually. The URL should match your installation path, for example `/hacsfiles/daylight-calendar-card/skylight-calendar-card.js` (HACS) or `/local/skylight-calendar-card.js` (manual). 4. Hard-refresh your browser with `Ctrl+Shift+R` (Windows/Linux) or `Cmd+Shift+R` (Mac) to force the browser to reload the resource. If you installed via HACS, the resource entry is usually added automatically. If it's missing, try removing and re-downloading the card in HACS, then check Resources again. A blank calendar most often means the card cannot find any events from the configured entities, or the entities themselves are not returning data. **Things to check:** * Verify that the entity IDs in your `entities` list exactly match calendar entities in Home Assistant. Entity IDs are case-sensitive. * Open the **Calendar** view in the Home Assistant sidebar and confirm your events appear there. If they don't, the problem is with the calendar integration itself, not the card. * Review your YAML for typos in the `entities` block: ```yaml theme={null} type: custom:daylight-calendar-card entities: - calendar.my_google_calendar - calendar.family ``` * Temporarily remove any filters that could be hiding all events, such as: ```yaml theme={null} past_event_mode: hide default_hidden_calendars: - calendar.my_google_calendar ``` Open your browser's developer console (F12) and look for any errors from the card while the dashboard loads. Connection errors may indicate that Home Assistant is slow to deliver calendar data — try refreshing the page after a few seconds. If HACS shows the latest version but new frontend behavior is missing, the most common cause is a stale dashboard resource or browser cache. HACS confirms that the files are installed. It does not confirm that Home Assistant or your browser is loading the current file. This is especially likely if you installed the card before the Skylight → Daylight rename. The filename is still `skylight-calendar-card.js` for compatibility, but the HACS folder path should now be the Daylight folder. **Symptoms:** * New options or features are missing * Documented options have no effect * The card editor looks outdated * The card editor is missing the **About / Diagnostics** section **Steps to fix:** 1. **Confirm HACS version** Open **HACS → Frontend → Daylight Calendar Card** and confirm it shows the version you expect. This only confirms installation, so continue with the resource checks below if the dashboard still looks old. 2. **Check Dashboard Resources** In Home Assistant, go to **Settings → Dashboards → Resources**. Look for every resource entry that points to `skylight-calendar-card.js`. 3. **Remove old Skylight resources** Delete duplicate or old entries that point to the pre-rename folder, such as: ```text theme={null} /hacsfiles/skylight-calendar-card/skylight-calendar-card.js ``` 4. **Keep only the current Daylight resource** For a HACS install, the resource should use the Daylight folder: ```text theme={null} /hacsfiles/daylight-calendar-card/skylight-calendar-card.js ``` The filename is intentionally still `skylight-calendar-card.js`. The important part is the folder path: `daylight-calendar-card`, not `skylight-calendar-card`. 5. **Refresh or restart** Hard-refresh your browser with `Ctrl+Shift+R` (Windows/Linux) or `Cmd+Shift+R` (Mac). If the old UI still appears, try a private/incognito window, clear your browser cache, or restart Home Assistant. 6. **Verify the current editor loads** Edit the card in your dashboard and scroll to the bottom of the card editor. Seeing the **About / Diagnostics** section is a good sign that the current frontend/editor is loading. If that section is missing, an old frontend resource is probably still being loaded. 7. **Include details when opening an issue** If you still need help, include screenshots of: * The HACS version shown for Daylight Calendar Card * **Settings → Dashboards → Resources** * The bottom of the card editor, especially whether **About / Diagnostics** appears This checklist is most useful when HACS shows the latest version but new options or editor sections are missing. Other bugs can have different causes. The **Add Event** button is hidden when event management is disabled or no writable calendar is available. Check each of the following in your card YAML: * `enable_event_management: false` — set this to `true` to enable event management. * `hide_add_event_button: true` — set this to `false` or remove the line entirely. * All of your calendar entities are listed under `readonly_calendars` — remove any calendars you want to write to from that list. ```yaml theme={null} type: custom:daylight-calendar-card entities: - calendar.my_calendar enable_event_management: true hide_add_event_button: false readonly_calendars: [] ``` At least one calendar entity must be writable (i.e., your Home Assistant integration must support creating events for that calendar). Read-only integrations — such as some holiday calendars — cannot receive new events regardless of card settings. There are several reasons an event might not be editable or deletable: **Google Calendar events** Editing events is not supported through the Home Assistant Google Calendar integration. Google Calendar edits are simulated via create-then-delete, which changes the event's UID. To truly edit an event, use the Google Calendar app or website directly. Deletion does work through HA. **Event is missing a UID** Some calendar integrations do not attach a UID to every event. Without a UID, the card cannot uniquely identify the event to send an edit or delete request. The only fix is to delete the event and recreate it through a source that generates UIDs. **Calendar is marked read-only in the card config** Check whether the calendar is listed under `readonly_calendars`: ```yaml theme={null} readonly_calendars: - calendar.work_holidays ``` Remove it from the list if you want to allow editing. **Event management is disabled globally** Confirm `enable_event_management` is not set to `false` in your card config. Never store sensitive data in calendar event titles or descriptions with the expectation that the card's read-only setting will protect it. `readonly_calendars` only affects the card UI — the underlying HA integration may still allow edits through other means. Weather icons require a valid `weather.*` entity that provides a daily forecast. **Steps to fix:** 1. Confirm you have set `header_weather_sensor` in your card config: ```yaml theme={null} header_weather_sensor: weather.home ``` 2. Open **Developer Tools → States** in Home Assistant and search for your weather entity (e.g. `weather.home`). Verify it exists and has a valid state. 3. Confirm that the weather integration provides a **daily forecast**. Some integrations only provide hourly forecasts, which the card does not use for day-cell icons. 4. If the entity exists and has a daily forecast but icons still don't appear, check the browser console for errors related to the weather subscription. On slower Home Assistant instances, weather data may take a few seconds to arrive after the page loads. Refresh the page and wait a moment before concluding the icons are broken. Height behavior depends on the dashboard layout you're using. **Using a panel or grid dashboard layout** Enable compact height mode to let the card fill its container: ```yaml theme={null} compact_height: true ``` This tells the card to measure its parent container and size itself to fit the available vertical space. It works correctly in HA panel and grid dashboard layouts. **Using a sidebar or standard layout** The card auto-sizes to its content in standard layouts. If it appears clipped, check whether `compact_height: true` is set — this mode is not appropriate for sidebar layouts and may cause the card to collapse. Remove it or set it to `false`. **Fine-tuning the height** Use `height_scale` to proportionally scale the card taller or shorter: ```yaml theme={null} height_scale: 1.2 # 20% taller than default height_scale: 0.85 # 15% shorter than default ``` `compact_height: true` requires the card to be placed in a grid or panel dashboard layout. In a standard vertical layout, use `height_scale` instead. If you see the same event appearing twice (or more), you likely have multiple calendar entities that both contain that event — for example, a personal Google Calendar and a shared family calendar that both include the same entry. Enable calendar combining to automatically deduplicate events that share the same normalized title, start time, end time, and location: ```yaml theme={null} combine_calendars: true ``` Deduplication does not rely on event UIDs. If duplicates persist after enabling `combine_calendars`, compare the event title, start time, end time, and location across calendars. Any difference in those fields makes the card treat the entries as distinct events. The card auto-detects your language from Home Assistant's locale settings. If detection produces the wrong language or date format, you can override both explicitly. **Set the display language:** ```yaml theme={null} language: de ``` Supported language codes: `en` (English), `fr` (French), `de` (German), `nl` (Dutch), `es` (Spanish), `ca` (Catalan), `da` (Danish), `sv` (Swedish). **Set the date and time locale:** ```yaml theme={null} locale: en-US ``` The `locale` key controls how dates and times are formatted (e.g. `MM/DD/YYYY` vs `DD.MM.YYYY`) and is independent of the `language` key. If you share a dashboard with users in different regions, set both `language` and `locale` explicitly so formatting is consistent regardless of individual HA profiles. If the card header appears but the calendar body is missing, check whether your dashboard card has an explicit `grid_options.rows` value that is too small. This can happen in v4.5.0 and newer because the card body now fills the available height of the Home Assistant dashboard card. If the dashboard card is only one row tall, the calendar body may collapse and only the header remains visible. **Fix:** ```yaml theme={null} grid_options: rows: 8 ``` If you currently have `rows:` set to anything less than 4, it is probably too small. The safest approach remains removing `rows:` entirely and letting the card size naturally. The card keeps a local snapshot of the last successful calendar fetch so it can render events immediately when Home Assistant reloads, even before a fresh refresh completes. The snapshot is stored in the browser (IndexedDB) and is scoped to your current card configuration. **What you might see:** * A brief flash of previously known events on startup before the current data loads. * A small **"Calendar data may be stale"** warning if no successful refresh has completed for 30 minutes (for example, when Home Assistant is unreachable or a calendar integration is failing). * Events that were deleted on your calendar still appearing until the next successful refresh finishes. This is expected behavior. A successful refresh — including one that legitimately returns no events — replaces the cached snapshot. Failed refreshes leave the last-known-good data in place instead of blanking the card. **If cached data looks wrong or you want to force a clean reload:** 1. Edit the card and scroll to **About / Diagnostics**. 2. Select **Flush event cache**. 3. The card clears its stored snapshots and triggers a fresh fetch from Home Assistant. Flushing only removes Daylight Calendar Card snapshots from your browser. It does not delete any events from your calendar integrations. If none of the above resolves your issue, please open a GitHub issue so the maintainer can investigate. **Before submitting, gather the following:** * Which dashboard view and card position is affected * Your complete card YAML configuration (remove any sensitive entity names if needed) * Screenshots or a screen recording of the problem * Your Home Assistant version (found in **Settings → About**) * Your browser and version * Any errors shown in the browser developer console (F12 → Console tab) Incomplete bug reports are much harder to diagnose. Including your full YAML config and HA version is the single most helpful thing you can do. Open an issue at [github.com/superdingo101/daylight-calendar-card](https://github.com/superdingo101/daylight-calendar-card/issues).