When I started in October 2026, the built-in CalDAV integration of Home Assistant could only show events and create new ones. Changing or deleting them didn't work, it didn't know recurring events as a series, and to-dos had neither subtasks nor reminders. My CalDAV integration does all of that, but has to be installed on top.
So I'm bringing these features into Home Assistant itself, one by one, until my integration is no longer needed. Each feature is its own pull request that the Home Assistant team reviews. Some depend on bugs in libraries, others on decisions that apply to every calendar in Home Assistant. This post shows for every feature whether it's already in and what blocks it otherwise.
To-do lists
- To-dos show when they were completed: in Home Assistant 2026.11 (core#187925)
- Checking off a to-do in Home Assistant saves when it was completed: in 2026.11 (core#188236)
- Unchanged lists are not reloaded on every poll: in 2026.11 (core#188540)
- Sort to-dos: in review (core#189018, docs#49947), a fix it needs is already merged (core#189017)
- Recurring to-dos move to their next date when checked off: blocked by a bug in the caldav library (caldav#765), the fix is merged and ships with the next release (caldav#845)
- Subtasks: blocked by the new field for all to-do lists, which Home Assistant doesn't have yet. The architecture team approved it in November 2026 (discussion)
- Priority: blocked by an open decision for all to-do lists, already discussed by the architecture team (discussion)
The to-do model of Home Assistant has no subtasks or priority for any integration yet. A new field there applies to every to-do list, so it needs a decision by the architecture team. For subtasks that decision has been made, for priority it is still pending.
Calendars and events
- Calendars take their color from the server: in 2026.11 (core#188287)
- Unchanged calendars are not reloaded on every poll: up next
- Recurring events show up as a series: blocked by bugs in the ical library (ical#676, ical#692)
- Change and delete events, one occurrence of a series or all later ones: blocked by the point above and more bugs in ical after ical#728
- Change and delete events from automations: blocked by the point above and an open decision for all calendars (discussion)
- Attendees: blocked by an open decision for all calendars, since 2024 (discussion)
- Attachments: blocked, the discussion so far was not accepted as a proposal
- Reminders trigger automations: blocked, there is no proposal for this yet
Recurring events are the biggest blocker. Today Home Assistant gets every event of a series on its own, without the rule behind it, so it shows a lot of single events. The interface can already edit a series, it only lacks that rule. Reading and editing are meant to go through ical, the library that the local calendar of Home Assistant uses too. A few bugs there have to be fixed first.
Setup and troubleshooting
- Change the server or password without setting it up again: in 2026.11 (core#188159, docs#49680)
- Diagnostics for bug reports: in 2026.11 (core#188158)
CalDAV only
- Answer invitations, free/busy, journal entries, import and export, create calendars: after the points above, as actions of the CalDAV integration
Not coming are a poll interval option, which Home Assistant doesn't allow, and shared or delegated calendars, which the library can't do.
How to help
Many blockers are open decisions of the architecture team. What helps there is showing that a feature is needed. If you need one of them, upvote its discussion. You can of course join the discussion too, for example with your own use case. To keep the discussions readable, plain agreement is best shown with an upvote rather than a comment.