core icon indicating copy to clipboard operation
core copied to clipboard

Caldav error on todo with Nextcloud `'datetime.date' object has no attribute 'tzinfo'`

Open Octelly opened this issue 1 year ago • 1 comments

The problem

#106671 seems related

Home Assistant crashes when trying to sync a Nextcloud (28.0.10) Tasks (0.16.1) to-do list.

What version of Home Assistant Core has the issue?

core-2024.5.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

CalDAV

Link to integration documentation on our website

https://www.home-assistant.io/integrations/caldav/

Diagnostics information

home-assistant_caldav_2024-10-05T11-31-20.006Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

Installed and configured via Nix on a NixOS installation.

Packaging is done here and the configuration module (likely less relevant) can be found here.

I am not familiar with HAss' codebase, but since Python module installation is handled by Nix here, checking out component packaging in particular could be relevant.

I really hope this is not a Nix-specific issue.

Octelly avatar Oct 05 '24 11:10 Octelly

This seems to be a bug in the vobject module, which seems to be used directly by the HA caldav integration. It seems to me that the icalendar module is more mature and actively maintained than the vobject module, so I would recommend getting rid of the vobject dependency.

tobixen avatar Nov 27 '24 06:11 tobixen

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. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

This issue is still relevant on the latest version.

Octelly avatar Feb 25 '25 13:02 Octelly

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. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.