2025-01-05 22:08:17.648 ERROR (SyncWorker_5) [caldav] Possibly the server has a path handling problem, possibly the URL configured is wrong.

[thogitnet]

I use a calDav service from my provider which has a different URL format. The URL is /calendars// instead of calendars/principals//

For this reason I get this error message when starting HA. However, the connection to the service basically works.

homeassistant  | 2025-01-05 22:08:17.648 ERROR (SyncWorker_5) [caldav] Possibly the server has a path handling problem, possibly the URL configured is wrong.
homeassistant  | Path expected: /calendars/principals/<USER>/, path found: ['/calendars/<USER>/'] Please raise an issue at https://github.com/python-caldav/caldav/issues or reach out to [email protected], include this error and the traceback and tell what server you are using.
homeassistant  | Continuing, probably everything will be fine
homeassistant  | 2025-01-05 22:08:17.650 ERROR (SyncWorker_0) [caldav] Possibly the server has a path handling problem, possibly the URL configured is wrong.
homeassistant  | Path expected: /calendars/principals/<USER2>/, path found: ['/calendars/<USER2>/'] Please raise an issue at https://github.com/python-caldav/caldav/issues or reach out to [email protected], include this error and the traceback and tell what server you are using.
homeassistant  | Continuing, probably everything will be fine
homeassistant  | 2025-01-05 22:08:17.713 ERROR (SyncWorker_3) [caldav] Possibly the server has a path handling problem, possibly the URL configured is wrong.
homeassistant  | Path expected: /calendars/principals/<USER>/, path found: ['/calendars/<USER>/'] Please raise an issue at https://github.com/python-caldav/caldav/issues or reach out to [email protected], include this error and the traceback and tell what server you are using.
homeassistant  | Continuing, probably everything will be fine
homeassistant  | 2025-01-05 22:08:17.722 ERROR (SyncWorker_2) [caldav] Possibly the server has a path handling problem, possibly the URL configured is wrong.
homeassistant  | Path expected: /calendars/principals/<USER2>/, path found: ['/calendars/<USER2>/'] Please raise an issue at https://github.com/python-caldav/caldav/issues or reach out to [email protected], include this error and the traceback and tell what server you are using.
homeassistant  | Continuing, probably everything will be fine

[tobixen]

This is interesting - what server do you use?

(I should probably consider to remove this warning or downgrade it to info, I think nobody reporting it has had problems with it).

[thogitnet]

I use the Service from All-Inkl. (all-inkl.com), a German web hoster.

The URL is also shown in setp 6 in the setup guide ...
https://all--inkl-com.translate.goog/wichtig/anleitungen/programme/e-mail/caldav-kalenderfunktion/einstellungen-im-webmail-anzeigen_457.html?_x_tr_sl=de&_x_tr_tl=en&_x_tr_hl=de&_x_tr_pto=wapp

Is there a standard (RFC or similar) where you can point this out to the provider?
Or to what extent is this a problem? During the implementation, something was thought of to display this message...

[tobixen]

So your configuration is set to /calendars/<USER>/ and not /calendars/principals/<USER>/? Hm. What happens if you just use https://webmail.all-inkl.com/calendars/ as the configuration URL?

Is it possible to register an account for free there? It would be nice to add this server to the list of servers I'm testing the library against, but I'm not willing to pay for it.

In any case, I think the best thing to do is to downgrade this from a warning to an info message in the library. I think it's many years since this warning actually caused real-world problems.

[thogitnet]

As far as I know, there is no test access,
But I can set up access for you via my account. I will send you the information by e-mail.

[tobixen]

Thanks. I'm expecting to be extremely busy over the weekend, and probably the first days of next weeks as well, but I hope to get time to run some tests soon anyway.

[tobixen]

It appears the caldav URL can be shortened down to https://webmail.all-inkl.com/calendars/, it's not needed to include the calendar/username there. (once one is logged in, it's possible to find the calendar URL through the DAV/CalDAV protocols, and the caldav library will take care of that). I didn't investigate yet, but perhaps this is sufficient to remove the warning.

[tobixen]

The calendar server apparently does not support sync-tokens - for some reason or another, it throws "415 Unsupported Media Type" when doing a calendar.objects_by_sync_tokens(). I'm not sure if HomeAssistant is using sync tokens, but this is the most normal way of synchronizing a local copy of a calendar. Google also seems to have problems with this, ref #507. To get this to work - even to get the test suite to pass. I should fix #402 first, then I can try to make some workarounds so that calendar.objects_by_sync_tokens() will work (though in an extremely inefficient way on large calendars) also on servers not supporting sync tokens.