VW Group Connect v4.10.0b2
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
- Plug-in hybrids on the volkswagen.de channel finally get a battery charge level (#1313, thanks @realynot and @fschulte2812).
On MBB plug-in hybrids the EU Data Act feed carries no drive-battery charge at all and the charging read is refused,
so those cars have had no state of charge — the one number most people actually want. There is another read on the
same session that returns both drives, and it is now used: drive-battery charge and electric range, plus fuel level,
combustion range and oil level. Which drive is the electric one is taken from the data rather than from its position
in the response, so a car that lists its engines the other way round still maps correctly. A reading from a live
brand channel still wins where one exists. - Battery-care mode now reports why it last spoke up (Vehicle Data Scout, #1444, thanks @josie127-neu).
A new diagnostic sensor (off by default) shows the battery-care notification state — whether the charge target was
reset for the next charge, whether care mode is off, or whether the care score hit its warning threshold. It had
been left unmapped because its meaning was a guess; VW's own field catalogue documents the values, so there was
nothing left to guess. Two long-standing neighbours of it (the care score and its threshold) were also quietly
re-reporting themselves to the Scout on every poll for cars that send them nested — that's fixed in passing.
Changed
- A read refused for a missing subscription now says so (#1659, thanks @Joassens).
His maintenance read came back as4007 connectivityLicenseInactive, which is precise and tells you nothing about
what to do — he read it as a registration problem, so did I, and he eventually solved it by buying the paid Car-Net
subscription, which is exactly what the code meant. Those refusals now spell out the action, once per read, in the
log and in the error. The two cases are worded differently on purpose: an expired subscription needs paying for, an
account that isn't enrolled needs enrolling — and a refusal we haven't understood still says nothing rather than
guessing.
Fixed
- A frozen timestamp from the car no longer makes fresh data look days old (#1688, thanks @Datendieb).
His portal kept delivering all afternoon — odometer and charge level visibly moving — while the timestamp the car
reports about itself stayed five days old. The "data is stale" warning and problem sensor were built on that
timestamp alone, so they claimed 105 hours on data that was minutes old. A reading that has actually changed since
the last poll now proves the data is live and overrides the timestamp. Deliberately one-directional: unchanged
readings still prove nothing, because a car parked for days repeats them and a genuinely dead feed must still be
reported. He also spotted that "minutes since last snapshot" contradicted the snapshot time right next to it —
that field was measuring the car's timestamp instead of the snapshot, and now measures the snapshot. - The "no vehicle data yet" warning really does name the car now (#1656, thanks @kalwados).
The first attempt at this shipped in the last beta and still showed only the brand. The warning is raised from the
portal's own state, which is independent of any per-car flag — and the flag the first version filtered on isn't
reliably set, so on exactly the accounts this warning fires for, nothing matched and it fell back to the brand.
It now prefers the car that is actually flagged (useful when one car on the account works and another doesn't) and
otherwise names every car on the account, since the warning means the account's portal is delivering nothing. - The volkswagen.de channel no longer tells you your password is wrong when it isn't (#1679, thanks @Fishermanjb; #1313, thanks @realynot).
Both reporters had the channel refuse them with "email address or password incorrect" while the very same
credentials signed in fine on volkswagen.de and even reached the e-mail-code step. The login itself was careful
about this — it only gets a real "wrong credentials" answer from a specific refusal — but both places that show
you the result threw every other failure (an expired session, a redirect loop, a page it didn't recognise, the
portal being down) into the same message. So people were sent off to reset a password that was never the problem.
Only the genuine credential refusal says that now; everything else says it is not your password and points at
the log, which has carried the real reason for a while. - The Porsche login now tells Auth0 which language and country you are in.
The official Porsche app passes the device locale into its login call; we sent
nothing, so the page we land on came back in whatever language Auth0 guessed.
That matters less for you than for us: when a login runs into one of Porsche's
wall screens, the integration describes it by looking for English keywords, so
an unexpected language could leave a report saying nothing at all about what
was hit. It now sends your Home Assistant language and country, which also
matches what the app does. Nothing is invented — a country the integration
doesn't know is simply left out rather than guessed.
Security
- The Vehicle Data Scout can no longer post your VIN into a public issue (#1690).
One portal field carries a credential blob with the car's VIN encoded inside it. The Scout masks VINs by looking
for them as readable text, so it never saw this one, and the length limit that follows happened to leave the VIN
inside the part that got posted. It had leaked five times — four of those were cleaned up by hand afterwards
without the masking itself being fixed. Encoded identifiers are now detected and the whole blob is replaced before
anything is written out; what remains says only what kind of value was removed and how long it was. Already-posted
issues were redacted. Nothing about ordinary readings changes.
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:
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.