[VW EU] Where to enable the continuous data request (portal)

[Mech0z]

I have an ID 7 in Europe, I have checked the "EU Data Act" concent on the VW Portal. But I cant see the option mentioned anywhere on the portal
"Enable the continuous data request for the specific car. Without it, the portal returns no data request for that VIN and the vehicle shows up with no readings."

In VW Group Connect — Settings I have enabled
Audi/VW push updates (beta)
Eu data act portal headless browser fallback
Eu data act auto kick off custom data request

But I dont get any data, I can only see my serial number

[its-me-prash]

Are you able to provide me with the logs from HA including the diagnostics logs from the integration? Thanks

[Mech0z]

The only log I can find in my logs is

This error originated from a custom integration.

Logger: custom_components.vag_connect.coordinator
Source: custom_components/vag_connect/coordinator.py:3068
Integration: VW Group Connect (documentation, issues)
First occurred: 8:24:07 AM (1 occurrence)
Last logged: 8:24:07 AM

VAG Connect: vehicle unreachable — entities set to unavailable (....@protonmail.com)

The diagnostics is
config_entry-vag_connect-01KWFRRWHF7B2Z2J87Z8CFFT5F.json

[its-me-prash]

Hi @Mech0z — good news: you don't need to find that option on the portal yourself anymore.

As of v2.17.4 the integration creates the continuous data request for you automatically (that's the "auto kick-off custom data request" toggle you already switched on). The old manual portal step is no longer required.

A couple of things to check:

1. Update to v2.17.5. v2.17.3 and earlier had a bug where the auto kick-off was silently rejected because the portal changed the format it expects — v2.17.4+ fixes that, so the request actually gets created now.
2. After updating, give it 15–60 minutes — the first data delivery isn't instant once the request is created.
3. The one prerequisite that is on the portal is the EU Data Act consent granted for that specific ID.7 (Data → your vehicle → consent). You mentioned you ticked the consent, so that part should be covered.

The coordinator.py:3068 line you saw is just the normal "no data this poll" warning, not the cause.

If it's still empty after updating + waiting, please grab a debug log and I'll dig in:

logger:
  logs:
    custom_components.vag_connect: debug

[Mech0z]

Tried updating and adding that log part and rebooted and have waited over an hour now

default_config:
themes: !include_dir_merge_named themes

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

http:
use_x_forwarded_for: true
trusted_proxies:
- 127.0.0.1
- ::1
- 192.168.1.225

logger:
logs:
custom_components.vag_connect: debug

But see nothing in the log :/

config_entry-vag_connect-01KWFRRWHF7B2Z2J87Z8CFFT5F.json

[its-me-prash]

Hi @Mech0z — you were completely right, the README was misleading. That "enable the continuous data request" switch it told you to look for doesn't actually exist: the integration creates that request itself, the auto kick-off is on by default (not opt-in), and the 1-month subscription it registers is free — so you weren't missing anything. I've corrected the README in v2.18.0 across all 12 languages. Thanks a lot for flagging it — this had been confusing people!

[its-me-prash]

Hi @Mech0z — that switch doesn't exist anymore, and you don't need it: the integration creates the continuous data request for you automatically (since v2.17.4). Make sure the EU Data Act consent is granted for the vehicle on the portal, update to v2.19.0, and give it 15-60 minutes for the first data to arrive. Until then you'll only see the VIN and a 'no data this poll' notice.

[Mech0z]

Hi @Mech0z — that switch doesn't exist anymore, and you don't need it: the integration creates the continuous data request for you automatically (since v2.17.4). Make sure the EU Data Act consent is granted for the vehicle on the portal, update to v2.19.0, and give it 15-60 minutes for the first data to arrive. Until then you'll only see the VIN and a 'no data this poll' notice.

Installed 2.19.0 but still dont have access :/ I havetn been out driving today though, only charged the car, not sure if thats important.

Under https://eu-data-act.drivesomethinggreater.com/ I have

You have successfully verified your usership
You can now make data access requests under EU Data Act

And on https://vwid.vwgroup.io/account I have
Concent for EU Data Act

In logs I have 1 error

Log details (WARNING)
This error originated from a custom integration.

Logger: custom_components.vag_connect.coordinator
Source: custom_components/vag_connect/coordinator.py:3282
Integration: VW Group Connect (documentation, issues)
First occurred: 12:11:27 PM (1 occurrence)
Last logged: 12:11:27 PM
VAG Connect: vehicle unreachable — entities set to unavailable (xxxx@xxx.com) <--- This is the same email as I login to https://vwid.vwgroup.io/account

Under HA settings I have the following "repair" warning/error

The EU Data Act portal signed in for volkswagen but isn't returning any vehicle data yet.

Usual causes:

A VW-side outage. VW reported an all-brands EU Data Act portal outage from late May 2026 (their notice: the data-extraction infrastructure failed under load). While it lasts the portal returns empty data for every tool, not just this integration, and it has been recovering brand by brand.
No data request set up. The portal only delivers once you create a continuous data request for your car.
The car hasn't sent anything new. A fresh dataset is only published after the car has been driven, charged, or locked/unlocked.

Quickest check: open eu-data-act.drivesomethinggreater.com in a browser and sign in. If you see no data for your car there either, it's the VW side — nothing this integration can do until VW restores it. If there is no data request, create a continuous (15-minute) one, tick all data clusters, then drive or wake the car and wait an hour or two.

This is the read-only portal beta — the warning clears by itself once data arrives.

config_entry-vag_connect-01KXSZFK0PB2ZJ411CGQHHQYEY.json

[its-me-prash]

Good news — you don't have to create the continuous data request yourself; the integration does that for you automatically. The one thing you do need is to grant the EU Data Act data-sharing consent for the car, once, on the VW/Audi data portal — until that's granted the request exists but stays empty. v2.19.1 reworks the in-app "no data yet" help so it now leads with exactly this consent step. Update, grant the per-vehicle consent on the portal, give it a bit to start reporting, and it should fill in.

[Mech0z]

Good news — you don't have to create the continuous data request yourself; the integration does that for you automatically. The one thing you do need is to grant the EU Data Act data-sharing consent for the car, once, on the VW/Audi data portal — until that's granted the request exists but stays empty. v2.19.1 reworks the in-app "no data yet" help so it now leads with exactly this consent step. Update, grant the per-vehicle consent on the portal, give it a bit to start reporting, and it should fill in.

Sorry for the late reply, but I still dont have it working :/

At https://eu-data-act.drivesomethinggreater.com/de/en/user/details.html I get the following message

You have successfully verified your usership
You can now make data access requests under EU Data Act

Not sure if I need to do more on that portal though?

I have this error in my logs

This error originated from a custom integration.

Logger: custom_components.vag_connect.coordinator
Source: custom_components/vag_connect/coordinator.py:3530
Integration: VW Group Connect (documentation, issues)
First occurred: 11:03:51 AM (1 occurrence)
Last logged: 11:03:51 AM
VAG Connect: vehicle unreachable — entities set to unavailable (m***@***.com)

config_entry-vag_connect-01KXSZFK0PB2ZJ411CGQHHQYEY(1).json

[its-me-prash]

hey @Mech0z, thanks for the fresh diagnostics. good news first: the integration is set up fine, it has your car and it's polling the portal every cycle, the portal is just handing back nothing yet (no_data), which is why everything shows unavailable. that coordinator.py:3530 line is unrelated, you can ignore it.

the page you're on (user > details) only confirms your usership is verified, that's step 1. the bit that actually opens the data tap is a separate, per-car consent: go to Fahrzeugübersicht (vehicle overview) on that same portal, open your ID.7, and grant/confirm the EU Data Act data-sharing there. usership-verified but car-not-consented is exactly the "requests work but stay empty" state you're in.

can you check that page and tell me: does your ID.7 show data-sharing as active/granted, or is there a consent toggle there you haven't flipped yet? that tells me whether it's the consent step or something car-side. and since the ID.7 is a really new model, even once consent is on it can take a drive cycle or two before the first continuous report lands.

[Mech0z]

hey @Mech0z, thanks for the fresh diagnostics. good news first: the integration is set up fine, it has your car and it's polling the portal every cycle, the portal is just handing back nothing yet (no_data), which is why everything shows unavailable. that coordinator.py:3530 line is unrelated, you can ignore it.

the page you're on (user > details) only confirms your usership is verified, that's step 1. the bit that actually opens the data tap is a separate, per-car consent: go to Fahrzeugübersicht (vehicle overview) on that same portal, open your ID.7, and grant/confirm the EU Data Act data-sharing there. usership-verified but car-not-consented is exactly the "requests work but stay empty" state you're in.

can you check that page and tell me: does your ID.7 show data-sharing as active/granted, or is there a consent toggle there you haven't flipped yet? that tells me whether it's the consent step or something car-side. and since the ID.7 is a really new model, even once consent is on it can take a drive cycle or two before the first continuous report lands.

[its-me-prash]

Thanks for the screenshots, that clears it up. Both the important bits are done on the portal side: your usership is verified, and the EU Data Act permission toggle on the vehicle page is on. So this is not a consent gap.

What's left is just the data actually starting to flow. The ID.7 is a very new model, and even once permission is granted the portal can take a drive cycle or two before the first continuous report lands. So the honest answer is: give it a bit of driving and it should start filling in. If it's still completely empty after, say, a few days and a couple of proper drives, let me know and we'll dig into whether the request itself needs a nudge.

[its-me-prash]

@Mech0z — following up: since your screenshots already prove usership + per-car consent are fully on, and the portal still returns no data, this is looking like a VW-side / very-new-model provisioning gap rather than anything in your setup. If it's still empty after a few more drive cycles, that's worth noting as a datapoint (some brand-new models take a while before VW starts populating the EU-Data-Act feed) — not a config you can fix. If it does start returning data, a quick note here helps me confirm the parse end-to-end.

[Mech0z]

Year we will see if it ever starts working :/ I just keep updating the plugin

[Mech0z]

Just to give an update, still don't work, but I tested the other HACS https://github.com/robinostlund/homeassistant-volkswagencarnet and that one works fine, so they must be doing something different, not sure what though

[its-me-prash]

Thanks for the update, @Mech0z — and that's a genuinely useful datapoint, because it tells us where your ID.7's data is coming from.

The difference isn't a trick we're missing — it's a different data source. The other integration reads through the manufacturer app's own backend (the modern CARIAD one), and for a brand-new ID.7 that backend does carry live SoC/range while the EU Data Act portal — the path we use for VW EU reads — hasn't provisioned your car into its feed yet. Same car, two different pipes; yours happens to be full on one and empty on the other.

Here's the honest part: this integration did have that app-backend read path — the opt-in "VW EU Two-Way" channel read live values straight off that backend. Volkswagen disabled the login it relied on on 2026-08-18 — the same window you were testing — so it can no longer be set up on any version right now. That's the whole reason we lean on the EU Data Act portal for VW EU, and it's why, for a very new ID.7 the portal doesn't feed yet, we currently can't match that other source. It's not that we're reading it wrong; the pipe we'd read it from was closed by VW a few days ago.

I'm working the durable replacement paths, and a car like your ID.7 is exactly the one that benefits the moment a live read path reopens. Until then, on the portal side the only lever is time — some brand-new models start feeding after a few more drive cycles. If yours flips from empty to populated at some point, that timing is itself a useful signal, so do let me know.

[Mech0z]

Thanks for the update, @Mech0z — and that's a genuinely useful datapoint, because it tells us where your ID.7's data is coming from.

The difference isn't a trick we're missing — it's a different data source. The other integration reads through the manufacturer app's own backend (the modern CARIAD one), and for a brand-new ID.7 that backend does carry live SoC/range while the EU Data Act portal — the path we use for VW EU reads — hasn't provisioned your car into its feed yet. Same car, two different pipes; yours happens to be full on one and empty on the other.

Here's the honest part: this integration did have that app-backend read path — the opt-in "VW EU Two-Way" channel read live values straight off that backend. Volkswagen disabled the login it relied on on 2026-08-18 — the same window you were testing — so it can no longer be set up on any version right now. That's the whole reason we lean on the EU Data Act portal for VW EU, and it's why, for a very new ID.7 the portal doesn't feed yet, we currently can't match that other source. It's not that we're reading it wrong; the pipe we'd read it from was closed by VW a few days ago.

I'm working the durable replacement paths, and a car like your ID.7 is exactly the one that benefits the moment a live read path reopens. Until then, on the portal side the only lever is time — some brand-new models start feeding after a few more drive cycles. If yours flips from empty to populated at some point, that timing is itself a useful signal, so do let me know.

Cool, but just FYI my ID.7 is from mid 2024, so not that new :)

[its-me-prash]

Thanks for the correction — you're right, a mid-2024 ID.7 is not "brand new", so "not provisioned yet" doesn't fit your case. Let me give you the straight version.

For your ID.7 the EU Data Act portal is coming back empty, and that's a VW-side provisioning gap: the portal simply isn't publishing a data slice for that car yet (it varies car-to-car and widens over time as VW expands coverage), rather than something the integration is failing to read.

As for the other integration reading your car fine — that one works because it reads VW's CARIAD app backend directly (the same path the official app uses), not the EU Data Act portal. We had that app-backend login too, but VW shut it down on 2026-08-18, so it's no longer a route we can rely on for new setups. It isn't a trick we're missing — it's a different door, and VW has been closing it. Where that backend still answers (older Car-Net cars), we do use it; for a modern ID.7 it's exactly the door VW just locked.

So honestly, for your ID.7 today the portal is the available path, and it's on VW to populate it. If a live read route reopens, your car is exactly the kind that would start working. Appreciate you pushing on this.