github its-me-prash/vwgroup-connect-ha v4.10.0
VW Group Connect v4.10.0

latest releases: v5.5.0, v5.4.1, v5.4.0...
one month ago

VW Group Connect v4.10.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

The stable release that gathers the whole 4.10.0 beta line (b1–b5). The headline is that the
volkswagen.de read channel works again: from the morning of 2 October the site began answering
only over HTTP/2, which returned an error for every request this integration made, and every sensor
on that channel went unavailable. It now speaks HTTP/2, and a stored login survives the update.

Alongside that, the beta line brought: a battery charge level for plug-in hybrids on the
volkswagen.de channel; sixteen more high-voltage, thermal and climate readings for cars on the raw
portal feed, plus a lot of data the portal was already sending in a shape that got ignored; a sensor
for the portal's own delivery trigger; the distance since your last fill-up; the climatisation
duration the portal sends; and fixes so a frozen timestamp from the car no longer makes fresh data
look days old, an electric car without a reported charge level no longer loses every EV entity, the
channel no longer has to be re-added after each restart, a read refused for a missing subscription
says so, cars set to miles no longer get a 1.6× service interval, and the login stops claiming your
password is wrong when it isn't. The Vehicle Data Scout can also no longer post a VIN into a public
issue.

Thanks to everyone whose reports and captures drove this line: @Joassens, @eurojojo, @fschulte2812,
@Ra72xx, @Fishermanjb, @realynot, @dasebi91, @Datendieb, @kalwados, @josie127-neu, @user222008,
@iansyder8, @DanyZdog93 and @keithellis74.

Four more fixes land on top of the betas:

Fixed

  • A volkswagen.de login that ends on an error page is no longer treated as a successful login.
    The channel considered itself connected as soon as the final page came from volkswagen.de. But the manufacturer
    serves its own error pages from that same address, and the check above it only rejects outright HTTP failures —
    so an error page delivered as a normal page passed both. Reconfiguring then looked like it had worked while
    nothing usable was stored, and the car silently ran without its volkswagen.de data. The rule that the silent
    background refresh has always applied — an address carrying an error marker is not a login — now applies to the
    interactive login too. The error marker itself is checked for plausibility before being shown, so an
    upstream-supplied value cannot ride into a log or a bug report.
  • A portal outage no longer looks like an expired session, and no longer replays your password (#465).
    Listing the cars on your account is the one portal call that has to fail loudly — an empty list would read as
    "this account has no cars" and end the setup. It did fail loudly, but as an authentication error, and the code
    that handles that has exactly one move: refresh the token or send the password again, retry, and then raise a
    "session expired" repair notice. So a portal hiccup lasting seconds sent your credentials back over the wire
    and then told you your login had gone stale. A server error now reports itself as what it is — the manufacturer's
    portal being unavailable — which skips the re-login entirely, keeps the message off the "check your password"
    track, and lets the next poll recover on its own. This is the same misdiagnosis fixed for the volkswagen.de
    channel in 4.10.0b4, one channel over, and this one sits in the primary read path for Volkswagen EU.
    A genuine 401 or 403 still means your session, and a 404 still means the data request is not provisioned yet;
    both behave exactly as before.
  • "Vehicle last reported" could run ahead of the mileage it describes, on cars whose odometer arrives under an opaque key (#1688, #529).
    The freshness work in 4.10.0b5 anchors the reported time on the odometer's own capture, so the time can never be newer
    than the reading it belongs to — otherwise Home Assistant sees the mileage change, sees the time move past it, and can
    conclude the car was driven when it was not. Finding the odometer's capture time used a list of four field names, but
    some cars deliver the odometer under one of two opaque identifiers instead. On those cars the list found nothing and
    the code fell back to the newest timestamp in the file, which is exactly the thing it was written to avoid. It now
    asks which field the odometer was actually read from, so the two cannot drift apart, and when the answer is unavailable
    it leaves the time alone instead of guessing. The same four-name list was also used by the older safeguard twenty lines
    below, which had been silently inactive on those same cars; it is now wired to the same answer.
  • A Porsche login error could print part of the server's reply into a message you are asked to share.
    When a Porsche sign-in or token refresh is rejected, the error shown in Home Assistant names the reason the
    server gave. That reason was taken from the reply and passed through unchecked, so if the server put
    something long in that field — an echoed request, or a token — it ended up verbatim in a message people paste
    into bug reports. The helper doing this was written to prevent exactly that and dropped the rest of the reply,
    but nothing bounded the one field it kept. It is now shared with the other login paths and only ever shows a
    value that actually looks like an error code; anything else reports as "no usable error code".
    Two things improve as a side effect: Porsche errors now also read the second field manufacturers use for the
    reason, which is the one carrying it in most real replies, so previously blank reasons will now be named — and
    there is one implementation of this for every brand instead of two that disagreed.

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.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:

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.

Don't miss a new vwgroup-connect-ha release

NewReleases is sending notifications on new releases.