VAG Connect v2.10.1
VW EU login hotfix.
What's new
The v2.10.0 SPA fix unblocked one path but several users still hit HTTP 403 on the authorize endpoint itself - the Azure WAF in front of identity.vwgroup.io started rejecting the Android user-agent some time on 2026-05-31. Same finding the wider HA-VAG community converged on this week.
Fixed
- VW EU 403 on authorize endpoint (#388, #393). When the initial GET to
/oidc/v1/authorizecomes back 401 or 403, retry once with a plain mobile-browser user-agent. Picks up users blocked at the WAF without affecting accounts that already work on the Android UA. - VW user-agent bumped to
Volkswagen/3.61.0-android/14to match the current shipping APK. The old3.51.1string is what the WAF presumably flagged.
Full diff vs v2.10.0
Installation / Update
HACS users: the update notification appears automatically within ~6 hours.
Manual install:
- Download
vag_connect.zipfrom this release - Unzip and copy
custom_components/vag_connect/to your HAconfig/custom_components/folder, replacing any older copy - Restart Home Assistant
Found a bug?
Open an issue with the bug-report template: https://github.com/its-me-prash/vwgroup-connect-ha/issues/new/choose
Please mask your VIN to the last 6 characters and remove email/tokens/GPS before posting.