Closed RichJeanes closed 2 years ago
Is there any possibility to set up a testing account on the Synology server that I could use for running the test code, pinpointing the problem and test a bugfix or workaround?
Gotcha! (sorry for spending so long time before looking properly into this).
Synology suggests to use the URL path /caldav/username@ldap.example.com
The first thing I did was to shorten it down to just /caldav/
However, that also didn't solve the problem. I went in with the debugger, and found that the URL reported back from the server is /caldav.php/ !
Changing the URL in the config to end with /caldav.php seems to resolve the traceback above.
This is an issue at the server side .... but the error handling on the client side is also rather lacking.
My philosophy has all the time been that the library should work around slightly wrong configuration as well as common server compatibility issues, so I will conside rsome workaround in the client library.
(and also, when changing the config above, I ran into 405 errors from the server. I hope to get more time to look into it today)
Latest version of master should work with your Synology.
Except for the .php-issue, it seems to be a good server, quite few incompatibility issues found (one minor failure in the sync token test, but that's not a breach of the RFC and won't cause problems. Some problems when doing date search for tasks (VTODO), but almost all server implementations fail that test).
I am running Synology Calendar 2.4.5-10930 and Home Assistant 2022.6.0. When attempting to connect my calendar, Home Assistant doesn't load any calendars and the following errors appear in the logs. The server URL in the configuration is
https://<server>/caldav/<user@ldap>
.Usernames and server names have been redacted to "\<name>". The configuration does not include any "<" or ">" symbols.