VW Group Connect v4.8.0

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

• Brake-fluid warning now surfaces as its own binary sensor where the car reports it (Vehicle Data
  Scout, #1592). An Audi Q6 (PPE) ships the brake-fluid warning lamp as a raw FlexRay/ESC signal in
  its Data Act export. It's now decoded into a "Brake Fluid" problem binary sensor (on = warning
  active); cars that don't report the signal get no entity. Only the OFF state is confirmed so far, so
  the active decode is conservative (anything that isn't the OFF value reads as a warning).
• Battery cell-level telemetry for cars that report it (Vehicle Data Scout, #1622). Some VW cars
  ship raw battery-management (BMS) signals in their Data Act export. These now surface as diagnostic
  sensors — highest/lowest cell voltage, battery coolant return temperature, battery capacity,
  recuperated energy and pack voltage — and the cell-temperature extremes feed the existing HV battery
  temperature (min/max) sensors. All are disabled by default and only created for cars that actually
  report the signals; the raw module/cell index fields stay visible in diagnostics until their meaning
  is documented.

Fixed

• A live vw.de state-of-charge no longer gets dragged to the EU Data Act battery figure (discussion #1231, thanks @Ra72xx).
  On a multi-channel car (vw.de read live + the EU Data Act portal filling gaps) the fresh vw.de SoC could be
  overwritten by the portal's battery-energy figure, so the reading "bounced" to a lower number and lagged the live
  channel. The portal feed is a ~15-minute batch that can re-send a frozen stop-charging snapshot, so a live on-demand
  reading now always wins over it for SoC — on both the energy-sanity and the contested-value paths. Single-channel
  portal cars are unchanged: there the battery figure still corrects a genuinely stuck reading.
• A combustion car with an empty data feed is now typed correctly (#1538, thanks @Latte9090). A Golf
  GTD (diesel / ICE) read over the vw.de channel showed has_combustion = false when its EU Data Act
  feed was empty and the status carried no fuel/range block — even though VW's own relations response
  classifies the car as ICE (carnetAllocationType). We now read that classification and set the
  drivetrain from it (ICE → combustion, BEV → electric, hybrid → both), additively — only ever setting
  a flag true, never forcing it false — so an empty feed no longer mistypes the car.
• An odometer sitting at exactly 65,535 km is no longer blanked. 65535 (0xFFFF) is VW's
  "no reading" marker on bounded portal fields (state of charge, range, charge time, temperature), so
  it was dropped everywhere — including a genuine 65,535 km reading on the odometer / lifetime-distance.
  It's now kept for the mileage/odometer family (a plausible real value there) while still being
  dropped on the bounded fields; the separate odometer guard still screens VW's real 32-bit "no value"
  markers.
• Companion (ADB) EV cars now get their battery entities (#1552, thanks @nekas123). A companion-only
  read that parsed a valid state of charge / range still left has_battery false, so the Battery SoC,
  Electric Range and charging entities never appeared. A companion read now infers the battery from a
  present SoC/range (like the brand parsers already do); it only ever sets the flag true, so a
  combustion car is unaffected.
• Companion (ADB) detail-screen values no longer freeze after the first read (#1552, thanks @nekas123).
  The nav-read cache was re-applied before the "is a refresh due?" check, so the detail walk saw its
  targets already filled and skipped forever after the first read — charge target / power / time (and,
  on newer layouts, SoC and range) went stale. The scheduled refresh now runs first, and a fresh detail
  value wins over a stale overview one.
• Companion (ADB) no longer halves its overnight poll rate for no reason (#1552, thanks @nekas123).
  The 22:00–05:00 cadence reduction saves cloud API calls, which a local ADB read doesn't make — so it
  now skips a companion entry, unless the wake/sleep opt-in is on (there the slower night cadence also
  cuts how often the phone screen wakes).
• The portal climacontrol flag now feeds the climate-active sensor instead of just being noise
  (Vehicle Data Scout, #1603). A VW Passat's Data Act export carries a bare climacontrol on/off flag
  — the same "climate is running" datum the climatisation-active sensor already shows. It's now folded
  in as a fallback (the richer climate-state read still wins) and no longer flagged as an unmapped field.
• A car the BFF doesn't serve no longer spams the log with 404s (#1590). An Audi Q4 whose
  selectivestatus read persistently returns 404 (the backend simply doesn't serve it) used to raise on
  every poll — filling the error report and re-hitting the dead endpoint. After a few consecutive
  structured 404s the integration now backs off for a few hours (re-probing automatically) and shows
  the car's last-known data as stale instead of erroring, while a one-off or transient 404 still
  surfaces as before.

Docs

• Clearer where the test-cohort opt-in actually lives (#584, thanks @Donath206). A new FAQ entry
  spells out that the toggle sits in Configure on the existing entry (dialog "VW Group Connect —
  Settings"), not in the "Add integration" / „einrichten" wizard where you pick a login method — with
  the German UI labels too, since that's exactly where the mix-up happened.

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

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

➜ v4.7.16...v4.8.0

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.7.16 · 2026-09-25
• v4.7.15 · 2026-09-25
• v4.7.14 · 2026-09-23

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.