MMM-CalendarExt3 BST Timezone issue

[shall_]

I currently have an issue with MMM-CalendarEXT3 where since we have switched to british summer time (BST) Timezone, now all my all and multi day calendar events roll into the following day, i had the same issue last year, my only resolution was to switch back to DST timezone.

I have trawled through the internet looking for a solution but i can’t find one. I have check my calendar timezone matches the Pi timezone. Plus tried various updates.

a lot of the “solutions” I have seen required hiding the end date, which isn’t really a fix and wouldn’t work for my situation.

Has anyone had this issue and found a good solution to this?

[shall_]

I have managed to fix my issue, it seems the event transformer I was using (to colour mt events) may have been contradicting the fix.

I removed the following from my event transformer which fixed the issue!

  e.startDate = new Date(e.start?.date || e.start?.dateTime).valueOf()
  e.endDate = new Date(e.end?.date || e.end?.dateTime).valueOf()

[sdetweil]

@shall_ i have not heard of this problem before.

can you provide the tinezone and a calendar entry from the ics file

to get the ics file take yiur calendar_url and do

curl -sL calendar_url >xxx.ics

then edit xxx.ics (its just text)

and find a BEGIN:VEVENT… END:VEVENT

That has the matching date/time info

xxx out any private data, but dont change anything else

post back here

[shall_]

@sdetweil said in MMM-CalendarExt3 BST Timezone issue:

curl -sL calendar_url >xxx.ics

Thanks for the reply. I am having trouble getting the ics file.
i have ran the command in the terminal, all it does is return to the empty command line. is this supposed to open something?

@sdetweil said in MMM-CalendarExt3 BST Timezone issue:

then efit xxx.ics (its just text)

I am not sure what you mean by this? Apologies i am still fairly green on this side of things.

[sdetweil]

@shall_ sorry efit was edit, new phone and thumb havent become friends yet

by default most linux commands produce NO output when successful. they were designed back
in the teletype terminal world, where every character took a long time.

so, this means the ics file was downloaded as requested

[shall_]

@sdetweil
Ok that makes sense. I have found the generated ics file, however it has a 0 file size and when I open it with text editor it is just an empty file. The file type is listed as “Outlook.File.ics.15”

I am using google calendar urls, not sure if that makes any difference? i have tried 3 different urls that I use with the module.

[sdetweil]

@shall_ weird. are using the same url in mm config?

you might also try it in a browser on your pc. it should download the ics (downloads folder)

[shall_]

@sdetweil yes i copied each url straight from my config file.
I tried opening them in the browser, it downloaded as described but is still an empty file.

I found a work around by just downloading the ics right from google calendar, this is an example of one of the events. with the timezone tied in.

RPi timezone is set to GMT +1 Europe/London (BST)

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:Work
X-WR-TIMEZONE:Europe/London
BEGIN:VEVENT
DTSTART;VALUE=DATE:20170626
DTEND;VALUE=DATE:20170701
RRULE:FREQ=WEEKLY;WKST=MO;UNTIL=20190331T235959Z;INTERVAL=2;BYDAY=MO
DTSTAMP:20240403T224236Z
UID:15dcXXXXXXujb@google.com
CREATED:20171216T163405Z
LAST-MODIFIED:20190330T214112Z
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Earlies
TRANSP:TRANSPARENT
END:VEVENT

[shall_]

@sdetweil this is another entry added this week with the issue.

BEGIN:VEVENT
DTSTART;VALUE=DATE:20240402
DTEND;VALUE=DATE:20240403
DTSTAMP:20240403T224236Z
UID:70rjap1gXXXXX6oo68db56o@google.com
CREATED:20240402T105500Z
LAST-MODIFIED:20240402T105500Z
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:12 hours 
TRANSP:OPAQUE
END:VEVENT

[sdetweil]

@shall_ ok. weird. anyhow

we dont process anything other than vevents. so the garbage at the top which has the x-wr timezone, we dont see.

so the calendar will be processed in the current system timezone.

if you want to see the debug of processing, add the ,“DEBUG” to the end of the logLevel property in config.js

and then start mm like this

npm start >somefile.txt 2>&1

wait til the cal is up, then ctrl-q quit mm and examine the somefile.txt

[sdetweil]

@shall_ because there is no timezone specified on the entry, it will be processed in the current system timezone