Integración comunitaria CalDAV, gratuita y de código abierto

Sync your CalDAV calendars (Google, iCloud, Nextcloud, Fastmail…) into Gladys.
La documentación de esta integración la escribe su autor y, por ahora, solo está disponible en inglés.
This integration copies your CalDAV calendars (Google, iCloud, Nextcloud, Fastmail, Infomaniak, Baïkal, Radicale, SOGo, Synology Calendar…) into the Gladys calendar. The events show up in the calendar view, can trigger scenes ("an event is coming") and are known by the assistant.
The sync is one way: Gladys reads your CalDAV server and never writes to it. An event created or edited in Gladys on a synced calendar is not sent back to the server.
Enable the integration for your account
Every Gladys user enables the integration for themselves: your calendars are personal data, nothing is synced until you enable it.
- Open the CalDAV integration, Configuration tab.
- In the My calendars block, fill in:
- your provider: Google, iCloud, Fastmail and Infomaniak need no URL;
- otherwise ("Other" provider), the CalDAV server URL (see the table below) — a URL typed here is always used, whatever the provider;
- your username;
- your password — use an app password when your provider offers one.
- Click Enable. Your calendars show up a few seconds later.
| Provider | Server URL | Notes |
|---|---|---|
in the list (https://www.google.com/calendar/dav) | Gmail address + app password (2-Step Verification must be on) | |
| iCloud | in the list (https://caldav.icloud.com) | Apple ID + app-specific password (mandatory) |
| Fastmail | in the list (https://caldav.fastmail.com) | App password with CalDAV access |
| Infomaniak | in the list (https://sync.infomaniak.com) | Infomaniak login (not the email address) + app password |
| Nextcloud | https://cloud.example.com/remote.php/dav | App password: Settings → Security |
| Framagenda | https://framagenda.org/remote.php/dav | App password: Settings → Security |
| Baïkal | https://dav.example.com/dav.php | |
| Radicale | https://dav.example.com (or http://ip:5232) | |
| SOGo | https://mail.example.com/SOGo/dav | |
| Synology | https://nas.example.com:5001/caldav |
The integration discovers your calendars from that URL (principal and calendar home): no need to enter the address of each calendar. Task lists are ignored.
Subscribed calendars (webcal)
The calendars your account is subscribed to by URL (public holidays,
sports fixtures, school timetable… — webcal:// or https:// addresses) are
synced too, when your server keeps the subscriptions in your account:
Nextcloud, iCloud, SOGo do. They show up in Gladys like your other calendars,
with the same toggles.
- The integration reads the feed itself, at its address: the feed must be reachable from your Gladys. It is read without your CalDAV credentials.
- A feed is read at every sync, but written to Gladys only when its content changed.
- A subscription that only exists in a client application (a calendar subscribed in Thunderbird or on a phone only) is not on the server: the integration cannot see it.
Choose what to sync and share
Every synced calendar shows up in Gladys with two toggles:
- Sync — switch it off to skip a calendar: its events are removed from Gladys. Switched back on, it is refilled by the next sync.
- Share — a calendar starts private. Shared, it becomes visible to the whole household, and usable by the scenes.
The name, description and color of a calendar follow the server's.
Settings (administrator)
These settings apply to every user:
- Sync interval — every 15 minutes by default (from 5 minutes to 24 hours).
- Days of history — past events older than 30 days (by default) are not synced.
- Days ahead — 365 days by default (up to 730): recurring events are expanded up to that horizon.
- Detailed logs — off by default. Switched on, every CalDAV request and its result is written to the integration logs (see Troubleshooting).
The Sync now button reads every account right away and shows how many calendars and events were synced.
Good to know
- An event deleted on the server disappears from Gladys at the next sync; a calendar deleted on the server is deleted from Gladys with its events.
- Recurring events (exceptions and moved occurrences included) are expanded into individual occurrences.
- Cancelled events (
STATUS:CANCELLED) are not imported. - A "floating" time event (without time zone) is read as UTC.
- Gladys limits: 50 calendars per user (subscriptions included), 10,000 events per calendar; texts too long are truncated.
- Disabling the integration for your account deletes your synced calendars from Gladys (they stay untouched on the server).
Troubleshooting
The Configuration screen shows how many accounts fail. The most common causes:
- Wrong URL — check the URL in a CalDAV client (Thunderbird, DAVx⁵); try
the root URL of the server, the
/.well-known/caldavdiscovery is automatic. - Credentials refused — with two-factor authentication enabled, an app password is required.
- Self-signed certificate — the server must present a valid HTTPS certificate (or be reached over HTTP on the local network).
- "N object(s) the server could not return were skipped" — the server lists an event it then fails to send (Google does it on some calendars). The rest of the calendar is synced; only those objects are missing.
- "feed …: 404 Not Found" (or "not an iCalendar feed") — a subscribed calendar whose address no longer works: check it in your calendar application. The error names the feed's host only, its full address may hold a private key.
The administrator finds the details of the errors in the integration logs (the integration page, supervision tab). Passwords never show up there.
To report a problem, switch on Detailed logs in the settings, click Sync now, copy the logs, then switch the option off: they show each step of the discovery and every request sent to the server, with the calendar URLs (often your email address) — review them before posting them publicly.
Parámetros de configuración
Estos son los parámetros que CalDAV te pide en su pantalla de configuración en Gladys.
| Parámetro | Tipo | Obligatorio | Descripción |
|---|---|---|---|
| How it works | section | No | Each user enables the integration for themselves in the "My calendars" block below, with their own CalDAV server and credentials. Their calendars and events are copied into Gladys, one way: Gladys never writes to the CalDAV server. The settings here apply to every user. |
| Sync interval (minutes) | number | No | How often each user's calendars are read from their CalDAV server. |
| Days of history | number | No | Past events older than this are not synced. |
| Days ahead | number | No | Horizon of the sync: recurring events are expanded up to this many days ahead. |
| Detailed logs | boolean | No | Writes every CalDAV request and its result to the integration logs, to diagnose a calendar that fails to sync. They hold the calendar URLs: switch it off once done. |
Cómo instalar CalDAV en Gladys
- En Gladys, abre Integraciones: CalDAV aparece en el catálogo junto a las integraciones nativas, con una insignia de comunidad.
- Haz clic en Instalar. Gladys descarga la imagen Docker (
ghcr.io/bertrandda/gladys-caldav-sync:1.1.0), la ejecuta en un entorno aislado del núcleo y genera la interfaz de la integración (dispositivos, descubrimiento y configuración). - Abre la pantalla de Configuración de la integración, rellena los parámetros y guarda.
- También puedes instalarla directamente desde la URL de su repositorio: https://github.com/bertrandda/gladys-caldav-sync.
CalDAV requiere Gladys >=5.2.0. El catálogo de Gladys se actualiza cada hora, así que una nueva versión está disponible como máximo una hora después de publicarse.
¿Todavía no usas Gladys? Es gratuito y de código abierto: sigue la guía de instalación para empezar.
Sobre las integraciones externas
CalDAV es una integración externa: una integración comunitaria empaquetada como contenedor Docker y publicada en GitHub. Gladys la instala con un clic y la ejecuta en un entorno aislado del núcleo. La publica y mantiene bertrandda, no el equipo principal de Gladys.
- Explorar todas las integraciones, nativas y de la comunidad
- Crear y publicar tu propia integración externa
- Código fuente en GitHub — fuente de esta documentación