Touareg CR eHybrid (2021) – Official VW App has live data but VW Group Connect gets no vehicle data

[Bugi66]

Hi,

I'm using the latest VW Group Connect (2.17.0) with Home Assistant 2026.7.1.

I have two vehicles on the same Volkswagen account:

• VW ID.3 GTX Performance → works perfectly
• VW Touareg CR eHybrid (2021) → almost no data

The official Volkswagen iOS app shows live:

• Battery SOC
• EV range
• Fuel level
• Fuel range
• Lock status

However, VW Group Connect only creates a few entities and reports:

"EU Data Act Portal logged in successfully but no vehicle data available."

Diagnostics show:

no_data: true
_poll_failed: true

In the EU Data Act portal the difference is interesting:

• ID.3 offers a continuous 15-minute data subscription ("Custom Data Request").
• Touareg only offers a one-time ZIP download. There is no continuous subscription available.

The downloaded ZIP already contains battery SOC (RBC.vehicleStates.soc), so Volkswagen clearly provides at least some hybrid battery data.

Is the Touareg CR eHybrid currently unsupported because it uses a different backend/API, or is this something that could be added to VW Group Connect?

If required, I can provide anonymized diagnostics and the Data Act ZIP.

Thank you!

[its-me-prash]

Hey, thanks for using the integration. Are you able to provide me with the zip file, so I can review this? Have you tried our latest updates yet and it's the behaviour the same?

[Bugi66]

Hi,

thanks for your quick reply. I have attached the ZIP file exported from the VW Data Act portal.

I’m using the latest version of the integration, but unfortunately the issue is still the same. My ID.3 GTX Performance is recognized correctly, but my Touareg eHybrid is not detected and is always treated as an unknown vehicle.

If you need any additional information or logs, I’d be happy to provide them.

Thanks for your support!

20260710201413_WVGZZZCRZMD036061.zip

[its-me-prash]

Thanks so much for sending over the ZIP — exactly what we needed. Good news on one front: in v2.18.0 we've decoded the old Car-Net one-time-export format your Touareg CR eHybrid ships, so we now understand its charge level, charge mode, current limit and target temperature from your file. The honest catch: v2.18.0 doesn't yet read that off your live car — we only ever create and read the continuous 15-minute feed, and your Touareg is only offered the one-time export, so nothing gets fetched for the mapping to act on. Building that one-time-export fetch is the missing piece and my next step, so I'll keep #702 open until it works end to end.

[Bugi66]

Thank you very much for the detailed explanation and for your work on this.

It’s great to hear that you were able to decode the Touareg’s one-time export format. I’m glad the ZIP file was useful.

I understand that the missing part is now fetching the one-time export directly from the vehicle. If there is anything else I can provide to help with testing or development (additional ZIP exports, logs, screenshots, or anything else), I’d be happy to help.

I’ll keep an eye on discussion #702 and I’m looking forward to testing the feature once it’s available.

Thanks again for your support and all the effort you put into this integration!

[its-me-prash]

Hi @Bugi66 — your Touareg is only being offered the portal's one-time (ZIP) export, not the 15-minute continuous feed, which is why the normal poll finds nothing. That path is wired as two services now: vag_connect.request_historical_export creates the request, then once the ZIP is ready vag_connect.import_historical_export pulls it in. It hasn't been confirmed end-to-end against a live account yet, so if you're up for it, running those two would really help validate it. Thanks again for the export sample that made the format work possible.

[Bugi66]

Hi! I’d be happy to test it.

I looked in Home Assistant under Developer Tools → Actions, but I can’t find either vag_connect.request_historical_export or vag_connect.import_historical_export.

I’m running the latest released version (v2.18.0). Are those services already included, or do I need to install the current development version from GitHub?

[its-me-prash]

Refresh to our latest 2.19.1 which is also on HACS.

[Bugi66]

Hi! I updated to v2.19.1 and tested both new services.

I created the EU Data Act export request and then ran vag_connect.import_historical_export with my VIN. The service completed without any errors and triggered a data refresh afterwards.

Everything appears to have worked successfully from my side. Let me know if you’d like me to check anything specific or if there are any logs you’d like me to share.

[its-me-prash]

Thanks for running both services and reporting back. One thing left before this can be closed properly: does the Touareg now actually show values, in particular the charge level and the fuel readings, or are the entities still empty after the import?

The reason for asking is that the one-time export uses the older field naming, which is a different dialect from the 15-minute feed, so a clean run without errors does not by itself prove the values landed in entities. A fresh diagnostics export taken from the entry after an import would settle it either way.

If it is populated, the Touareg goes down as covered in the next release notes and this can be closed out. If it is still empty, the diagnostics will show where it stops.

[Bugi66]

Hi Prash,

I completed the historical import and generated a fresh diagnostics export.

Unfortunately, the Touareg is still not working correctly. All vehicle entities remain unavailable (SOC, fuel level, range, etc.).

One additional observation: at some point in an earlier version, the Touareg actually did show values such as the SOC and fuel level. So these values were successfully populated before. It seems that this stopped working in a later version.

Please find the diagnostics attached.

config_entry-vag_connect-01KX6PJGJQSJN896Z0J2GSQ4SX.json

[its-me-prash]

You were right, and the cause turned out to be worse than I assumed.

I went through your diagnostic and then through the code. When Home Assistant starts, the integration restores the values it saved, and the very first fetch afterwards overwrites them. That step was only protected against an outright error, and a portal response carrying no data is not an error, it is an empty but valid answer. So the empty answer was written over your saved values, and the next poll wrote that emptiness to disk.

That is exactly what you described: the values were there, then they stopped. It also explains why the historical import did not stick. You imported it, it appeared, and the next restart removed it.

The periodic polls have been protected against this for a while. The fetch that runs at startup never was. Fixed in v2.24.1.

After updating, please run the historical import once more. This time it should survive a restart. If the Touareg still stays empty after that, we are looking at a second and separate problem, and a fresh diagnostic taken at that point would be the right thing to send.