Calendar has stopped working. Updated to latest version. Have been using Outlook Calendar for a few years with no issues. Calendar is stuck on “Loading…”

Error messages:

[2022-09-18 17:35:15.966] [ERROR] No toISOString function in curr.start //Microsoft/Utc:20220930T133000
[2022-09-18 17:35:15.967] [ERROR] No toISOString function in curr.recurrenceid //Microsoft/Utc:20220930T133000
[2022-09-18 17:35:15.972] [ERROR] No toISOString function in curr.recurrenceid //Microsoft/Utc:20221001T133000
[2022-09-18 17:35:17.277] [ERROR] Whoops! There was an uncaught exception…
[2022-09-18 17:35:17.278] [ERROR] TypeError: event.start.getFullYear is not a function
at /home/pi/MagicMirror/modules/default/calendar/calendarfetcher.js:285:33
at Array.forEach (:null:null)
at Request._callback (/home/pi/MagicMirror/modules/default/calendar/calendarfetcher.js:91:25)
at Request.self.callback (/home/pi/MagicMirror/node_modules/request/request.js:185:22)
at Request.emit (events.js:210:5)
at Request. (/home/pi/MagicMirror/node_modules/request/request.js:1154:10)
at Request.emit (events.js:210:5)
at Gunzip. (/home/pi/MagicMirror/node_modules/request/request.js:1076:12)
at Object.onceWrapper (events.js:299:28)
at Gunzip.emit (events.js:215:7)
at endReadableNT (_stream_readable.js:1183:12)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

Thoughts?

@sdetweil You’re right. Was totally on my end. Didn’t realize I had a file that was preventing the upgrade. After upgrading, works like a charm. Thanks for your help as always.

@sdetweil

As you can see, this event is scheduled to begin at 10:00am but is actually displaying on the calendar as starting at 5:00am.

BEGIN:VEVENT
UID:00D4F0F7-BF5A-45C4-B92F-41B8C771E111
SUMMARY:TEST
DTSTART;TZID="(UTC-05:00) Eastern Time (US & Canada)":20201123T100000
DTEND;TZID="(UTC-05:00) Eastern Time (US & Canada)":20201123T103000
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20201122T204236Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT

@sdetweil I’m still on the branch origin/develop and it says I’m up to date.

@sdetweil Not sure what changed but the times are now displaying as starting 5 hours before they are supposed to.

@sdetweil The ics file is generated with Microsoft Exchange Server 2010.

UID:55CA88B7-8EF2-4AB5-AD4E-557F33C33FBE
SUMMARY: TEST
DTSTART;TZID="(UTC-05:00) Eastern Time (US & Canada)":20201028T133000
DTEND;TZID="(UTC-05:00) Eastern Time (US & Canada)":20201028T150000
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20201015T165939Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT

@sdetweil Thank you for all your help. Unfortunately, it still has the timezone issue i.e. all times displayed UTC-4 (I’m in EDT). It appears that the times that are pulled from Outlook are not recognized as already in EDT and are being treated as UTC (hence the additional -4 hours). I’ll keep working on it.

@sdetweil Thank you. I have updated to v2.13.0 and still have the issue. Sorry for the dumb question, but how do I pull only from the develop branch?

Not sure if anyone else is having this problem, but the start times in my calendar are different from my Outlook entries. Usually, they are off by 4 hours (I’m in EDT). The only time it displays the correct time is when the calendar entry was entered in UTC. This seems to be a new issue as it was working previously. Thoughts?