Read the statement by Michael Teeuw here.
MMM-CalendarExt3 not syncing automatically with icloud
-
@lightfixer2000 MMM-CalDav is creating the ics file
the node-ical problem is processing the rrule, if any
i have not seen reports of calendar troubles with the latest mm release on April 1
-
@sdetweil
A couple of questions for my understanding.
Does RRULE make calendar display repeat events?
Is CalDAV responsible for dropping the RRULE?
Is it possible to show repeat weekly events? -
@lightfixer2000
At this moment, I’m unsure the exact symptom what you said.
There is an undocumented options for more detail configuration.
Tryexpand: false,
in your module config.{ module: "MMM-CalDAV", config: { servers: [ { envPrefix: "ICLOUD_", // I assumed. serverUrl: "https://caldav.icloud.com", expand: false, // <== This. targets: [ ...
I’m not sure whether this will help yours or not. I just suspect.
PS. (more detail).
This option is related to expanding repeated events to a series of single independent events. As far as I remember, in some prior calendars, there were some issues handling repeated events by RRULE. So, I made this module to forcefully avoid that issue by default. I think recently things might be changed, so hidden optionexpand: true
might cause your symptom. -
@lightfixer2000 RRULE stands for Repeating Rule
it handles ALL the rules that make this event happen again (on some cycle)
it is optional… as some (most) events don’t repeatMMM-CalDav is processing the caldav calendar and creating the ICS file we process, using the ICAL standards.
if there is no RRULE, then it is not repeating.
the default calendar does not look at the text of the ICS file, we download it, then send it to the node-ical module to convert the text into workable objects.
it replicates the RRULE into an object in the event entry, and then we check for the RRULE object… if present we ask the RRULE library for the events that match the rules in the next year. -
-
-
@lightfixer2000
Happy to hear. I’ll reveal that option in the readme. Recently, someone else reported me the same issue, and the solution was the same. I’ll change the default value soon.