VW EU Data Act setup, but SoC not update #30644
Describe the bugI have set up the the VW EU data act (every 15 minutes). However, it seems that the SoC is only updated very rarely, maybe once a day. Today, the whole day there was about difference of 7 to 9 % in the SoC between EVCC and VW-App. The delta was most probably because my Buzz was charged in the morning for about 45 min as Gastfahrzeug. Most probably I did configure the VW-EU-Data-Act not 100% correct. However I don't know what I did wrong. Steps to reproduce
Configuration details# open evcc at http://evcc.local:7070
network:
schema: http
host: evcc.local # .local suffix announces the hostname on MDNS
port: 7070
log: debug
levels:
cache: error
# unique installation id
plant:
interval: 30s # control cycle interval
sponsortoken:
# sponsors can set telemetry: true to enable anonymous data aggregation
# see https://github.com/evcc-io/evcc/discussions/4554
telemetry: false
meters:
- type: template
template: kostal-plenticore
id: 71
host: 192.168.178.78
port: 1502
usage: pv
modbus: tcpip
name: pv1
- type: template
template: kostal-plenticore
id: 71
host: 192.168.178.78
port: 1502
usage: battery
modbus: tcpip
name: battery2
- type: template
template: kostal-ksem-inverter
id: 71
host: 192.168.178.78
port: 1502
usage: grid
modbus: tcpip
name: grid3
chargers:
- type: template
template: vestel
id: 255
host: 192.168.178.103
port: 502
modbus: tcpip
name: wallbox5
vehicles:
- type: template
template: vw
user:
password:
vin: WV2Z
title: Buzz
capacity: 86
timeout: 10s
name: ev4
loadpoints:
- title: Garage
charger: wallbox5
mode: pv
phases: 0 # Ermöglicht automatische Umschaltung 1P/3P
# --- STABILISIERUNG DER UMSCHALTUNG ---
enable:
delay: 1m # Startet Ladung erst, wenn 1 Min. lang genug Überschuss da ist
threshold: 0 # Startet bei 0 Watt Überschuss
disable:
delay: 5m # Stoppt Ladung erst, wenn 3 Min. lang zu wenig Überschuss da ist
threshold: -200 # Erlaubt 200W Netzbezug während der 3 Min. Wartezeit
site:
title: S4
meters:
grid: grid3
pv:
- pv1
battery:
- battery2
tariffs:
currency: CHF # (default EUR)
grid:
# static grid price
type: fixed
price: 0.2597 # [currency]/kW
zones:
- days: Mo-Fr
hours: 07-19
price: 0.3440 # CHF/kWh
feedin:
# rate for feeding excess (pv) energy to the grid
type: fixed
price: 0.138 # [currency]/kWh 0.115 + 0.023
# co2:
# type: template
# template: electricitymaps-free
# token:
# zone: CH # siehe https://api.electricitymap.org/v3/zones
solar:
- type: template
template: forecast-solar
lat:
lon:
dec: 24.8 # 0 = horizontal, 90 = vertikal
kwp: 11.1
az: 38 # -180 = Norden, -90 = Osten, 0 = Süden, 90 = Westen, 180 = NordenLog detailsWhat type of operating system or environment does evcc run on?Linux External automation
Nightly build
VersionNo response |
Replies: 8 comments 17 replies
|
You'll need to see if VW even delivers data in the portal and if it's what you expect. If not- complain at VW support! |
|
Thank you @andig Just another thought. My ID.Buzz is from Volkswagen Nutzfahrzeuge and not from Volkswagen Personkraftwagen. Maybe this makes a difference in URL. At I saw such a parameter during the redirection to the "VW-identity" website. 
|
|
When the portal is working they appear on the page you screenshoted. But the Portal is overloaded. Nothing a user can fix, only VW can fix it. |
|
@ambitzgi - can you please shortly tell me, how you set this stuff up?
|
|
@ambitzgi - push ;) Can you please give me a feedback. Still dont get it ;) THX |
|
My understanding is, that currently there is no public API. The zip files are a workaround, which is also implemented in EVCC. Currently my SoC is updated in evcc only randomly, maybe every second day. |
|
II have the same problem and a similar configuration. the portal only updates once a day, and automatic vehicle detection upon plugging in the charging cable isn't working either. Consequently, the current state of charge (SOC) isn't displayed, even when the cable is connected and charging has started. Currently, it only shows the "Guest Vehicle" with a completely outdated SOC. |
|
Import via VW app was the original way it was imported. That access was blocked by VW. With the data as provided by VW (often several hours old) via the EU data act portal no control is possible. |
|
For what it's worth, I switched my vehicle to the generic "off-line" template. The data reported by the eu data act website is so far off (ie. currently the soc data in the json file doesn't seem to have been updated for > 24hs) that it becomes unusable. In casu, my car stopped charging due to evcc thinking it reached the 80% target, whereas in reality I'm at 35%... |
|
VW is still overwhelmed by load on the portal and working on fixes... |
|
In my case the json, delivered by VW has 3 battery_state_report.soc without timestamps. (45, 45, 74). 74 is correct. evvc shows 45. May I suggest to correlate with or use "battery_level_HV.value" which is correct. |
|
@matzeruegge are you using current version? If yes, open issue. If not, please always do so before posting "doesn't work". |
|
I am using 0.309.2. I will open an issue. Thanks @andig for your excellent work. |
|
Thanks- that release should work unless we have conflicting keys that are each updated. Lets find out. |
|
bei mir schaut´s so aus, das der battery_state_report.soc 2x vorkommt mit unterschiedlichen Werte. Der erste Wert wäre annähernd der passende und es ist auch nur ein PKW bei VW eingetragen. Is zu heulen, was die in Wolfsburg treiben. |
|
Anhand des keys können die Werte interpretiert werden.
Siehe auch https://github.com/evcc-io/evcc/pull/31092#issuecomment-4762461286 |
|
Ich habe seit Tagen in evcc 84% Ladestand. Da ändert sich nix. Könnte am Zeitstempel der Daten liegen. |
|
At first the file names ended in no_content_found and they were only some bytes big. 20260823121307_WVWZZZAAZND....json{
"vin": "WVWZZZAAZND",
"user_id": "74ad4795-",
"Data": [
{
"key": "ac86e00b-7fa1-3a59-b481-aa7cfc49b0d9",
"dataFieldName": "maintenance_interval_distance_until_inspection",
"value": "-11300",
"timestampUtc": "2026-08-23T01:23:00.000Z"
},
{
"key": "d9f36adc-1840-37da-8ca1-7c2d789bcf9e",
"dataFieldName": "maintenance_interval_distance_until_oil_change",
"value": "-1700",
"timestampUtc": "2026-08-23T01:23:00.000Z"
},
{
"key": "c17ead4f-09b8-357f-ac2b-38c448ab88c4",
"dataFieldName": "parking_lights",
"value": "2",
"timestampUtc": "2026-08-23T01:23:00.000Z"
},
{
"key": "053496dc-0a8e-3e0c-93fd-055e622d3f99",
"dataFieldName": "bem_level",
"value": "0",
"timestampUtc": "2026-08-23T01:23:00.000Z"
},
{
"key": "97aa3271-7b36-322f-b913-d4bf5ab31633",
"dataFieldName": "maintenance_interval_inspection_warning",
"value": "1",
"timestampUtc": "2026-08-23T01:23:00.000Z"
},
{
"key": "42b1c47b-e1d1-375f-a76f-32ab0177f03e",
"dataFieldName": "maintenance_interval__time_until_oil_change",
"value": "-17",
"timestampUtc": "2026-08-23T01:23:00.000Z"
},
{
"key": "f8bbe94d-06e1-3311-bf8f-c0c99cc67d48",
"dataFieldName": "parking_brake",
"value": "0",
"timestampUtc": "2026-08-23T01:23:00.000Z"
},
{
"key": "41c0805c-43e5-313e-9dfb-356cb8d20f7c",
"dataFieldName": "mileage",
"value": "53136",
"timestampUtc": "2026-08-23T01:23:00.000Z"
},
{
"key": "173589ce-e437-3c6e-a0ec-6df704586fd7",
"dataFieldName": "trueness",
"timestampUtc": "2026-08-23T01:23:00.000Z"
},
{
"key": "d607f5ff-cacb-3460-a8eb-8ca16d4acc08",
"dataFieldName": "maintenance_interval_monthly_mileage",
"value": "257",
"timestampUtc": "2026-08-23T01:23:00.000Z"
},
{
"key": "0b7f22d9-1703-35f5-94cc-0c58a42fcbb4",
"dataFieldName": "maintenance_interval_oil_change_warning",
"value": "1",
"timestampUtc": "2026-08-23T01:23:00.000Z"
},
{
"key": "fd600221-7965-3396-96d7-82a840a2831c",
"dataFieldName": "maintenance_interval__time_until_inspection",
"value": "-432",
"timestampUtc": "2026-08-23T01:23:00.000Z"
}
]
} |
|
Optimist! Since the start I have had a lot of different formatted packages with varying age of outdated data. Quite often also without the really important data at all. If the authorities in the EU countries become active (which may take quite some time) they may be able to force VW-group to get their act together but even there I have little hope. In other words: I don't expect VW to provide stable and useful data prior to our car being ripe for the car crusher. |
|
Contact VW support and complain with the BNetA- it‘s your data and you have a legal right to it. |
|
If he is living in another EU country (not Germany) he can´t file with BNetzA. Then he has to do it with the authority in his country responsible for the EU data act. |
|
Same problem here with a Cupra Born. I'm pulling the SoC from Tibber now. Different VW brand, same backend, so this should work for other cars as well. Steps to do:
vehicles:
- name: ev4
type: template
template: tibber
title: ID.Buzz
capacity: 79
clientid: <client id>
clientsecret: <client secret>
redirecturi: http://localhost:7070/providerauth/callback
vin: WVW...
cache: 5m
Two things worth knowing:
Tibber doesn't talk to VW itself. It uses Enode, a B2B provider that builds and maintains the OEM integrations and polls the cars from its own infrastructure, faster while a car is charging. So the chain is |
That's actually a bug. Didn't have an account with >1 vehicle when testing. If you could share access with info@evcc.io I'd be happy to provide a fix. |
|
I can confirm the solution via Tibber is working. Great work Christian. Thx. |
I deleted the dummy car from the tibber account, sorry. But I think you can reproduce by creating a new tibber account, and just adding a car, it will be a dummy car. |
When the portal is working they appear on the page you screenshoted. But the Portal is overloaded. Nothing a user can fix, only VW can fix it.