MMM-CalendarExt3Agenda on a higher screen resolution?

[rkorell]

Dear team,
I have upgraded my monitor and so I could use a higher resolution for the screen.
Coming from 1.920x1.080 I’ve tried 2.560x1.440 which really looks great.

Unfortunately MMM-CalendarExt3Agenda (which I use for calendar representation) disappears after every single restart of the mirror.
This is true for the display itself as well as for a headless (remote) VNC session.
Interesting enough the webbrowser SHOWS the module!

After some time has passed calender appears suddenly (not sure which event this triggers).

Currently I’m clueless.
(It happens earlier that MMM-CalendarExt3Agenda disappeared after a Raspberry-Reboot but a restart of MagigMirror corrects this)

Any idea/hint from the experts?

Thanks a LOT!
Regards,
Ralf

[sdetweil]

@rkorell i don’t think the screen change has anything to do with it

the Ex3 family of modules gets their data from the default calender.

if you look at the pm2 logs, you can see timestamps of when the data is sent…

the Ext3 modules, try NOT to ‘flash’ on every change, and he doesn’t KNOW how many calendars there are, or how long they will take to process…

so, he has a couple config parms that control it

waitFetch:5000 (5 seconds)

wait THAT long from first incoming block of messages, then display the calendar
anything that comes it LATER, has to wait for the refreshInterval 1800000 milliseconds
or 30 minutes… oops… a LONG time

SO, the default calendar is taking a little longer in this release(2.30.0), so I bet that calendar missed the waitFetch time limit

so I suggest looking at the pm2 logs messages and get the elapsed time from start to finish and set the waitFetch a little longer than that…

NOW, this WILL cause the calendar NOT to display AT ALL for a little longer
its a catch-22
OR change the refreshInterval to faster…

be careful, its takes work to do the refresh
and refreshing when there are no changes (once a minute say) takes system resources away from other modules…

[MMRIZE]

@sdetweil
Thanks for your explanation always.
I’ll add small message in the screen on waiting - “Waiting calendar fetch…” or something informative in the next update…

[rkorell]

@MMRIZE @sdetweil ,
thanks for this.
I’ve played around with waitFetch which doesn’t help.
But with your justification I have to investigate deeper and find the right value.

Warmest regards,
Ralf

[rkorell]

I have set refreshinterval at 180000 - 3 Minutes.
this may triggers appearance of MMM-CalendarExt3Agenda …

I’m not able to identify the startup of MMM-CalendarExt3Agenda in the log.

If I consider the difference between Mirror-startup and first calender fetching as the “right” fetching time

[2025-01-24 10:44:49.288] [LOG]   Starting MagicMirror: v2.30.0 

[2025-01-24 10:45:05.760] [INFO]  Calendar-Fetcher: Broadcasting 22 events from https://www.feiertage-deutschland.de/
[2025-01-24 10:45:06.206] [INFO]  Calendar-Fetcher: Broadcasting 21 events from https://calendar.google.com/calendar

it should be around 16,9 seconds - is this the right assumption?.

At least with

waitFetch:  17000,  //  start: 0:45:06.206 -  first calender fetch: 10:44:49.288 = 16.918 ms 

MMM-CalendarExt3Agenda appears “faster” than before …

[sdetweil]

@rkorell you want more than last calendar for wait fetch

[rkorell]

@sdetweil , sorry, I didn’t get you…
what do you mean by this?

Ralf

[sdetweil]

@rkorell you want the time til after the LAST calendar broadcast not the first

10:45:06.206

He wants to wait til ALL the data is present

So waitFetch: 19*1000

[rkorell]

@sdetweil
O.K. , sorry my fault…Wrong expression from my side “first fetch” means first complete fetch (so ALL data fetched).
In addition I accidentally switched the begin and end…
So correct view is

waitFetch:  17000,  //  MM starts: 10:44:49.288   minus  complete calender fetch at: 10:45:06.206 = 16.918 ms

Sorry for my mistake.
And thanks for your explanation!
Warmest regards,
Ralf

.

[sdetweil]

@rkorell and did that work?