Google Calendars Timezone Off-By-One Hour

lksdf978

@sdetweil FWIW, deleting and re-creating the event seems to work; hopefully this won’t be a recurring thing when the time changes again. :)

If you still wish to troubleshoot, I’m ready and available.

sdetweil

@lksdf978 did u save the prior event?

I would like to see the info in the ics file ( it’s just text)

I will be away from my system til next sat 14th.

lksdf978

Here is the beginning of the ics (before the first event), and one of the events that are off-by-one:

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:John Paul 
X-WR-TIMEZONE:America/New_York
BEGIN:VTIMEZONE
TZID:America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE

The following displays as 6:30am through 9:30am

BEGIN:VEVENT
DTSTART;TZID=America/New_York:20201028T073000
DTEND;TZID=America/New_York:20201028T103000
EXDATE;TZID=America/New_York:20201103T073000
RRULE:FREQ=WEEKLY;WKST=SU;UNTIL=20210601T035959Z;BYDAY=FR,MO,TH,TU,WE
DTSTAMP:20201106T114410Z
UID:DE090EB0-49C0-4E06-98AE-F2BD7386F847
CREATED:20201028T111707Z
DESCRIPTION:
LAST-MODIFIED:20201105T123002Z
LOCATION:
SEQUENCE:4
STATUS:CONFIRMED
SUMMARY:JP: Morning Meeting
TRANSP:OPAQUE
X-APPLE-TRAVEL-ADVISORY-BEHAVIOR:DISABLED
BEGIN:VALARM
ACTION:NONE
TRIGGER;VALUE=DATE-TIME:19760401T005545Z
X-WR-ALARMUID:AADE8A31-CBF0-49DD-AC18-DDEA1D7F8EA0
UID:AADE8A31-CBF0-49DD-AC18-DDEA1D7F8EA0
ACKNOWLEDGED:20201105T123002Z
END:VALARM
END:VEVENT

For comparison, here is an event I created yesterday that displays correctly:

BEGIN:VEVENT
DTSTART;TZID=America/New_York:20201105T130500
DTEND;TZID=America/New_York:20201105T140500
RRULE:FREQ=WEEKLY;WKST=SU;UNTIL=20210602T035959Z;BYDAY=MO,TH,TU,WE
DTSTAMP:20201106T114410Z
UID:3cr68na953sr1uaei12jg2p292@google.com
CREATED:20201105T171800Z
DESCRIPTION:
LAST-MODIFIED:20201105T180504Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:JP Specials Call
TRANSP:OPAQUE
X-APPLE-TRAVEL-ADVISORY-BEHAVIOR:AUTOMATIC
BEGIN:VALARM
ACTION:NONE
TRIGGER;VALUE=DATE-TIME:19760401T005545Z
X-WR-ALARMUID:28E7B417-A7FD-4035-B013-BB8DE130B977
UID:28E7B417-A7FD-4035-B013-BB8DE130B977
ACKNOWLEDGED:20201105T180504Z
X-APPLE-DEFAULT-ALARM:TRUE
END:VALARM
END:VEVENT

sdetweil

@lksdf978 great thanks. I think this is the rrrule problem. the fix is waiting to be merged.

sdetweil

@lksdf978 the latest fixes have been merged into the develop branch. you can git pull to refresh them. npm install again to get the latest node-ical update too

put that entry back in an ics file in the calendar module folder to test

lksdf978

My apologies for the late response, but I just pulled down develop, did an npm install, and reloaded MagicMirror. The issue still persists. I even went so far as deleting node_modules and reinstalling just in case. I did check the git log to be sure the changes in node_ical version was present, and it is. Any other ideas?

sdetweil

@lksdf978 still waiting for one fix to be accepted