MMM-CalendarExt3Agenda Only loading a few items.

[sdetweil]

@schwarem can you show the messages from npm start where the deault calendar module says how many events it broadcast.

like

Calendar-Fetcher: Broadcasting 11 events from https://ics.calendarlabs.com/76/mm3137/US_Holidays.ics.

[schwarem]

@sdetweil

Below is the screenshot. It is loading everything, but not displaying in CalendarExt3. I also noticed in the debug console there was the message below. I don’t know what it means.

[sdetweil]

@schwarem i erased your image, one line at top had full url, please fix and then edit post and add it back in

did you do

npm install

in the module folder after git clone??

[schwarem]

@sdetweil Yes. and I just ran it again.

[sdetweil]

@schwarem it should have done the extension install too

[MMRIZE]

@schwarem
Only events from some specific calendars seem being missed.
Usually, that case happens when CX3* will be displayed before all the calendars’ fetching is completed.
Give enough waitFetch of CX3*'s config. By default, it would be 5000ms(5 sec). I think 10_000 or something may be enough for you.
Generally, 5 seconds is enough for most of the environment, but in some low-powered devices, too many calendars or events, slow internet speed or many various other reasons could make the case.

[MMRIZE]

@schwarem said in MMM-CalendarExt3Agenda Only loading a few items.:

@sdetweil

Below is the screenshot. It is loading everything, but not displaying in CalendarExt3. I also noticed in the debug console there was the message below. I don’t know what it means.

Not error, just info. You can ignore it.

[schwarem]

@MMRIZE

Increasing the WaitFetch worked. Thanks to everyone for the suggestions.

By the way, I have a Raspberry Pi 4 B with 1 gb of RAM which had enough power for CalendarExt2.

[MMRIZE]

@schwarem
That’s not your or your RPI’s fault. :)

With your previous log image, at least 7 calendars had to be parsed. The first calendar (12 events) was fetched on 11:06:27, and the last calendar(93 events) was fetched on 11:06:40. These 7 calendars need almost 13 seconds to parse completely.

But CX3* would appear after 5 seconds(by default) from the first fetching. Nobody can’t foresee when the last calendar will finish the fetching (or even whether it is complete or not). So CX3* will wait a few seconds and then show only the events from the current aggregated regardless of whether some unfetched calendars remain.

CX2 parsed events of the calendar by itself so it could know whether all events were fetched or not.(At least I made so), but CX3 doesn’t parse the calendar, only using the feed from another module. That’s the difference.

No worry. Until the next cycle(defined by refreshInterval), the unfetched calendars would be fetched until then. In the following refreshInterval, your missing events will be shown adequately.

Or, increase waitFetch to wait more seconds for more calendars to fetch.