VAG Connect v2.10.5

EU Data Act portal: no more manual click-through. When the integration is in read-only portal mode and you opt in via the new toggle, it kicks off the Custom Data Request on its own.

What's new

Added

• EU Data Act portal Custom Data Request auto-kickoff (live-trace based). At startup in read-only data_act_portal mode, the coordinator checks each VIN for an existing 15-min Custom Request and creates one when none exists. Uses the verified /proxy_api/euda-apim/ endpoints captured 2026-06-03: GET metadata/partial to detect, CSRF + POST requests/partial to kick off, GET datadelivery/{Identifier}/list to pick up the ZIPs. The portal accepts at most one active custom request per VIN at a time so the check-then-create order is critical; we adopt an existing request if one is already running instead of double-kicking.

  New toggle eu_data_act_auto_kickoff in OptionsFlow defaults to OFF because the kickoff implies a 1-month data subscription on the user's account at the portal.

• Repairs issue on portal session expiry. HTTP 401 on any portal API call now opens a guided data_act_session_expired Repairs issue pointing the user at the Reconfigure flow. Portal sessions are cookie-bound and not refreshable, so we surface the prompt instead of silently looping.

How it works (when toggle is ON, strategy is data_act_portal)

1. Setup completes -> coordinator runs _ensure_data_act_custom_request_kickoff().
2. For each VIN: GET metadata/partial to detect active 15-min request.
3. If one exists -> adopt its Identifier into entry.options[CONF_DATA_ACT_IDENTIFIERS].
4. If none exists -> CSRF fetch -> POST requests/partial with canonical payload (Frequency=15mins, 31-day duration, all 6 DataClusters) -> persist new Identifier.
5. Datasets become downloadable via GET datadelivery/{Identifier}/list (404/500 = still collecting, can take up to 24h).

Full diff vs v2.10.4

v2.10.4...v2.10.5

Installation / Update

HACS users: the update notification appears automatically within ~6 hours.

Manual install:

1. Download vag_connect.zip from this release
2. Unzip and copy custom_components/vag_connect/ to your HA config/custom_components/ folder, replacing any older copy
3. Restart Home Assistant