ojat

Ah, good to know! I also checked the googles api response and I kinda see where the problem is coming from, second calendar has indeed +3h.

Calendar 1:
“start”: {
“dateTime”: “2024-06-17T10:00:00Z”,
“timeZone”: “Europe/Tallinn”
}

Calendar 2:
“start”: {
“dateTime”: “2024-07-13T08:30:00+03:00”,
“timeZone”: “Europe/Tallinn”
}

Might also be related to this topic:
https://stackoverflow.com/questions/25179267/why-google-calendar-api-returns-timezone-utc-although-its-incorrect

Both calendars are owned by the same client/account and api key, same time zone. Can ofcourse be a client side setup issue.

Here is a quick dirty js fix I did ( while proper solution emerges ):
https://codepen.io/Suusa-Meister/pen/QWReZbm