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
[Bug]: Leap Year Issue #1844
Comments
same here, using ics calender of (AVM München) stopped working after update feb 20th with the same error message in log. |
Same here. First time user and thought i misconfigured it. |
Same here using "Stadtreinigung Hamburg"
|
Same for "KWU Entsorgung Landkreis Oder-Spree" |
Same isue with ics file |
Same with Mags Mönchengladbach Abfallkalender |
Date exception cases and programmers, name a better duo :) I feel the maintainer :i-know-that-feel-bro: |
I would guess it fixes itself tomorrow. |
Same here |
Leap year error fixed in #1855. But should work normally today. ICS helper calculated an end date by replacing the year with year +1 in the current date, which throws an error as the 2025-02-29 does not exist. |
I Have A Problem With:
The integration in general
What's Your Problem
Found an error this morning in the logs when the integration was trying to fetch the schedule from the server
Feb 29 01:21:31 smarthome hass[7852]: ValueError: day is out of range for month
Obvisously "end_date" is set to "same day next year", with doesn't work for February 29th
end_date = start_date.replace(year=start_date.year + 1)
Source (if relevant)
ICS
Logs
Relevant Configuration
Checklist Source Error
Checklist Sensor Error
Required
The text was updated successfully, but these errors were encountered: