Populate uid and recurrence_id in CalDAV calendar events

[frenck]

Proposed change

The CalDAV integration was not passing uid or recurrence_id from the source VEVENT when constructing CalendarEvent objects, even though both fields are supported by CalendarEvent and other calendar integrations (local_calendar, google, remote_calendar) properly populate them.

This meant that both the REST API (/api/calendars/<entity_id>) and the calendar.get_events service returned null for uid and recurrence_id on every event, breaking downstream consumers that rely on uid to identify or deduplicate events.

This PR passes uid and recurrence_id from the vobject VEVENT to CalendarEvent in both code paths (async_get_events and _async_update_data).

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes CalDAV integration: CalendarEvent.uid not populated from source VEVENT #170761
• This PR is related to issue:
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies a diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[Copilot]

Pull request overview

This pull request updates the CalDAV integration to propagate uid and recurrence_id from CalDAV VEVENTs into Home Assistant CalendarEvent objects so API consumers can reliably identify/deduplicate events.

Changes:

• Populate CalendarEvent.uid and CalendarEvent.recurrence_id in both CalDAV event listing (async_get_events) and coordinator refresh (_async_update_data).
• Extend CalDAV calendar tests to assert uid (and add a new test for recurrence_id) in the /api/calendars/{entity_id} response.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
homeassistant/components/caldav/coordinator.py	Adds uid and recurrence_id mapping when constructing CalendarEvent instances.
tests/components/caldav/test_calendar.py	Updates expected API event payload to include uid and adds a recurrence-id-focused API test.