@schwarem can you look at the messages from npm start?

@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.

Thanks for the reply Sam.
I had done that which you instruct.
My problem, I just found, I had forgotten to add “.html” at the end as in “http//:192.168.xx.x:8080/remote.html” which threw this error message:- {“status”:“error”,“reason”:“unknown_command”,“info”:“original input: {}”}
Thank you.