-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
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
windows_to_olson issues #135077
Comments
Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) calendar documentation |
This is related to a problem with the icalevents python library, see https://github.com/jazzband/icalevents/pull/145/files with the fix that is available sind 3 month, but not merged yet :-( I've successfully tested it and it works for me now. |
Using HAOS I can see no ICalEvents integration or smiliar. ICS Calendar integration already using ICalender 6.1: |
The problem
Updating to Core 2025.1.0, I noticed the following error related to an external integration. I'm unsure if this issue is genuinely tied to the external app or possibly connected to the Calendar (hence why I'm starting this thread). However, I resolved the problem "windows_to_olson" modifying /usr/local/lib/python3.13/site-packages/icalevents/icalparser.py of package icalevents replacing "from icalendar.windows_to_olson import WINDOWS_TO_OLSON" to "from icalendar.timezone.windows_to_olson import WINDOWS_TO_OLSON".
What version of Home Assistant Core has the issue?
2025.1.0 & 2025.1.1
What was the last working version of Home Assistant Core?
Just before 2025.1.0
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
icalevents
Link to integration documentation on our website
https://www.home-assistant.io/integrations/calendar
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
The text was updated successfully, but these errors were encountered: