[BUG]: The time zone or time of alarm does not match by an hour.

[earlywaff]

Hi, I have a floating problem.
Sometimes the appointments I get set from a different time zone work an hour later than they should.
In google itself the appointment works fine, but in ical node red it comes with an hour delay.
I check the start time.
date: "10/12/22, 12:30 - 12:45 PM"
eventStart: "2022-10-12T09:30:00.000Z"
The meeting was actually supposed to take place at
date: "10/12/22, 11:30 - 11:45 AM"

But in the originalEvent: object
type: "VEVENT"
params: array[0]
start: "2022-08-09T08:30:00.000Z"
datetype: "date-time"
end: "2022-08-09T08:45:00.000Z"
dtstamp: "2022-10-12T08:37:31.000Z"

The date and time are correct here.

I can't find a clear correlation as I check subsequent appointments and there event start and originalEvent converge, but sometimes they don't and true at the start of the appointment comes with an hour delay. As if there is a problem with time zones.

Checking on Node-red 3 + Pi4
Latest version of ical.
Calendar type is ical, google.
The problem is present in all cubes from ical.

[earlywaff]

This is how I check on the bare config.

[ThomasBeavers]

I am seeing a similar issue. It appears to only happen to me for meetings that are recurring and set in a different time zone. Is it the same for you?

[ThomasBeavers]

I tracked my issue down to the processRRule method in the kalendar-events library.
If on line 218 I put:
options.tzid = null;

Then my recurring events come through with the right timestamp. It looks like it is being adjusted twice.

[naimo84]

Hey @ThomasBeavers, @earlywaff ,

is the timezone set correctly? 😉 Maybe it's the same problem like here: #149?

I don't know, if setting options.tzid = null; will break some other events from other people :(
This will take my some spare time to investigate 😉

Greets,
Benjamin

[ThomasBeavers]

I appreciate you looking into it.

I am running node-red in a docker container, but I already have the TZ env var set TZ = America/New_York