Skip to content

Connecting to CalDAV only show one calendar #42

Closed

Description

@davidmunoz-dev

Before submitting

  • I've searched existing issues and this isn't a duplicate.
  • This is a reproducible bug in Calnode — not a configuration/setup question or a feature request.

What's the bug?

I'm using Calendar app with Synology. When I connect to it through Calnode it only show the "primary" calendar and none of the others. Also the Check/Book inputs are confusing and the "book" can't be unchecked.
With any other app using the exact same login it does show me all the calendars I have in my account.
I should be able to choose which calendar to use.

Steps to reproduce

Calendar -> Connect a calendar -> CalDAV (Apple iCloud, Fastmail, Nextcloud)

Provider: Nextcloud / other (cusom URL)
Server URL: https://caldav.example.com
User: X
Password: X

Calnode version / commit

v0.9.0

How are you running Calnode?

Self-hosted — Docker

Logs, screenshots, or anything else

Image

Activity

  1. pullfrog commented on Sep 10, 2026

    @pullfrog
    Contributor
  2. shockalotti commented on Sep 17, 2026

    @shockalotti
    Contributor

    All three parts of this are real bugs, and all three are fixed on branch fix/mcp-bearer-archived:

    1. Only one calendar shown. Discovery walked your collections and kept just the first VEVENT one; the picker then reported only that. Now discovery returns every VEVENT collection (tasks/reminders-style ones still filtered out), seeds them with their server-side names, and the picker lists them all. The previously-picked calendar stays the bound default, so existing setups don't change behaviour.

    2. Checking never worked beyond the first calendar. Even deeper: conflict checks only ever queried the one bound collection, so ticking another calendar would have silently done nothing. Free/busy now REPORTs every selected collection and unions the results.

    3. Book can't be unchecked + confusing labels. The destination control was a radio with no empty state, and the backend already accepted a cleared destination - the UI just couldn't express it. It's now a toggle (select again to clear; writes fall back to the bound calendar), and the headers read Check / Destination with an explainer.

    Two honest caveats: existing connections list only the previously-bound calendar until reconnected (the re-list needs the calendar-home URL, which is stored from now on), and I verified against a fake server plus the full test suite - not a real Synology box. If you reconnect your account and open Manage calendars, I'd love to hear whether all your collections show up.

  3. davidmunoz-dev commented on Sep 17, 2026

    @davidmunoz-dev
    Author

    Thanks @shockalotti
    I just tested your changes and it does work perfectly !
    I've checked the calendar destination then created new bookings and it does show up well on the right agenda.

    Image
  4. shockalotti commented on Sep 17, 2026

    @shockalotti
    Contributor

    Fixed on main via #57 (commit c22fcc2 - CalDAV now discovers and checks every calendar, not just the first). Reopen if you still see it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions