VW Group Connect v4.10.0b5

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

Fixed

• The "data is stale" warning stops firing on fresh data, and per-field capture times finally appear (#1688, thanks @Datendieb).
  He downloaded one of his own portal files and found what the integration had been missing: every reading in it carries
  its own capture time, minutes old — while the single "vehicle last reported" value the manufacturer sends alongside
  was frozen five days earlier. The integration only ever read that one frozen value, so it announced data as four days
  old while the readings beside it were from that afternoon. The earlier fix helped only for the one poll in which a
  reading happened to change, which is why he kept seeing the warning come back minutes later.
  The reason the per-reading times were ignored is embarrassingly small: they arrive under a spelling the parser did not
  recognise — and it is the most common spelling there is, 411 of the stored sample files use it against 140 for the one
  the parser knew. Two more things were quietly broken by the same gap. The per-reading capture times were empty
  everywhere (he spotted that too), and when a file repeats the same reading at different times — which this feed does
  constantly — the integration could pick the older one, because with no timestamps to compare it fell back to the order
  the file happened to list them in.
  Freshness now anchors on the readings themselves whenever the manufacturer's own timestamp is older than they are,
  preferring the odometer's own capture so the "last reported" time can never run ahead of the reading it describes.
  Cars that send no per-reading times behave exactly as before.

Changed

• A failed login now says which page it landed on, instead of just "no form fields found" (#1712).
  When the login page is not the classic form, the error said nothing about what it actually was — not the address,
  not the form it found, not the field names it saw. That one line existed only in debug logging, so every report
  started with a round of "please switch on debug logging and try again" before anyone could tell which login variant
  had been served. It matters because there is more than one: the integration only treats a page as the modern login
  when the address says so, and the manufacturer demonstrably serves others — error, consent and terms pages all live
  under a different address, and our own stored samples contain seven of them. The message now names the page, the form
  it found, whether there was a form at all, and the field names it saw. Addresses are reported without their query
  string and with account identifiers masked, and field names are reported without their values, so the message
  stays safe to paste into a public issue.
• A rejected token exchange now names the reason, not just "HTTP 400" (#1712).
  The reason is in the reply and it distinguishes a wrong client, a spent code, an account that is not authorized and a
  refused method. Which key carries it was counted rather than assumed: 90 of the stored samples use errorCode
  against 18 for the one the standard prescribes, so reading only the standard key — as the first version of this did —
  would have found nothing on most real replies. Only a value shaped like an error code is ever shown; free-text
  descriptions, which echo request content back, are deliberately not read.

Full diff vs v4.9.0 / Kompletter Diff zu v4.9.0

Every commit, file and code change between the two versions:
Jeder Commit, jede Datei und jede Code-Änderung zwischen beiden Versionen:

➜ v4.9.0...v4.10.0b5

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:

• v4.9.0 · 2026-10-01
• v4.8.0 · 2026-09-29
• v4.7.16 · 2026-09-25

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:

1. Download vag_connect.zip from this release / vag_connect.zip aus diesem Release herunterladen
2. Unzip and copy custom_components/vag_connect/ to your HA config/custom_components/ folder, replacing any older copy / Entpacken und den Ordner custom_components/vag_connect/ in dein HA config/custom_components/ kopieren — alten Ordner ersetzen
3. 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.