Hi, do I need to have VW Connect Plus activated (€11.90 per month or €265.00 every 2 years) for it to work?
No — Connect Plus isn’t required. The portal FAQ only asks for a brand account (VW ID etc.) and Primary User role; access is free under the EU Data Act. You do need an active continuous 15-minute request on the portal and a car that’s online enough to upload data. Connect Plus is the paid app package for remote control — unrelated to this read-only integration.
Hi!
Range: It's missing from the json as well. If you're interested, I can share the full json as reference for the ID.7.
Battery: It's pointing to 2 different entity IDs, but not really clear what it is:
Entity
State
Device
Area
Attributes
sensor.id_7_pro_batterie
Batterie
49
ID.7 Pro
Garten
state_class: measurement
unit_of_measurement: %
device_class: battery
friendly_name: ID.7 Pro Batterie
sensor.id_7_pro_batterie_2
Batterie
49.0
ID.7 Pro
Garten
state_class: measurement
unit_of_measurement: %
device_class: battery
friendly_name: ID.7 Pro Batterie
Hope this helps!
Johannes
Hi @jnehrk — thanks, this helps!
Two “Batterie” sensors: That matches what we expected. They are two different portal fields:
battery_state_report.soc→ integer SoC (your…_batterie, 49 %)battery_level_HV.value→ HV battery level with one decimal (your…_batterie_2, 49.0 %)Both are valid; the confusing part is the German name — we’re missing a translation for the HV field, so HA shows both as “Batterie”. Will fix in the next release (
HV-Batteriestand/HV battery level).Range: The integration currently exposes electric range only for
range.valueandvalue_of_the_primary_range. On ID.7, range is often inbattery_state_report.cruising_ranges.*.rangeinstead — we don’t map that yet.You wrote range is missing from the JSON entirely — could you search your file for
cruising_rangesorrange? If those fields exist, it’s a mapping gap we can fix; if not, the portal isn’t delivering range for your car yet.Yes please — a redacted JSON/ZIP via GitHub issue (VIN removed) would be perfect for ID.7 range mapping. Thanks!
I will test with a Golf 8 as well, as soon as I don't get "request failed" messages from the portal. 
For me it looks like there's a current problem on the portal, for my both cars last files where received >20 hours ago.
Also In portal itself no files are visible.
1 Like
@roudini , @cameron I thought it's only for me but indeed last file I had after 16pm yesterday (GMT) but while ago got new one again.
@TommiG1 Now I have even 121 entities 
In my case it was not required to drive nor charge, ignition in the evening and seems like after 30-60 minutes full data appeared. Maybe drive/charge helps to speed up this but I'm not sure.
Temp / units: Units make sense 
, temp value also makes sense, it looks like 'diagnostic' value doesn't match real value from the other field.
I'm going to post edited file in a moment after download available again after outage.
BTW I like 'repairs' or issues which appear in HA when there is no access to files and when no data for more than 12 hours 
Well done! Idea for improvement - maybe we can have these timeouts configured in settings? At the moment I'm OK with default values but some user's may find tweaking handy.
Hello
Too bad I’m not getting any data but the VIN… I have an « old » VW Passat from 2017 and I think WeConnect is mandatory for cars that are « very » old…
I have requested all data in one request (not periodically) but I haven’t received any files either since the request (2 days ago)
I already get error messages at the portal. In VW connect portal, I agreed to share data under this EU data act.
All back up and running for me.
1 Like
I again don't receive updates since 2026-06-17 12:30 UTC.
Seat app is up to date, so car seems to send datta
Hi @levican506 — thanks for testing with the ID.7.
What you’re seeing is expected right after setup, not a broken integration. Your screenshot shows Integration status: Empty snapshots only — login and the portal subscription are fine (364 days left), but the portal has only delivered empty _no_content_found snapshots so far, so Home Assistant has no vehicle fields to create yet.
The entities you see are the built-in diagnostics (status, subscription, timestamps, etc.). Real sensors (battery, temperature, charging, …) appear automatically once a ZIP with actual telemetry arrives — no need to remove and re-add the integration.
We already have a successful ID.7 test in this thread (@jnehrk): full data worked after the portal started delivering real snapshots. Other testers saw a similar slow start (e.g. ~11 entities first, ~120 after a few hours / overnight).
Please double-check on the portal:
• Continuous 15-minute request active for this VIN
• Dataset All Data (not only Charging)
• Vehicle linked under Data clusters → Vehicle overview
• Car recently online (ignition, short drive, or open the VW app)
First real data is often 15–60 minutes, sometimes a few hours. Empty snapshots are normal when the car sent nothing in a 15-minute window.
If it’s still only empty snapshots after ~24 h with the car awake, let us know the integration status value and whether the portal shows real ZIPs (not only _no_content_found).
Thanks!
Tommi
Hi everyone,
I am testing the new beta portal for the VW Group EU Data Act with my ID.3, but I am running into an issue where the data in Home Assistant gets stuck and becomes stale, even though the car has been driven recently.
Right now, my dashboard claims the car hasn't been connected for about 9 hours.
Here is what I have observed and tested so far:
- The Setup: My portal configuration is active with a Continuous Data Request set to
Every 15 minutesforAll Datawith no end date. The integration is configured with my VIN asPRIMARY_USER. - The Official App Works: If I pull down and refresh the official MyVolkswagen app, it updates instantly and shows the correct status (e.g., current battery is at 23%).
- The Data Act Portal is Stale: When checking the raw JSON payload downloaded from the EU Data Act portal, the values are completely stuck in the past. For example, it still reports
battery_state_report.socat34and theinstrument_cluster_timeis locked to exactly11:57:11from this morning.
What I have tried to force an update:
- Confirmed that the privacy/online status in the car's infotainment system is fully enabled.
- Made sure to actively press "OK" on the welcome/profile screen when starting the car to avoid the restrictive "Guest" mode.
- Completely deleted the data package request on the EU Data Act portal and recreated it from scratch to clear any stuck API cache.
Despite all of this, the Data Act portal refuses to fetch the live data that the official VW home-servers clearly already have.
It seems like there is a major sync-delay or a missing trigger between VW's internal vehicle backend and the new Data Act mirror/B2B layer, causing the cron-jobs on VW's side to stop pushing data over.
Is anyone else experiencing this massive latency on the MEB platform, or is there a known trick to force the VW backend to sync the Data Act cluster when the car finishes a trip?
Thanks for the thorough report — this is very helpful.
Your comparison (MyVolkswagen app fresh vs. raw EU Data Act JSON stale) strongly suggests the issue is upstream on VW’s side, not in Home Assistant. The integration only mirrors what the portal delivers; if battery_state_report.soc and instrument_cluster_time are frozen in the portal export itself, HA cannot fix that.
A few other beta testers recently hit temporary portal problems (downloads/listing unavailable for a while). We don’t know how deep that outage went — it may have affected only the portal API, or also the backend sync into the Data Act mirror. Your symptoms (new ZIPs arriving, but vehicle timestamps hours old) could be a sync backlog after such an incident, not a misconfiguration on your end.
That is different from HA showing listing_failed (HTTP 5xx, no datasets at all) — but both point to VW infrastructure, not the integration.
There’s no known client-side trick to force a backend resync after a trip. I’d wait a bit longer after any recent outage, and if it stays stuck, report it to VW via the portal with: MEB/ID.3, continuous 15‑min “All Data”, PRIMARY_USER, and that raw portal JSON lags the MyVolkswagen app by X hours.
For debugging in HA: if Dataset generated is recent but Last connected / Last vehicle update are old, that confirms stale portal content rather than a polling problem.
1 Like
I’ve got exactly the same as you described. Already reinstalled the latest version but no difference.
The app tells me the current battery range is 87% but the VW EU data act json still report 58% since 15.00u today
1 Like
