# \[APP\]\[Pro\] VW Group Vehicles - Access your vehicle data via the EU Data Act portal for VW, Audi, Škoda, SEAT, Cupra and Bentley

**URL:** <https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345>\
**Category:** Apps\
**Tags:** homey-pro\
**Created:** [June 19, 2026, 6:17pm UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345 "2026-06-19T18:17:50Z")\
**Posts on this page:** 20\
**Page:** 6

<div class="post-metadata">

**Author:** ![Tobi\_Wo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tobi_wo/32/168169_2.png) [@Tobi\_Wo](https://community.homey.app/u/Tobi_Wo)\
**Post date:** [August 2, 2026, 7:13pm UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345/104 "2026-08-02T19:13:45Z")

</div>

Hi Andi,

thanks for your nice work.  
I see the data polled from the data portal in the JSON in debug, but it is not transfered to the capabilities in my case.

70417691-97c6-463e-bcd6-9023cae4f979

Cheers  
Tobias

---

<div class="post-metadata">

**Author:** ![Andi](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andi/32/160466_2.png) [@Andi](https://community.homey.app/u/Andi)\
**Post date:** [August 2, 2026, 10:04pm UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345/105 "2026-08-02T22:04:03Z")

</div>

Could you please share your JSON data (under app settings)?

---

<div class="post-metadata">

**Author:** ![Tobi\_Wo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tobi_wo/32/168169_2.png) [@Tobi\_Wo](https://community.homey.app/u/Tobi_Wo)\
**Post date:** [August 3, 2026, 4:56am UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345/106 "2026-08-03T04:56:04Z")

</div>

Sure 😊

{  
“vin”: “TMBJH9NY1xxxxxxxx”,  
“user\_id”: “dc964aac-6e08-xxxx”,  
“Data”: [  
{  
“key”: “0a18a053-b4b0-3db1-be44-a6c5dba629b1”,  
“dataFieldName”: “currentSoc”,  
“value”: “59”,  
“timestampUtc”: “2026-07-31T06:41:17.181Z”  
},  
{  
“key”: “62a0652d-2dae-32af-9404-4879cf6f669a”,  
“dataFieldName”: “persLocation”,  
“value”: “[51.042301,8.67465]”,  
“timestampUtc”: “2026-07-31T06:41:17.196Z”  
},  
{  
“key”: “8a5df67d-839f-3117-be3b-6f09d345ebfa”,  
“dataFieldName”: “shortTermAverageConsumption”,  
“value”: “14.4 kWh/100km”,  
“timestampUtc”: “2026-07-31T06:41:27.084Z”  
},  
{  
“key”: “bfd914a7-e030-3dc1-99f4-93d3b945da07”,  
“dataFieldName”: “speed”,  
“value”: “0”,  
“timestampUtc”: “2026-07-31T06:41:27.228Z”  
},  
{  
“key”: “5150d35f-9f5d-3f61-b8d5-8bdca8178448”,  
“dataFieldName”: “tripId”,  
“value”: “fdca8c5e-9828-4f26-8cc4-db9b504acb8e”,  
“timestampUtc”: “2026-07-31T06:37:22.774Z”  
},  
{  
“key”: “56bc8dc1-e326-3da8-b0d0-8c5519001c17”,  
“dataFieldName”: “heading”,  
“value”: “159”,  
“timestampUtc”: “2026-07-31T06:41:27.228Z”  
},  
{  
“key”: “85807008-0add-3e9c-86a7-949a07334e8c”,  
“dataFieldName”: “ignition”,  
“value”: “keyContact”,  
“timestampUtc”: “2026-07-31T06:41:27.084Z”  
}  
]  
}

Skoda Enyaq from 2025, all data selected on EU data portal.

Cheers

Tobias

---

<div class="post-metadata">

**Author:** ![Lifevolution](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lifevolution/32/168063_2.png) [@Lifevolution](https://community.homey.app/u/Lifevolution)\
**Post date:** [August 21, 2026, 7:23am UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345/107 "2026-08-21T07:23:07Z")

</div>

has anyone else encountered the issue of the same datafield occuring multiple times in the same JSON file? I have 2 SOC-values in the file and the first one (86%) is an old value that keeps on popping up and the Homey app reports that one instead of the current value (76%). I also contacted the [drivesomethinggreater.com](http://drivesomethinggreater.com) about it, but am still waiting for a reaction.

```auto
  "key": "7bddd5e7-43a4-3878-bd63-9502782f77a5",
  "dataFieldName": "battery_state_report.soc",
  "value": "86"

 "key": "506cb83e-f99f-3af3-bbeb-0429b69a78d9",
  "dataFieldName": "battery_state_report.soc",
  "value": "76"

```

---

<div class="post-metadata">

**Author:** ![Bug](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bug/32/16493_2.png) [@Bug](https://community.homey.app/u/Bug)\
**Post date:** [September 2, 2026, 7:43pm UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345/109 "2026-09-02T19:43:17Z")

</div>

according to the documentation:

the first one is “State of Charging when charging is started”

the second one is “The int value of “battery state report soc””

the second value should be used for the SOC displayed in the app for your car.

for my hybrid Golf 8.5 GTE it reports the SOC fine in the app by the way…

---

<div class="post-metadata">

**Author:** ![Andi](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andi/32/160466_2.png) [@Andi](https://community.homey.app/u/Andi)\
**Post date:** [September 2, 2026, 7:57pm UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345/110 "2026-09-02T19:57:30Z")

</div>

@Bug Thank you for the hint

@Lifevolution Please check new TEST version: [VW Group Vehicles | Homey](https://homey.app/a/com.vwgroup.vehicledata/test/)

---

<div class="post-metadata">

**Author:** ![Lifevolution](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lifevolution/32/168063_2.png) [@Lifevolution](https://community.homey.app/u/Lifevolution)\
**Post date:** [September 4, 2026, 9:58am UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345/111 "2026-09-04T09:58:41Z")

</div>

Hi Andi, great update, and @Bug thanks for the helpful insight!

The result is dat when both values are in the JSON, the first one (= the right one, also identified by the key) is being used. Unfortunately this morning I noticed that the second SOC value was being used. When I looked at the JSON file the “first one” was not in there at all, so only the second SOC was being reported and apparently that value then is used. I don’t know how to resolve this issue, other than always exclude a certain key?

---

<div class="post-metadata">

**Author:** ![Andi](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andi/32/160466_2.png) [@Andi](https://community.homey.app/u/Andi)\
**Post date:** [September 4, 2026, 3:41pm UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345/112 "2026-09-04T15:41:42Z")

</div>

Good catch — you’re right, and that’s now fixed in 0.0.49.

The charge-start value is never the current SOC, so falling back to it was wrong in principle. It’s now dropped entirely instead of just deprioritised. When a dataset contains only that entry, the app reports no SOC for that poll and keeps the last real measurement — an older but genuine value rather than a charge-start number that could be days old. The next valid dataset takes over immediately.

I deliberately excluded only that one key rather than whitelisting “known good” ones — otherwise vehicles whose live SOC arrives under a key I haven’t catalogued would stop reporting altogether.

One open question: your data also had a third key, `93b55324-…`, reading 90 where 84 was correct. I’ve left it alone since I’ve only seen it once. If it turns up again next to a known-correct value, let me know.

> **[VW Group Vehicles | Homey](https://homey.app/en-us/app/com.vwgroup.vehicledata/VW-Group-Vehicles/test/)**
>
> VW, Audi, Škoda, SEAT, Cupra & Bentley — battery, range, charging and more on Homey.

---

<div class="post-metadata">

**Author:** ![Lifevolution](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lifevolution/32/168063_2.png) [@Lifevolution](https://community.homey.app/u/Lifevolution)\
**Post date:** [September 6, 2026, 10:32am UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345/113 "2026-09-06T10:32:20Z")

</div>

So far the fix seems to did the job, thanks! I haven’t seen the 93b55324 key since, but if it returns and has impact, I will let you know.

---

<div class="post-metadata">

**Author:** ![M\_Molenkamp](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/m_molenkamp/32/172345_2.png) [@M\_Molenkamp](https://community.homey.app/u/M_Molenkamp)\
**Post date:** [September 8, 2026, 8:28am UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345/114 "2026-09-08T08:28:23Z")

</div>

Hi, thank you so much for your work.

It look liked since the last update the app won’t refresh anymore. In de debug en JSON files are the timestamps right. But the info in the app is old.

After a re-instalation, I still have the same refresh problems in your app. Can you help me to fix this?

---

<div class="post-metadata">

**Author:** ![Andi](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andi/32/160466_2.png) [@Andi](https://community.homey.app/u/Andi)\
**Post date:** [September 8, 2026, 5:38pm UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345/115 "2026-09-08T17:38:33Z")

</div>

Thanks for reporting this — the detail that the JSON timestamps were right while the app showed old values is what pinned this down, and I could reproduce it.

It’s a bug in the app, not your setup. The app decided whether a dataset contained anything new by looking at the newest timestamp in it. Some vehicles include an entry stamped with a fixed date in the future (a validity or due date), and that permanently became “the newest” — so the app concluded nothing had changed on every single poll and stopped applying readings, while it kept downloading and storing fresh data. That’s exactly why the Debug tab looked correct.

Fixed in 0.0.64: readings are now always applied, and future-dated entries are no longer mistaken for measurements. No action needed on your side beyond updating — no re-pairing, no portal changes.

Please test newest version: [VW Group Vehicles | Homey](https://homey.app/a/com.vwgroup.vehicledata/test/)

---

<div class="post-metadata">

**Author:** ![MRK](https://avatars.discourse-cdn.com/v4/letter/m/7ba0ec/32.png) [@MRK](https://community.homey.app/u/MRK)\
**Post date:** [September 8, 2026, 7:13pm UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345/116 "2026-09-08T19:13:53Z")

</div>

Hi,

I installed everything according to the instructions in the app manual, but in Homey it says “no reaction.”

The files look like this: 20260908185749\_WVGZZZE2ZNE006150\_no\_content\_found

It seems that something is not working correctly.

---

<div class="post-metadata">

**Author:** ![Andi](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andi/32/160466_2.png) [@Andi](https://community.homey.app/u/Andi)\
**Post date:** [September 8, 2026, 8:13pm UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345/117 "2026-09-08T20:13:09Z")

</div>

Those …\_no\_content\_found files are the portal’s placeholder for “the vehicle sent nothing in this 15-minute window” — the fact that you get them on schedule means your continuous data request is active and delivering. What’s missing is data from the car itself.

Three things to check, in the order that most often helps:

Data sharing in the vehicle. In the car’s privacy/data settings, data transmission must be switched on. This is by far the most common cause — if it’s off, the portal will keep producing empty snapshots forever.  
Data clusters on the portal. Open your continuous data request and confirm that data clusters are actually selected. A request created without them delivers empty snapshots indefinitely.  
Wake the car once. Many VW Group vehicles only report around a drive or unlock cycle. Drive or unlock it once, then wait for the next 15-minute window.

---

<div class="post-metadata">

**Author:** ![MRK](https://avatars.discourse-cdn.com/v4/letter/m/7ba0ec/32.png) [@MRK](https://community.homey.app/u/MRK)\
**Post date:** [September 9, 2026, 7:48pm UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345/118 "2026-09-09T19:48:03Z")

</div>

Tried and checked all but without result. So it should be something on the VW portal?

Any idea if it’s possible to contact VW?

---

<div class="post-metadata">

**Author:** ![Henrik\_Duerud](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henrik_duerud/32/120716_2.png) [@Henrik\_Duerud](https://community.homey.app/u/Henrik_Duerud)\
**Post date:** [September 9, 2026, 10:27pm UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345/119 "2026-09-09T22:27:39Z")

</div>

Had the same issue with “no content” for a week or so.

There’s a Contact us button on the bottom of the Eu.data.act page where you can explain the issue. They replied on email after a few days, and the issue was solved.

---

<div class="post-metadata">

**Author:** ![Kraakenes](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kraakenes/32/58189_2.png) [@Kraakenes](https://community.homey.app/u/Kraakenes)\
**Post date:** [September 10, 2026, 6:53am UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345/120 "2026-09-10T06:53:02Z")

</div>

Hi, great work with the app!! @Andi

Would it be possible to add last updated timestamp to the car widget like it is in the Hyundai widget here?

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/3/33daaaefa205f2b74a96c394d17ec1c8a21d69b0.jpeg)

---

<div class="post-metadata">

**Author:** ![Andi](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andi/32/160466_2.png) [@Andi](https://community.homey.app/u/Andi)\
**Post date:** [September 10, 2026, 6:09pm UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345/121 "2026-09-10T18:09:57Z")

</div>

Hi Kraakenes

Please install the latest TEST version: [VW Group Vehicles | Homey](https://homey.app/a/com.vwgroup.vehicledata/test/)

---

<div class="post-metadata">

**Author:** ![Mark\_Moerenhout](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mark_moerenhout/32/107200_2.png) [@Mark\_Moerenhout](https://community.homey.app/u/Mark_Moerenhout)\
**Post date:** [September 10, 2026, 6:18pm UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345/122 "2026-09-10T18:18:41Z")

</div>

4bab9539-a026-4e1a-98ce-a02913fd994d

Gewn reactie meld homey

Heb alles opnieuw gedaan maar zonder resultaat

Krijg wel om het kwartier een rapport.

Dus benieuwd wat ik fout doe of waar het mis gaat

Hoor het graag

---

<div class="post-metadata">

**Author:** ![Andi](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andi/32/160466_2.png) [@Andi](https://community.homey.app/u/Andi)\
**Post date:** [September 10, 2026, 6:23pm UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345/123 "2026-09-10T18:23:07Z")

</div>

in English please

---

<div class="post-metadata">

**Author:** ![Mark\_Moerenhout](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mark_moerenhout/32/107200_2.png) [@Mark\_Moerenhout](https://community.homey.app/u/Mark_Moerenhout)\
**Post date:** [September 10, 2026, 7:56pm UTC](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345/124 "2026-09-10T19:56:23Z")

</div>

No response from Homey.

I’ve tried everything again, but with no result.

I do receive a report every 15 minutes, though.

So, I’m wondering what I’m doing wrong or where things are going wrong.

Looking forward to hearing from you.

4bab9539-a026-4e1a-98ce-a02913fd994d

[Previous page](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345.md?page=5)

[Next page](https://community.homey.app/t/app-pro-vw-group-vehicles-access-your-vehicle-data-via-the-eu-data-act-portal-for-vw-audi-skoda-seat-cupra-and-bentley/156345.md?page=7)
