MMM-CalendarExt3 only one calendar not updating

[emlowe]

Actually have to take this back. Currently testing running in server only mode and a browser so I can see the console easier

When I see in the log this line:

[2025-01-27 13:52:24.893] [INFO] Calendar-Fetcher: Broadcasting 22 events from <redacted>

I can say that modules are NOT getting any calendar notifications, despite this log entry. They are not broadcast. I added some code to Ext3Agenda to print out when it gets any notification, and it never gets any CAL items. (I see it getting DOM_CREATED, DOM_UPDATED, etc,etc)

I see in the console log the following:

sorting events count=0
slicing events total maxcount=100

which seems odd given that the helper reported broadcasting 22 events. Those items repeat in the console log , but it’s always sorting events count=0

UNTIL I refresh the browser - Now I see the Ext3Agenda module getting CALENDER_EVENTS and sorting events count=22

[emlowe]

I guess I should have run some tests with just the standard calendar module.

Now just using the standard calendar module - and it just says “Loading” despite having also printed “Broadcasting 22 events from”

[sdetweil]

@emlowe as you updated to the develop branch, did you also redo the npm run install-mm

[emlowe]

I did yes - so the current test results are this

The calendar did eventually appear - but it took quite some time - I wasn’t watching, so I don’t know when exactly - I’ll test again. But it was several minutes after the log output of “broadcasting 22 events”

[sdetweil]

@emlowe the default for ext3 is 30 mins
if missed at waitFetch

only see the timing in
pm2 log

default calendar working, right?

[emlowe]

@sdetweil No, I’m stopped testing Ext3 and I am only testing the default calendar.

it is not working - I see Loading... for some number of minutes or hours, I haven’t determined any consistency. This test run is now past 45 mins and it still says Loading… despite having broadcast the events 9 times:

[2025-01-27 14:25:24.525] [LOG]   Starting MagicMirror: v2.31.0-develop 
...
[2025-01-27 14:25:31.806] [LOG]   Create new calendarfetcher for URL ...
[2025-01-27 14:26:21.083] [INFO]  Calendar-Fetcher: Broadcasting 22 events from ...
[2025-01-27 14:32:08.812] [INFO]  Calendar-Fetcher: Broadcasting 22 events from ...
[2025-01-27 14:37:55.863] [INFO]  Calendar-Fetcher: Broadcasting 22 events from
[2025-01-27 14:43:42.948] [INFO]  Calendar-Fetcher: Broadcasting 22 events from
[2025-01-27 14:49:30.144] [INFO]  Calendar-Fetcher: Broadcasting 22 events from 
...
[2025-01-27 15:12:37.552] [INFO]  Calendar-Fetcher: Broadcasting 21 events from 

still says Loading ... - if I refresh the browser page - then they all appear immediately

[sdetweil]

@emlowe can you extract those events out to a file

curl -sL theurl >somefile.txt
and share the file and your calendar config in an email to me
same userid at gmail

so i can look at it

one other thing is open the developers window console tab
ctrl-shift-i, select the console tab
or do
npm run start:dev

and see if there are any errors
the browser side broadcasts so it GOT the events block
then it processes for the ui

[emlowe]

@sdetweil No errors in the console log

If I wait long enough where this seems anywhere between 15min to an hour or more, they do appear without a manual refresh.

maybe it’s a complexity issue - when I curl the calender link (it’s a google private ICS link) - the resulting file is 4.8MB - I imagine parsing that is somewhat time-consuming

[sdetweil]

@emlowe yes, and new code takes longer than old with lots of events

what is the calendar refreshinterval

[emlowe]

@sdetweil You mean fetchInterval: 5 * 60 * 1000?

the calendar module doesn’t have refreshinterval does it?

[sdetweil]

@emlowe fetchInterval is same

[emlowe]

I added various log outputs to node_helper.js and calendar.js

node_helper is sending the socket notification for CALENDAR_EVENTS
this is not received by the front end code in calendar.js

I don’t know what happens to it, but I added logging to print out in calendar.js whenever the socketNotificationReceived handler is called and it doesn’t print.

(unless I refresh the page - at which point it does)

[emlowe]

Something even stranger - if I immediately refresh the page it also works. Here I mean is:

npm run server
got to browser and bring up host:8080
calendar will say “Loading” for a very long time
(despite the events getting broadcast)

But if I :
npm run server
go to browser and bring up host:8080
calender says “Loading”
Refresh the page immediately
calendar says “Loading”
calendar will immediately show the events as soon as the events are broadcast

[sdetweil]

@emlowe oh, “cool” ugh, i opened an issue about that last year

just reopened
https://github.com/MagicMirrorOrg/MagicMirror/issues/3380

can you add the contents of your post in an comment
actually this one
https://forum.magicmirror.builders/topic/19345/mmm-calendarext3-only-one-calendar-not-updating/30?page=3#

[MMRIZE]

Hmmm… I was in our traditional ceremony with my family - a lunar new year, so I couldn’t catch this post. Sorry.
Anyway, this symptom is not my module’s fault, right? There were some reports similar to this, but not figured out.

[sdetweil]

@emlowe can you try this , configure bigger socketio buffer
see the post in the issue
https://github.com/MagicMirrorOrg/MagicMirror/issues/3380#issuecomment-2645778523

[sdetweil]

ok, that didnt help