-
-
Notifications
You must be signed in to change notification settings - Fork 28.6k
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
Can't save any new To Do items when system timezone is not valid timezone #112647
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) local_todo documentation |
I'm with the same issue here |
Also noticed that this error occurred too with one list after trying to apply due date. It also affected other local todos which in turn did not allow me to modify items. I didn't try to add due dates to the other lists ... But then after a reboot, all local todos broke sand are unavailable. Reload of the device integration does not fix. Nor trying to use the get_items service. Adding new local todos works and can change those Hope this also helps |
@al-jimenez Thank you for the report. Two tracks to explore here:
|
|
Ok thanks that is super helpful. The error message is So it's getting to CST somewhere. I'll try to reproduce. Thanks! |
NOTE: additional info: In Developer Tools | Template, I enter the following to verify:
And got:
An important note on the severity of the issue: is that I cannot create and edit any new to-do items. I can start one but as soon as I try to edit one I get the error and can't modify it. But curious thing is I can modify older pre-existing To-do items. ¯_(ツ)_/¯ Hope this helps. |
I'm having the same issue. I don't have timezone set in configuration.yaml, just through the UI. For me, the template in the above comment expands to:
I've got it set to |
I have not yet been able to reproduce this myself to get to the bottom of it. Do you happen to use local calendar? I am curious if you also see problems there. If you happen to use local calendar and can get a diagnostics entry that would help get some debug information that isn't yet included in local todo. |
I don't use local calendar but I do have a couple calendar helpers. I'm not sure if those are related? |
I do not have the 'local calendar' integration installed and don't use any calendars. |
❗️I installed the 'Local Calendar'. I created an event without issue BUT, when I attempted to edit the event I received the following error:
So it would seem the issue may not be specifically related to 'Local To-do' |
@al-jimenez yeah sorry that's #112716 which i fixed for an upcoming patch release. What would be helpful here is if you get the diagnostics ("download diagnostics") for it as it includes detailed timezone information which is also relevant to the todo integration. |
Here is the diagnostic log: `2024-03-09 09:37:46.220 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration watchman which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant The above exception was the direct cause of the following exception: Traceback (most recent call last): |
Can you see the "Download diagnostics" in the link i provided? It is something different from the logs. |
Yes, that process is what I used for the above. |
Those are logs, the diagnostics section is a little lower ( I may have linked too high) |
When I asked it to download diagnostics log it included all of this. Only the last portion really applies to the issue, not sure why it included all the other stuff. |
Diagnostics gives you a file to download and attach as shown in this screenshot https://www.home-assistant.io/docs/configuration/troubleshooting/#download-diagnostics (different from enabling debugging and the log contents that is pasted above) |
Yeah, I enable diag logging, reproduced the issue to get the error, I then disable diag logging and the diag file downloads to my local folder (auto downloaded once I disable diag logging). That is what I pasted above. (I DO NOT get the 'Download Diagnostics' menu item though). The '[homeassistant.loader] ', '[homeassistant.setup]' & 'ical.component]' entries in the file is prepended to the diag file and seems to have been included in it. |
To clarify: You're saying "diag logging" (which is really "debug logging") which is not what i'm asking for. I am asking for "Download Diagnostics" for local calendar. |
Yes, sorry for that, diag logging = debug logging. And yes that is the file I provided above. Attached here: |
We seem to be misunderstanding each other. To clarify:
Here is a screenshot of what i'm talking about: Which is the same as this: https://www.home-assistant.io/docs/configuration/troubleshooting/#download-diagnostics |
Sorry, my fault. |
I also ran into the 'timezone not found' issue. I tried to reboot the HA computer and now two of my four lists are missing. They are there if I look at the local to-do integration but are not there if I look at 'to-do lists'. I have no idea what happened to the data or where I could find it to re-create the lists |
I am having this issue as well on v2024.3. I got the timezone issue. I tried to roll back to v2024.2, but it just made two of my todo lists dissapear once the system came back up. I updated back to v2024.3 and they're still missing. Not sure if it's related, but my timezone |
Same here. TZ issues with todo. Deleted 2 of my three lists. I did set the state of the two unavailable lists manually, and they got back, but after that, they can´t receive new entrys. Then a I deleted both unavailable lists and create new ones. Again, TZ issues. I do have local calendar. TZ gmt -03:00 São Paulo BR |
I have a similar issue, I started with this notice, shown in the photo, when I ticked off as complete the new items, that I had just added. It also had the same issue if I edited the item description. It progressed to not being able to add new items to the list, then it wiped my list from existence. When I restored it to the previous backup, the list came back, but with the first issue. Where I could add a new item, but it could not be completed or updated. I haven't had an issue with list items that were existing prior to the update, just new list items on any of my lists. (it is the same with all my todo lists.) I'm using pacific time zone, if that helps. New Todo lists created after the update have the same bug as well. They also continue to have the issue after the roll back. |
Thanks, I think i have enough information for a workaround even though I can't reproduce it myself yet. The new home assistant is writing date entries with timezones that are not found by the timezone library (old or new) so it makes sense why rollback doesn't help. I'll make a patch to simply ignore the invalid timezone entries for now, then we can clean them up later and get them repaired in another pass after that once I can reproduce. |
Thank you, the diagnostics show what I was looking for. The problem is the timezone information is coming from the system timezone and not the home assistant timezone:
|
I'm going to tackle this way:
Thanks for your patience folks |
Allen, thanks for looking into this. I have the same issue but my HA Timezone is the same as the System Timezone (as below) so I'm not sure if that is the issue. I too have only noticed this issue since 2024.3 if that helps. Timezone: Australia/Brisbane |
Just wanted to add that I am having both of these issues, one with the local Todo list and the local calendar. I am running HA on a docker container on linux which is an LXC on Proxmox. The Linux container shows the TZ as CDT -0500. Wanted to keep an eye on the resolution. Appreciate you looking into it. |
The fix is scheduled for the 2023.3.1 patch release. |
I know this issue is closed and the fix seems like a reasonable fix. But quick question. I just updated to Supervisor 2024.03.0 and lost one of the Todo lists. It had quite a number of items; will there be a way to restore those once the fix deployed? Thanks very much @allenporter for all your work on getting this issue resolved. |
Yes, I will ensure the content is restorable with no action on your part. I recommend not touching it and we can circle back. If 2024.3.1 does not solve your issue open a new issue report filling out the full issue template and we will get to the bottom of it. (That said,my intention is that it's fixed in this patch, but just elaborating to answer your question) |
Posting here as I think this might be the same issue but different flavour... 2024.3.0, HAOS, have started using todo lists. I have been using nodered to automatically assign due dates to new and completed tasks using the API node, sending in the YYYY-MM-DD format. This has been working fine up until I had restart just now - now the integration won't load and gives the following error:
This looks like it might be part of the same issue as above, but brought on in a different way - what do you think? My plan of attack is to just leave it and see if 2024.3.1 fixes it too. It could be my nodered flow I guess, but I don't think it is - here it is just in case: EDIT: Apologies if this isn't related to the issue above - I can make a new issue if so - and sorry for the giant wall of nodered! |
I think i might be experiencing this as well. I see several todo lists as entities, but I do not see them in the todo list section and if i were to add the todo list entities as cards they are blacked out. How do i restore the lists? |
Last two of you: please upgrade to 2024.3.1 which fixes those issues. |
Same error, with additional complication after upgrading to 2024.3.1, and a succesful (but manual) resolution. Here's what I observed:
The affected list entity was "homelab". I could no longer see the items on there, either through the UI or manually editing the URL to https://localURL/todo?entity_id=todo.homelab. I was able to see the data file in /homeassistant/.storage/local_todo.homelab.ics, with the original entries. The entry which was previously causing the timezone error was:
Hope this helps in troubleshooting, or for others with orphaned/missing to-do lists after the 2024.3.1 upgrade. |
My issue - fixed by 2024.3.1. Many thanks |
Hi @allenporter I have updated to 2024.3.1 but my to-do list are still inactive. Do you need any more information from me? Thanks for your help. Error while setting up local_todo platform for todo The above exception was the direct cause of the following exception: |
@Blackshome thanks for the report, we have issues tracking the additional set of issues that were not resolved in 2024.3.1 e.g. #113445 |
@allenporter thanks for the info Allen, looks like you all over it. We will wait for the patch from you. Again thanks for your help and everything you do for HA. |
The problem
Using Local To Do list integration. Created a new To Do list item, then I edited it to add a description; once I tried to save it (& I DID NOT specify a due date or time), I then received this error, which was also posted to syslog: "No timezone information available for event: {key}". I could NOT save the To Do item & discovered that I could start new items, but could not edit them. But... I was able to edit items that had been previously created. Just can't edit any new items.
What version of Home Assistant Core has the issue?
core-core-2024.3.0
What was the last working version of Home Assistant Core?
core-core-2024.2.5
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
Local To-do
Link to integration documentation on our website
https://www.home-assistant.io/integrations/local_todo
Diagnostics information
Attempted the above several times and kept getting the error. Checked my 'timezone' and it was correct:
(GMT-06:00) Central Time. I attempted to enter a due date and time, but still got the error. I was not able to save the To Do item so this basically means I cannot create any new To Do list items. NOTE: I was able to successfully edit and modify existing To Do items. Just not create any new ones. I have two To Do lists & and I could not create new items in either list.
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
I had forgotten to mention that I had also restarted HA and tested again. Same result.
The text was updated successfully, but these errors were encountered: