Read the statement by Michael Teeuw here.
MMM-CalendarExt3 not loading events
-
@carefreepineappl CalendarExt3 depends on the default calendar module to read and parse the ICS event data and broadcast it to other interested modules.
ext3 does NOT read the ICS directly
so, the calendars:[] list needs to be moved to the default calendar module. you can keep the default from showing by commenting out it’s position config option
-
@sdetweil that did it. thank you! sorry, I misread the example in the MMM-CalendarExt3 repo, it clearly shows configuration of the calendar module.
-
@sdetweil
ok, so after I got the example ICS working and displaying, I swapped out the URL link to my private google calendar, which I confirmed is available through an incognito window.The logs appear to show its downloading and attempting to parse the data, there are no errors, but it doesn’t display any events on the calendar.
{ module: "calendar", config: { broadcastPastEvents: true, calendars: [ { fetchInterval: 7 * 24 * 60 * 60 * 1000, symbol: "calendar-check", url: "https://calendar.google.com/calendar/ical/<redacted>/basic.ics", name: "google", color: "red" } ], maximumEntries: 5 } }, { module: "MMM-CalendarExt3", position: "bottom_bar", title: "", config: { mode: "week", instanceId: "basicCalendar", maxEventLines: 5, firstDayOfWeek: 7, weekIndex: 0, weeksInView: 3, calendarSet: ['google'] } }
Im looking for
error
in the logs, are there any other terms I should search for?pi@rpi2o1:/opt/MagicMirror $ cat log.txt | grep -i error pi@rpi2o1:/opt/MagicMirror $
I see entries getting processed
pi@rpi2o1:/opt/MagicMirror $ cat log.txt | grep -i "processing entry" | wc -l 398
Here’s an example event
[05.02.2024 14:31.15.068] [DEBUG] Processing entry... [05.02.2024 14:31.15.072] [DEBUG] Event: {"type":"VEVENT","params":[],"start":"2024-02-07T19:30:00.000Z","datetype":"date-time","end":"2024-02-07T22:00:00.000Z","dtstamp":"2024-02-05T19:30:09.000Z","uid":"<redacted>@google.com","created":"2024-01-30T15:39:19.000Z","lastmodified":"2024-01-30T17:02:11.000Z","sequence":"1","status":"CONFIRMED","summary":"Coco senior exam 3:10","transparency":"OPAQUE","method":"PUBLISH"} [05.02.2024 14:31.15.074] [DEBUG] start: Wed Feb 07 2024 14:30:00 GMT-0500 (Eastern Standard Time) [05.02.2024 14:31.15.076] [DEBUG] end:: Wed Feb 07 2024 17:00:00 GMT-0500 (Eastern Standard Time) [05.02.2024 14:31.15.078] [DEBUG] duration: 9000000 -- [05.02.2024 14:31.15.090] [DEBUG] start offset=0 [05.02.2024 14:31.15.092] [DEBUG] start date/time w tz =Wed Feb 07 2024 14:30:00 GMT-0500 (Eastern Standard Time) [05.02.2024 14:31.15.095] [DEBUG] event date=Wed Feb 07 2024 14:30:00 GMT-0500 (Eastern Standard Time) [05.02.2024 14:31.15.097] [DEBUG] event offset=0 hour=19 event date=Wed Feb 07 2024 14:30:00 GMT-0500 (Eastern Standard Time) [05.02.2024 14:31.15.099] [DEBUG] adjustHours=0
I tried going back to the prior parser, but there wasn’t a change for the google calendar. I tried changing the ICS back to the holidays ICS with the new parser, and that no longer showed any events either.
pi@rpi2o1:~$ cd /opt/MagicMirror npm install node-ical@0.16.1 pi@rpi2o1:~ $ cat /opt/MagicMirror/package.json | grep node-ical "node-ical": "^0.16.1",
tried going to the latest version of node-ical to at least get back to where I was and I still dont see any events even with the holidays ICS that was working.
pi@rpi2o1:~$ cd /opt/MagicMirror npm install node-ical@0.17.2
Log shows entries processed even identifying an upcoming one
[05.02.2024 15:42.40.179] [DEBUG] [weather.js:112:11] First upcoming event with location: { title: "Presidents' Day", startDate: '1676869200000', endDate: '1676955599999', fullDayEvent: true, location: 'United States', geo: false, description: "Visit https://calendarlabs.com/holidays/us/?utm_source=calendarlabs&utm_medium=web&utm_campaign=ical to know more about Presidents' Day. \n" + '\n' + ' Like us on Facebook: http://fb.com/calendarlabs to get updates', today: false, dayBeforeYesterday: false, yesterday: false, tomorrow: false, dayAfterTomorrow: false, symbol: [ 'fas fa-fw fa-calendar-check' ], calendarName: 'google', color: 'red' }
Im seeing new events and a total event count
pi@rpi2o1:/opt/MagicMirror $ cat log.txt | grep "Create new" [05.02.2024 15:42.34.945] [LOG] Create new calendarfetcher for url: https://ics.calendarlabs.com/76/82950923/US_Holidays.ics - Interval: 604800000 pi@rpi2o1:/opt/MagicMirror $ cat log.txt | grep "Calendar-Fetcher:" [05.02.2024 15:42.39.116] [INFO] Calendar-Fetcher: Broadcasting 24 events from https://ics.calendarlabs.com/76/82950923/US_Holidays.ics.
I hope i’m doing something stupid as per usual.
-
@carefreepineappl please go back to
node-ical@0.16.1
-
@sdetweil all set
pi@rpi2o1:/opt/MagicMirror $ npm install node-ical@0.16.1 pi@rpi2o1:/opt/MagicMirror $ cat /opt/MagicMirror/package.json | grep node-ical "node-ical": "^0.16.1",
Before attempting the google calendar again, i’m going back to trying to get the US holidays calendar working.
Unfortunately i’m still not seeing presidents day appear on the calendar.
-
@sdetweil if you’re interested, here’s the log file
https://drive.google.com/file/d/119GJ_HUliObRNVHb5iQkxr8VZX92Yl-_/view?usp=drive_linkEDIT: for some reason the presidents day event finally popped up. I wasnt watching it to see how long it took to populate, but it had to have been a little while.
I’ll test again to see if I can get a time frame. I was watching the logs and when the events were finished processing, I assumed they should be displayed. Is that not the case?
-
@carefreepineappl read this and following posts from Ext3 author about how ext processes
-
@sdetweil thanks, I read through it and I understand the time needed to download and parse the data, but what i’m seeing is after its done, it takes 10 minutes for the events to show up. And this is just for the US holidays calendar, which is fairly small.
I’m going to try my google calendar and see if it even populates after awhile.
-
@carefreepineappl note that the default fetch delay for the default calendar is quite long… 7 days… because all the mm systems polling the calendar labs urls were causing them problems
-