core icon indicating copy to clipboard operation
core copied to clipboard

Google calendar not adjusting the event time to dst change

Open bbrowaros opened this issue 2 years ago • 1 comments

The problem

After DST change time google calendar did not update the corresponding time. The events displayed in google calendar integration are -1h to actual event in google calendar. Time of the system is displayed correctly.

What version of Home Assistant Core has the issue?

2022.11.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Google Calendar

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

no logs error just a interpretation error.

Additional information

No response

bbrowaros avatar Nov 06 '22 09:11 bbrowaros

Came here to report this bug. Just experienced its effects this morning. I'm running the home assistant container in docker on Ubuntu 20.04

SteveDinn avatar Nov 06 '22 14:11 SteveDinn

Curiously, as I did experience this bug this morning, this afternoon the times on events seem to be correct.

I don't know if noon specifically has anything to do with it, but today being the day that the time changed, an event scheduled for 11am came into HA incorrectly as 10am, but an event scheduled for 3:45pm is correctly showing in HA as 3:45pm.

I am in Atlantic Time, yesterday UTC-3, today UTC-4.

SteveDinn avatar Nov 06 '22 18:11 SteveDinn

If it helps you debug this issue, I too am getting the issue from the UK. We changed from UTC+1 to UAT+0 on the 30th of October. My events are coming through with the wrong time, but only for repeating events. Single events seem to be unaffected. E.g I have a dentist event tomorrow, that was created in september which shows the correct time, but a repeating event is showing as 8am instead of 9am

wardy277 avatar Nov 07 '22 09:11 wardy277

I just realised this problem as well.. lots of automation not working in time....

Korte68 avatar Nov 07 '22 10:11 Korte68

Hey there @allenporter, mind taking a look at this issue as it has been labeled with an integration (google) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of google can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Change the title of the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign google Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


google documentation google source (message by IssueLinks)

home-assistant[bot] avatar Nov 12 '22 22:11 home-assistant[bot]

Duplicate of #81527

allenporter avatar Nov 12 '22 22:11 allenporter

Meant to respond to this earlier to confirm that it appears to be only recurring events that are affected by this bug (presumably ones where the first instance occurred before the time change, maybe?). One-time events seem to me unaffected.

SteveDinn avatar Nov 12 '22 22:11 SteveDinn