search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
70.14k stars 29.18k forks source link

CalDAV entities ignore events more than 6 days in the future #108003

Open thatso opened 6 months ago

thatso commented 6 months ago

The problem

I have a Nextcloud calendar with single monthly events for garbage collection. These events show up in the calendar view but only trigger the corresponding entity when they are no more than 6 days in the future. It does not matter if they are all day events or have start and stop times. Today is January, 14th. A test entry for the 20th shows up in the calendar and triggers the entity:

1

2

If I change this event's date to one day later or any other date more than 6 days in the future, it still shows in the calendar but the entity stays empty:

3

4

Notice that besides the test entries there is a regular entry for February, 3rd, which also does not show in the entity.

5

What version of Home Assistant Core has the issue?

core-2024.1.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

CalDAV

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

I've reloaded the CalDAV integration and also rebooted HA between the test entries. The described error happens only when adding the CalDAV integration via UI. If I add it manually via YAML and specifically state days: 60 the entity attributes contain the event scheduled for the next month as expected. I suspect the reason lies in line 45 of core/homeassistant/components/caldav/calendar.py: CONFIG_ENTRY_DEFAULT_DAYS = 7

home-assistant[bot] commented 6 months ago

caldav documentation caldav source

thatso commented 4 months ago

Any progress on this?

issue-triage-workflows[bot] commented 1 month ago

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.

thatso commented 1 month ago

not stale