VW Group Connect v4.10.0b3
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
- The distance since your last fill-up is now a sensor (Vehicle Data Scout, #1655 and nine more reports — thanks @user222008, @iansyder8, @DanyZdog93, @Nicohlav, @Neurupp2, @4ndy-bo and @checkner89).
Ten reports from seven accounts kept naming the same unmapped value, and it is in none of the 6610 entries of
the manufacturer's own field catalogue, so for a week it was held rather than given a guessed meaning. Three
things settled it. @iansyder8 happened to report the same car twice in one day, five and a half hours apart,
with the value sixteen higher — so it counts up as you drive. The catalogue documents its two siblings as the
car's short-term and long-term trip memories, both in kilometres, which fixes the unit. And @DanyZdog93 pinned
the meaning from his dashboard: it is the counter with the fuel-pump icon, resetting when he refuels rather
than at the start or end of a trip. The manufacturer's own app agrees — it has a whole screen for this memory,
labelled "From refuelling" and described as "all journeys between two fill-ups" (on a hybrid, "from charging
or refuelling").
Diagnostic, off by default, and deliberately not wired to the odometer: the two are different quantities, and
filling the odometer from a counter that resets would be a confident wrong answer on every car that has reset
it. For the same reason the sensor records the value without claiming a long-term total. One thing is still
open and asked in #1578: on a pure electric car nothing seems to reset it, so there the name is the closest
honest label rather than the whole truth. - The climatisation duration the portal sends is visible instead of swallowed (Vehicle Data Scout, #1689 and thirteen more reports).
Twelve accounts reported this leaf, and the catalogue does not document it either. "Duration" could be how long a
climatisation run lasted, how long one was configured for, or how long is left — three different sensors with three
different units. All fourteen reports read zero, and in the seven that also carried the climatisation state it was
off, which hints at a run time without proving it. Rather than invent a unit, the raw number gets its own sensor with no unit at all and
"(raw)" in its name, off by default, and it is kept well away from the climate ETA sensor beside it, which is
documented in minutes. A leaf nobody maps is re-reported on every poll, which is how fourteen issues happened.
Fixed
- The volkswagen.de channel works again: the site now requires HTTP/2 (#1679, thanks @eurojojo; #1313, thanks @fschulte2812; #1659, thanks @Joassens).
Since early October every request to volkswagen.de's app endpoints came back with a 502, which took the whole
volkswagen.de channel down — logins, vehicle reads, everything. The cause is not the login, the account or the car:
the site stopped answering those paths over HTTP/1.1 and now serves them only over HTTP/2. Browsers negotiate that
automatically, the library this integration uses for every request speaks only HTTP/1.1, so it hit a wall it could
not see. @eurojojo found it and proved it with a side-by-side of five different clients; @fschulte2812 and
@Joassens then confirmed independently that reads, a credential login and an e-mail code all work over HTTP/2.
This channel now speaks HTTP/2, and only this channel — nothing else in the integration changes. Your saved login
is reused as before: the cookies live where they always did, so no re-adding and no new e-mail code. - A server outage no longer gets reported as an expired session (#1679, #1313).
The same 502 was being read as "your session died", because the error came back for the login address itself and
so looked like a login page. Two things followed from that, and both were worse than the wrong message. The
integration replayed your stored password to recover — which on accounts that use e-mail codes sent you a code for
nothing — and it then told you to re-add the channel, while the saved session was in fact still perfectly valid.
@fschulte2812 proved that: his three-day-old cookies resumed on the first try once the transport could reach the
site. A server error now says so plainly, leaves the saved login untouched, never replays the password, and simply
retries on the next poll. - A single junk number from the portal could discard a whole snapshot.
JSON allows the bare literalsNaNandInfinity, and the portal is parsed as JSON, so one of those really can
arrive in a reading. It then flowed straight through the parser's number conversion — where turning it into a whole
number raises an error, and that aborted the mapping of everything else delivered in the same snapshot. If it did
land in a sensor instead, it made the diagnostics download invalid JSON, so the dump attached to a bug report could
no longer be read. The same literal in a capture-time field was worse again: that value is the sort key for picking
the freshest of several readings, and since every comparison against it is false, "freshest" became arbitrary — and
if it reached the last-seen anchor, the freshness check itself raised. Non-finite values are now dropped where they
are converted, like any other unusable reading, and everything sent beside them survives. Found by a test written
for the duration sensor above. - A negative reading from the car's trip computer no longer reaches a distance or duration sensor.
Three of the trip-computer values already ignored a negative reading; their twenty-odd siblings did not, so a
negative could land on a sensor where it makes no sense — a trip distance below zero, a negative travel time, a
negative average speed — and from there into long-term statistics, where it stays. Sixteen of those values now
ignore a negative reading, and a plain zero still counts as real (a trip that was just reset genuinely reads zero).
Decided value by value rather than by family name, because this family is mixed in two directions. The service and
oil countdowns are documented as going negative: once you pass the interval, the manufacturer sends how far you
have driven since, as a negative number, and the integration already turns that into a positive "overdue by" —
a blanket rule would have replaced a real overdue service with no reading at all. In the other direction, the
average monthly distance carries the maintenance prefix but is a distance you drove, so it does get the guard.
Left alone on purpose: electric, auxiliary and recuperation averages, which are net-energy figures — a downhill
trip can recover more than it uses, so a negative there may be the truth. - Cars set to miles no longer get a 1.6x service interval, oil interval, monthly average or last-trip distance.
A UK or US car's portal feed says which unit the car displays, and the integration used to convert every distance
it had mapped whenever it saw "miles". But only some of the portal's distances actually follow the car's display:
the manufacturer's own field catalogue gives a unit companion to exactly eight data points — the odometer, a
generic distance, the two estimated cruising ranges, the per-engine range list, the two service-due values and tyre
pressures — and documents every other distance as kilometres outright, several of them spelled out as "always in
km". So four readings were being multiplied although they already arrived in kilometres: the distance to the next
service and to the next oil change, the average monthly distance, and the last trip. On cars that report their
ranges under the catalogue's kilometre-documented names, the range sensors were inflated the same way.
Whether a value needs converting is now decided from the field it came from rather than from the sensor it feeds —
which matters because most of these sensors can be filled from either kind of field, sometimes on the same car.
Nothing changes for a car reporting kilometres, the odometer still converts as before, and readings from the older
flat payload dialects — which is where the conversion was originally established from real cars — keep converting
too, since nothing documents those either way.
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.