Read the statement by Michael Teeuw here.
MMM-CalendarExt3 not picking up calendar set from default calendar module
-
Hi team,
First timer here, please help. Following is my config file. The CalendarExt3 and CalendarExt3Agenda modules are not picking up the calendars on the default calendar modules. It loads up correctly in the calendar module. Any help will be apprieciated.
{ module: 'MMM-CalendarExt3', position: 'bottom_bar', config: { mode: 'day', instanceId: 'myCalendar', locale: 'en-US', firstDayOfWeek: 0, weeksInView: 1, animationSpeed: 0, fontSize: '25px', calendarSet: [ 'family', 'us_holiday' ] } }, { module: 'MMM-CalendarExt3Agenda', position: 'top_left', header: 'My Agenda', config: { instanceId: 'myCalendar', locale: 'en-US', firstDayOfWeek: 1, endDayIndex: 5, calendarSet: [ 'family', 'us_holiday' ] } }, { module: 'calendar', position: 'hidden', config: { instanceID: 'myCalendar', broadcastPastEvents: true, calendars: [ { url: 'webcal://www.calendarlabs.com/ical-calendar/ics/76/US_Holidays.ics', name: 'us_holiday', color: 'skyblue', broadcastPastEvents: true, maximalNumberOfDays: 365, maximumEntries: 100 }, { url: '****', name: 'family', color: 'red', broadcastPastEvents: true, maximalNumberOfDays: 365, maximumEntries: 100 } ] } },
-
@st98325 so first thing is
mode :‘day’
in which it displays ONE day only
default is yesterday (dayIndex:-1)weeksInView is ignored in mode:day
second, how long did you wait?
the default calendar module broadcasts events independently for each configured calendarthe ext3 modules try not to flash the screen with redrawing on each blob of events arriving
there are two config parms that control this
waitFetch
refreshIntervalrefreshInterval is how often the output is redrawn,
whatever events have arrived since the last refresh will be drawn now. the default is 30 minutesbut you dont wait to wait at startup for the first draw
you want it NOW
but ext3 doesnt known WHEN the events will be coming from the default calendar module.
so, after waitFetch time (default 5 seconds) it draws the first time. even if NO events have arrived yet
and then it waits refreshInterval time to draw the next timeso, if the calendar takes more time to process, the events will arrive AFTER the 1st draw, but before the 2nd
so, i suggest increasing the waitFetch time to one minute
60000 , and reducing the refreshInterval to 2 minutes (120000)
to verify it worksthen tuning those as needed
if you use pm2 to launch MagicMirror, then the log output (pm2 logs) has timestamps, where you can calculate the tine for calendar processing, and set waitfetch just a little longer.
side effect of longer waitFetch is that the first draw waits that long. so no calendar output
-
@sdetweil This works and I get the logic now… thanks a ton!!!
-