Some how my HASS Calendar Addon configuration does not give me a calendar sensor with Synology Calendar.
The caldav-server I try to connect to is a Synology Calendar implementation. It supports synchronization with CalDAV clients such as Thunderbird, macOS, and iOS that are compatible with the CalDAV protocol. I tried both URL-strings for Thuinderbird and iOS.
The iOS integration URL-string works fine in HA Calender with de HA standard CalDAV integration and with CalDAV Synchroniser in Outlook365 .
I hope someone out here has experience with this Synology Calendar environment and how to connect to HASS Calendar Addon.
With this config in the HASS Calendar addon I do not get the sensor.tonneke in Development Tools > States
- calName: tonneke
calType: caldav
username: "!secret calendar_caldav_username_ton"
password: "!secret calendar_caldav_calendar_caldav_password_ton"
caldavUrl: http://xxx.xxx.xxx.xxx:20002/caldav.php/ton/
Overall HA Log does not show sensor.tonneke either.
HASS Calendar Log has no errors:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/00-banner.sh
-----------------------------------------------------------
Add-on: Hass Calendar Addon
Addon to consume caldav and google calendars and make calendar events available as sensordata in Home Assistant.
-----------------------------------------------------------
Add-on version: 0.300
You are running the latest version of this add-on.
System: Home Assistant OS 9.3 (amd64 / generic-x86-64)
Home Assistant Core: 2022.11.2
Home Assistant Supervisor: 2022.10.2
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started