VAG Connect v3.0.2
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
A round of fixes driven entirely by reporter diagnostics in the hours after 3.0.0: two cross-brand sentinel screens (charging type and odometer), Volkswagen US climate + door-lock mapping, volkswagen.de sessions that finally survive a restart, a diagnosable EU data-request creation, and the Škoda push channel that can now actually start. Thank you to everyone who sent logs and diagnostics.
Fixed
- A battery level that shows up several times in one data export now settles on the value the export repeats, not a lone stale copy. Some Volkswagen EU exports list the state of charge more than twice under one capture time with no per-point clock to separate them — for example 71 once and 60 twice. The integration now treats a value the export repeats as the real reading and keeps it, instead of possibly latching onto the single odd-one-out when your last known level happened to sit near it. A genuine two-way tie (each value once) is unchanged and still reconciles against your last known value. Thanks @PeterPrelo for the export that showed the three-way case.
- Volkswagen US/Canada: the climate temperature and the door-lock state now show up. Both were in the data the car sent all along. The target temperature arrives wrapped together with its unit (70 °F, for example) and the reader only understood a plain number, so it came out empty — the same wrapped shape this integration itself sends when you set the temperature. The lock state is reported per door on this firmware, in a form the reader mistook for a single value and then discarded, so the lock showed Unknown even with all four doors reporting locked. Thanks @fg877khkv8-maker for the diagnostics that showed exactly this.
- Škoda push updates can actually start now. The near-real-time push channel for Škoda needs the account id to subscribe, and the Škoda client never picked one up — so the channel quietly refused to start on every setup, without a single line in the log to say why. Škoda now captures that id the same way SEAT/CUPRA and VW US/CA do, and the skipped-setup case explains itself in the debug log. Push is still an opt-in beta and the Škoda handshake may yet need more work, but it can now be attempted at all. Thanks @thiete, who found this by reading the code.
- Creating the EU data request explains itself when it fails — and now tries to recover. The button that sets up the 15-minute data feed could fail with nothing useful in the log. The portal actually runs two separate sign-ins behind one address: one for reading your data, one for the page itself. Your session can be perfectly valid for reads while being signed out for the page — and the piece needed to create a request lives on the page side. The log now says plainly which of the two is missing, and the integration reloads the portal page once to try to restore it before giving up. Thanks @Jradon001, whose log made this findable.
- volkswagen.de sessions now actually survive a restart. Two more faults in how the saved session was restored: a sign-in cookie meant for the whole
vwgroup.iofamily was being pinned to a single address, so other steps of the sign-in never received it; and the cookie that has to reach both sites was only ever arriving at one of them, because the same object was reused for both — meaning the part this was written to guarantee had silently never worked. Both are fixed, which should end the repeated re-add prompts for good. - The volkswagen.de channel no longer asks to be re-added over and over. After signing in with the e-mail code, the channel could immediately report its session as expired — so the repair notification came straight back, and re-adding it produced the same result forever. The check that decides whether the session resumed was reading the whole callback address, so a perfectly good sign-in was mistaken for an expired one whenever that address happened to mention the login page. It now looks at where you actually landed. The session is also kept fresh while it is in use, instead of only being renewed after a read has already failed. Thanks @fight3, @shaarkys and @Jradon001 for the logs that made this findable.
- A newly-discovered field the car sends now says which reading it belongs to. The data portal packs about ten different opening states — doors, windows, sunroof, boot, bonnet — into one generic
openfield, told apart only by an internal id. The Vehicle Data Scout was showing justopen: true, so every reporter filed an identical row that nobody could act on. The report now names that id, which is what lets a field like this actually get mapped. Thanks to everyone who kept sending these in. - The "update interval too short" message no longer asks you to raise an interval you already exceed. A Škoda owner who had already gone up to 31 minutes kept being told to raise it to 30 minutes or more, which reads as nonsense. The suggestion now always steps up from the value you actually have configured. Thanks @starwarsfan.
- The charging-type sensor no longer shows "invalid". When the backend has no charge type to report it sends an
invalidplaceholder, and that was being shown as if it were a real charging type — so the history painted "invalid" bands, often for ten minutes at a time while the car sat parked and not charging. It's now dropped on every brand: Volkswagen, Audi, Škoda, SEAT, CUPRA, Bentley, whether the data comes from the brand backend or the EU data portal. The sensor simply stays clear until a real type comes back. Thanks @Lagaff86, whose Recorder audit of 90 occurrences pinned the pattern down — and who caught that the first attempt only covered one of the four data paths and left his own car unfixed. - The odometer no longer reads 429 million kilometres. When the backend has no mileage to report it sends a placeholder — the largest value a 32-bit field can hold, scaled down by the field's unit to
429,496,729— and that was surfaced as if it were a real reading, so the odometer jumped to an impossible number and stuck there. It's now recognised as the placeholder it is and screened out on every brand and every data path (EU data portal, brand backend and volkswagen.de alike), so an absurd value can't land — exactly the same one-guard-everywhere approach as the charging-type fix above. Thanks @dpk1987, whose diagnostics gave the exact figure that pinned it as a sentinel.
Internal
- The data-dictionary watcher no longer opens an empty pull request when Volkswagen only re-publishes the source page. The automation that watches the EU-Data-Act dictionary was treating any change to the source page as a new dictionary, even a cosmetic re-deploy — which produced a pull request whose only real difference was the date. It now regenerates only when the dictionary's version or download links actually change (the PDFs are versioned in their own filename), and treats a same-version page change as noise. No user-facing effect.
Full diff vs v3.0.1 / Kompletter Diff zu v3.0.1
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.