MMM-CalendarExt3 only one calendar not updating

MMRIZE · Jan 17, 2025, 6:12 AM

maximumEntries: 4,

Hmmmm… I think you’d better increase this value more.

sdetweil · Jan 17, 2025, 3:26 PM

@oquendo421 said in MMM-CalendarExt3 only one calendar not updating:

updating without a force refresh.

have you waited over 30 minutes?

if so, the update came after the initial Ext3 wait period (he doesn’t know how many calendars will be broadcasting… (and the timing changed on the updated cal code)

and before the refreshInterval (30 minutes)

refreshing the page does NOT fetch the calendar data, but DOES cause the rebroadcast

the output on npm start will show the two messages… if using pm2 those lines have timestamps, so you can tell how long between
(I think he waits 5 seconds)

emlowe · Jan 17, 2025, 8:54 PM

I have this same problem with Ext3Agenda - manual refresh always works.

Sometimes waiting works - I’ve waited for 4 hours and suddenly have items appear. Waiting for refreshInterval doesn’t work - I can see the module/refresh with no data even though the calendar has broadcasted the items.

My current workaround is to wait for a few minutes and then use MMM-RemoteControl to connect and refresh the browser using that module, which in my experience works 100% of the time

sdetweil · Jan 17, 2025, 9:21 PM

@emlowe i don’t understand what the underlying issue is here yet.

page refresh sends the same data already available…

emlowe · Jan 17, 2025, 10:14 PM

Yea, it’s a mystery to me as well - I just know doing the manual refresh works very reliably.

I’ve had this problem on a stock pi3 b and a pi3 a+ - initially, I thought it was related to the low memory issues on the pi3 a+ - but as I update to use this new module from older ones I’ve seen it again on a stock 4gb pi3

sdetweil · Jan 27, 2025, 7:10 PM

@emlowe its clearly a timing issue… multiple people have encountered it…

I think you can change the waitFetch value up , depending on the time between fetchs as shown in the pm2 logs…

emlowe · Jan 27, 2025, 7:10 PM

Was out for a week - some more details:

Here are relevant log entries:

So that was about a minute to broadcast the first time, and then it follows the refresh interval reasonably closes.

I have the Ext3 module waitFetch set to 5 minutes (5 * 60 *1000) - well after the first broadcast. When the Ext3 module draws after 5 minutes, there is nothing in it, and it is empty with no events whatsoever. It’s like it has no data at all.

I have the Ext3 module refreshInterval set to 7 minutes (7 * 60 * 1000) - after the 7 minutes the module will refresh and it remains empty despite the calendar having done two broadcasts. The Ext3 module will remain empty for hours.

However, if I manually refresh the browser using the remotecontrol module - the Ext3 module takes 5 minutes to appear (based on waitFetch but will have all the data)

sdetweil · Jan 27, 2025, 7:30 PM

@emlowe waitfetch is from CalendarExt3 start to latest broadcast

i cannot see start but latest is at 11:01:33

find start time and subtract. add a couple seconds for variability

his default waitfetch is 5 SECONDS

Then after that, next screen refresh is at updateInterval time

also 23 events seems small, if this is mm v2.23.0, you did put on the clipping fixes right?

is this the SAME calendar broadcasting?
then to its first broadcast from ext3 start

emlowe · Jan 27, 2025, 7:54 PM

I am on the develop branch

The entire start is at 10:54:23

[2025-01-27 10:54:23.207] [LOG] Starting MagicMirror: v2.31.0-develop

I’m not sure when Ext3Agenda starts as there is no log item specific to that afaik - but I assume it’s sometime around:

[2025-01-27 10:54:26.290] [LOG] No helper found for module: MMM-CalendarExt3Agenda.

so Ext3 start is no earlier than 10:54:23 and the first broadcast was at 10:55:44 - this is much less than the 5 minutes I have manually configured for waitFetch.

(in other words, I am waiting much longer than should be needed, but it does not work unless I manually refresh)

The log at 11:01 is the second broadcast of the same calendar

I am only pulling 5 days of data and not broadcasting past events, 23 is correct.

module: "calendar",
hiddenOnStartup: true,
position: "top_left",
config: {
    broadcastEvents: true,
    broadcastPastEvents: false,
    maximumNumberOfDays: 5,
    maximumEntries: 100,
    fetchInterval: 5 * 60 * 1000,
    calendars: [
    {
        name: "family",
        URL: "<redacted>"
    }
    ]
}

module: "MMM-CalendarExt3Agenda",
position: "top_left",
config: {
    showMiniMonthCalendar: false,
    firstDayOfWeek: 1,
    startDayIndex: 0,
    endDayIndex: 0,
    calendarSet: ['family'],
    waitFetch: 5 * 60 * 1000,
    refreshInterval: 7 * 60 * 1000,
}

sdetweil · Jan 27, 2025, 8:14 PM

@emlowe ok, in the case of modules that only have a browser component ( no node helper) then
starting application message is the start time

another use just resolved the same issue w waitfetch, but he had multiple calendars
https://forum.magicmirror.builders/topic/19359/mmm-calendarext3agenda-on-a-higher-screen-resolution?page=2