You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting up my calendar I noticed the calendar integration breaking, which happened suddenly after it worked for days without an issue. It took me some time to figure out what has been happening and I can now report an issue.
In short: if a calendar event has the duration of the entire day and is scheduled to be repeated on a yearly basis, this event will crash the calendar integration as long as this event is yesterday. This can be worked around by removing the yearly repeat feature or moving the event to today or 2 days back - which all is not helpful for a calendar.
context
This is an event which will crash the integration (displayed in .ics format):
However it will only crash the integration if today is 2021-07-24. If today is any other date it will not crash. Moreover the integration heals itself when the day changes. So if it's 2021-07-24 and the integration is crashed, the issue will resolve automatically if the day changes to 2021-07-25.
error message
The error thrown in the log is this one:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 350, in async_update_ha_state
await self.async_device_update()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 558, in async_device_update
raise exc
File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/caldav/calendar.py", line 146, in update
self.data.update()
File "/usr/src/homeassistant/homeassistant/util/__init__.py", line 280, in wrapper
result = method(*args, **kwargs)
File "/usr/src/homeassistant/homeassistant/components/caldav/calendar.py", line 212, in update
vevent = event.instance.vevent
File "/usr/local/lib/python3.8/site-packages/vobject/base.py", line 531, in __getattr__
raise AttributeError(name)
AttributeError: vevent
2021-07-24 23:59:44 ERROR (MainThread) [homeassistant.helpers.entity] Update for calendar.default_calendar fails
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/vobject/base.py", line 529, in __getattr__
return self.contents[toVName(name)][0]
KeyError: 'vevent'
There are no issues with other tools like the Android calendar to interact with the events and CalDAV - only the Home Assistant integration crashes for an entire day.
What is version of Home Assistant Core has the issue?
homeassistant/home-assistant:2021.6.6
What was the last working version of Home Assistant Core?
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 350, in async_update_ha_state
await self.async_device_update()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 558, in async_device_update
raise exc
File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/caldav/calendar.py", line 146, in update
self.data.update()
File "/usr/src/homeassistant/homeassistant/util/__init__.py", line 280, in wrapper
result = method(*args, **kwargs)
File "/usr/src/homeassistant/homeassistant/components/caldav/calendar.py", line 212, in update
vevent = event.instance.vevent
File "/usr/local/lib/python3.8/site-packages/vobject/base.py", line 531, in __getattr__
raise AttributeError(name)
AttributeError: vevent
2021-07-24 23:59:44 ERROR (MainThread) [homeassistant.helpers.entity] Update for calendar.default_calendar fails
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/vobject/base.py", line 529, in __getattr__
return self.contents[toVName(name)][0]
KeyError: 'vevent'
Additional information
I'm using the atomic-calendar-revive in lovelace, but the stacktrace makes be believe that the core issue is in the calendar integration.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
The problem
issue
When setting up my calendar I noticed the calendar integration breaking, which happened suddenly after it worked for days without an issue. It took me some time to figure out what has been happening and I can now report an issue.
In short: if a calendar event has the duration of the entire day and is scheduled to be repeated on a yearly basis, this event will crash the calendar integration as long as this event is yesterday. This can be worked around by removing the yearly repeat feature or moving the event to today or 2 days back - which all is not helpful for a calendar.
context
This is an event which will crash the integration (displayed in .ics format):
However it will only crash the integration if today is 2021-07-24. If today is any other date it will not crash. Moreover the integration heals itself when the day changes. So if it's 2021-07-24 and the integration is crashed, the issue will resolve automatically if the day changes to 2021-07-25.
error message
The error thrown in the log is this one:
similar issues
#46345
environment
configuration of the integration
There are no issues with other tools like the Android calendar to interact with the events and CalDAV - only the Home Assistant integration crashes for an entire day.
What is version of Home Assistant Core has the issue?
homeassistant/home-assistant:2021.6.6
What was the last working version of Home Assistant Core?
homeassistant/home-assistant:2021.6.6
What type of installation are you running?
Home Assistant Container
Integration causing the issue
calendar
Link to integration documentation on our website
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
I'm using the atomic-calendar-revive in lovelace, but the stacktrace makes be believe that the core issue is in the calendar integration.
The text was updated successfully, but these errors were encountered: