Read the statement by Michael Teeuw here.
Calendar Module not working with Google Calendar
-
Re: Default Modules
Hello. I recently updated to the latest MagicMirror build and my Google Calendar (in ical format) stopped loading. I tried to reset the Private ical link. I also tried the public ical link, but it still will not load. Anyone have any suggestions? I can load the config.js file (redacted) if that will help -
@redink yes, new rrule is having trouble…
lets go back to the prior parser
cd ~/MagicMirror npm install node-ical@0.16.1
-
@jott0204 yes config, url xxx out
also please show the messages where you do npm start
-
I have a very similiar problem. I use two calendar modules, one with dates from the local waste pickup service and another one with multiple google calendars. The waste calendar works fine (so nothing with the module), but google gives errors. I copied out two of the google-calendars:
[03.01.2024 11:05.10.477] [ERROR] Calendar Error. Could not fetch calendar: https://calendar.google.com/calendar/ical/XXXXX/basic.ics RangeError: Invalid time value at Date.toISOString (<anonymous>) at /home/pi/MagicMirror/modules/MMM-MyCalendar/calendarutils.js:314:28 at Array.forEach (<anonymous>) at Object.filterEvents (/home/pi/MagicMirror/modules/MMM-MyCalendar/calendarutils.js:142:24) at /home/pi/MagicMirror/modules/MMM-MyCalendar/calendarfetcher.js:74:29 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) [03.01.2024 11:05.11.076] [ERROR] Calendar Error. Could not fetch calendar: https://calendar.google.com/calendar/ical/XXXXX/basic.ics RangeError: Invalid time value at Date.toISOString (<anonymous>) at /home/pi/MagicMirror/modules/MMM-MyCalendar/calendarutils.js:314:28 at Array.forEach (<anonymous>) at Object.filterEvents (/home/pi/MagicMirror/modules/MMM-MyCalendar/calendarutils.js:142:24) at /home/pi/MagicMirror/modules/MMM-MyCalendar/calendarfetcher.js:74:29 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
I don’t know what
invalid time value
means, maybe someone can help -
@AnduriI you need the latest mm version which has a fix for the isostring problem
-
@sdetweil what do you mean with latest mm version? I did
git pull && npm install
, so I should have the latest… -
@AnduriI can u chedck the actual version u have
cd ~/MagicMirror grep version package.json
-
/MagicMirror $ grep version package.json "version": "2.26.0",
-
@AnduriI bizarre.
can u turn on debug in config.js
add
,"DEBUG"
to the loglevel: list
then let’s use non pm2 to capture the info
pm2 stop all cd ~/MagicMirror npm start >somefile.txt 2>&1
wait til u think the error occurs
ctrl-qto top mm
then look at the somefile.txt
search for the isostring
you should see dates=
for each eventthe problem was the rule.between function which calculates the repeating events would return junk
I put in a filter to remove the junk.anyhow, then remove the DEBUG
thing from config.jsand you can use pm2 to restart mm til we figure it out
if u can, send the somefile.txt to me via email
my userid here at gmail -
@sdetweil wow I was not aware of all old events also being sent and parsed… from 5+ years ago. That’s a lot of entries… (more than 1500 only for my main calendar)
I sent the log via eMail to you. -
@AnduriI yes, the ics holds all that junk