VAG Connect v3.0.3
Home Assistant integration for Audi · VW · Škoda · SEAT · CUPRA · Porsche · VW US/CA.
What's new in this release / Was ist neu in diesem Release
Added
- New opt-in "test cohort" option — help unlock features for your car. A new tick-box in the integration's options (off by default). When you turn it on, the integration may run experimental reads on your car — the first one being an attempt to recover GPS location for Volkswagen EU cars over the volkswagen.de channel — and, occasionally, show a dismissible notification asking you to share a diagnostics file so a new capability can be confirmed for your exact model. Everything shared is redacted automatically before it leaves your system (no VIN, GPS, tokens or e-mail), and turning the option back off stops the experiments and the notifications. It's how features like location get proven across the many different VW EU platforms without one person's single car having to represent them all. (#923)
Fixed
- The volkswagen.de channel now tells you when Volkswagen wants you to accept updated terms. If VW puts up a terms-and-conditions wall during sign-in, the channel used to report a generic "session expired" and loop forever; it now says plainly to open volkswagen.de, accept the terms, and re-add the channel — the actual fix.
- A volkswagen.de session that has just failed no longer overwrites your good saved cookies. If a refresh fails mid-poll, the integration now keeps the last known-good cookies instead of saving the dead set over them, so a later restart can still resume silently instead of being stuck.
- The volkswagen.de channel is more likely to survive a Home Assistant restart without asking you to re-add it. Volkswagen reuses the same cookie names (its sign-in cookies) on both the login host and the website host with different values; the way the session was saved could collapse the two and overwrite the one that actually keeps you signed in — so after a restart the silent resume landed on the login page and asked for the e-mail code again. The save now keeps each cookie distinct per host, the host allow-list is an exact check instead of a loose text match, and the silent-resume step follows Volkswagen's longer sign-in redirect chain (it recently grew past the old limit). If the prompt still returns after this, the debug log now shows exactly which cookie/host is missing. Thanks @Arno-MA-73 for an exceptionally precise write-up that pinned the failure to the cookie round-trip.
- Older Car-Net (MBB) cars get their volkswagen.de live-status readings back. Warning-lights, lock/unlock history and service status are fetched with a per-car "data-centre" id that depends on the car's platform; the platform was matched too strictly, so a Car-Net car whose platform id carries a suffix was sent the wrong id and every one of those reads came back empty. It now matches the platform family, so those cars get the readings instead of nothing. The portal ships a
vehicleIsStandingStillmotion flag that was catalogued but never mapped; it now drives the existing Driving sensor (standing still ⇒ not driving) on cars that send it. Some vehicles don't send it at all — that's a data gap on VW's side, not a parsing one — so it's only surfaced when actually present. Thanks @zdravac, who found it in the data dictionary and confirmed which fields were and weren't reaching entities. - A Volkswagen EU car read over the volkswagen.de channel no longer falsely shows OFFLINE. That channel (and the EU Data Act one) can't tell the integration whether the car is online, and an unknown online state was being treated as offline — so a car that was answering its reads perfectly well still reported OFFLINE. It now says OFFLINE only when the backend actually reports the car as offline, and otherwise leaves the state unknown rather than inventing one. Thanks @fight3, whose T-Roc showed this alongside the separate, still-open missing-GPS question in #923.
- Volkswagen US/Canada cars no longer show a range of −1. VW's US/Canada backend sends
cruiseRange: -1as a "no value" marker; it was taken literally, so the Range entity read −1 — and because the field was then set, it also blocked the car's real (EV) range from filling in. A negative range is now treated as unknown, so the genuine range shows through instead. Thanks @fg877khkv8-maker, whose field-by-field raw capture on a 2023 ID.4 pinned it. (#1082) - The ABRP "upload on data change" automation no longer strands after a single failed upload (#1135). The blueprint fired only when the "ABRP data changed" sensor turned on, and that sensor only clears once an upload actually succeeds — so if the one upload on that edge failed (a transient network / ABRP error), the sensor stayed on with no further trigger, and every later change silently stopped reaching ABRP. The blueprint now also re-checks every few minutes and re-sends whenever there is still unsent data, so a stuck state heals itself on the next tick. If you use this automation, re-import the updated blueprint to get the fix. Thanks @Fishermanjb for the precise diagnosis and the screenshots that pinned it.
Internal
- VW EU position reads now explain themselves in the debug log. The CARIAD parking-position endpoint being closed for EU passenger cars (403) is logged at debug instead of being swallowed silently, so a "device_tracker stays unknown" report (#923) is diagnosable rather than looking like a dropped read.
- The volkswagen.de channel logs which cookies it saves and restores — names, hosts and expiry only, never values. When a resume works once and then dies ~20–30 seconds later on the next reload, the cookie that changed between the two is what tells us whether the session was overwritten on our side or expired on Volkswagen's; export and import now record that value-free list at debug level so it's diagnosable from one log. Thanks @Jradon001 for a repro precise to the second. (#966)
Full diff vs v3.0.2 / Kompletter Diff zu v3.0.2
Every commit, file and code change between the two versions:
Jeder Commit, jede Datei und jede Code-Änderung zwischen beiden Versionen:
Recent releases / Letzte Releases
If you're upgrading from an older version, also read these notes:
Wenn du von einer älteren Version updatest, lies auch diese Release-Notes:
Full history: CHANGELOG.md
Installation / Update
HACS users: the update notification appears automatically within ~6 hours of the release.
HACS-User: Der Update-Hinweis erscheint automatisch innerhalb von ~6 Stunden nach dem Release.
Manual install / Manuelle Installation:
- Download
vag_connect.zipfrom this release /vag_connect.zipaus diesem Release herunterladen - Unzip and copy
custom_components/vag_connect/to your HAconfig/custom_components/folder, replacing any older copy / Entpacken und den Ordnercustom_components/vag_connect/in dein HAconfig/custom_components/kopieren — alten Ordner ersetzen - Restart Home Assistant / Home Assistant neu starten
Supported brands / Unterstützte Marken
Volkswagen EU · Audi · Škoda · SEAT · CUPRA · Volkswagen US/CA (Beta) · Porsche (Beta)
Found a bug? / Bug gefunden?
Open an issue with the bug-report template: https://github.com/its-me-prash/vwgroup-connect-ha/issues/new/choose
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.
Bitte VIN auf die letzten 6 Zeichen kürzen und Email/Tokens/GPS vor dem Posten entfernen.