-
-
Notifications
You must be signed in to change notification settings - Fork 32k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editing a todo list item due date and saving causes date to be out by one day. Google Tasks Integration. #125191
Comments
Hey there @allenporter, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) google_tasks documentation |
I am not able to reproduce this in the UI following the steps you said. I suspect this may be something related to timezones, but I can't tell. (1) Can you tell me a little more simply the steps to reproduce with a service call? Your words don't appear to match the service call sent below. |
I will be able to capture the logs tomorrow. I first logged the issue under frontend issues and the service call was suggested. The issue appears on my installation and on a friends. The time zone is set to (GMT+10:30) Central Time -Adelaide. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Problem still exists for me on 2024.12 |
@StefanSarzio see #125191 (comment) and provide requested information. thanks! |
Forgot to follow up on this one. Only logs on each save were: 2024-12-06 18:23:55.306 DEBUG (MainThread) [homeassistant.components.google_tasks.coordinator] Finished fetching Google Tasks MTc5Nzc0ODY0ODI5MDU2NTI2MDI6MDow data in 0.463 seconds (success: True) 2024-12-06 18:23:58.351 DEBUG (MainThread) [homeassistant.components.google_tasks.coordinator] Finished fetching Google Tasks MTc5Nzc0ODY0ODI5MDU2NTI2MDI6MDow data in 0.474 seconds (success: True) On each save the date changes to the day before. Date is set to 10/12/2024 |
Try again with GIF, JPEG, JPG, MOV, MP4, PNG, SVG, WEBM, CPUPROFILE, CSV, DMP, DOCX, FODG, FODP, FODS, FODT, GZ, JSON, JSONC, LOG, MD, ODF, ODG, ODP, ODS, ODT, PATCH, PDF, PPTX, TGZ, TXT, XLS, XLSX or ZIP." |
ok thanks, you're right google tasks is not configured correctly for debug logging. I will try to reproduce this myself by changing my timezone. I think the issue is the timezone may be getting dropped in the round trip between google and home assistant so the timezone distance away from UTC is what may impact this. e.g. if you truncate my timezone at midnight i still get the same day, but not GMT+10 etc |
I was able to reproduce the issue, and have a fix that appears to work. Thank you for the report. |
The problem
When adding a todo item for google tasks and then saving a date.
What will save is the day before the date selected.
What version of Home Assistant Core has the issue?
core-2024.8.3
What was the last working version of Home Assistant Core?
unknown
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Google Tasks
Link to integration documentation on our website
https://www.home-assistant.io/integrations/google_tasks/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
Steps to reproduce the issue
did a test and the call_service showed the correct date entered when saved. Set the date to 30/08/2024.
In the Todo list after saving it shows 29/08/2024.
Also if I set the date to say 31/08/2024 and save it. It will appear as 30/08/2024. If I then edit again and just save it and not change the date it will then show 29/08/2024.
event_type: call_service
data:
domain: todo
service: update_item
service_data:
item: T3BiUTE1OEdPb0QyTjhYZg
rename: test
status: needs_action
description: null
due_date: "2024-08-30"
entity_id:
origin: LOCAL
time_fired: "2024-08-28T00:20:14.041365+00:00"
context:
id: 01J6B5NEJS11A1DEPK6JBKNK7Q
parent_id: null
user_id: 1a662c9ead9543a6aff0859ff9fb7b86
The text was updated successfully, but these errors were encountered: