VW/Cupra: EU Data Act vehicle SoC remains stale while charging, EVCC ignores more accurate estimated SoC

[blackperform]

Description

Using a Cupra Born with the DSG / EU Data Act integration, EVCC receives new data packages every 15 minutes, but the SoC value contained in the packages can be significantly outdated.

Example:

Cupra App: 60% SoC
DSG data package: 30% SoC
EVCC vehicle SoC: 30%
EVCC estimated SoC: 38%

EVCC correctly parses the DSG data and displays the value delivered by Volkswagen/Cupra. However, the DSG package contains outdated values although newer data packages are being generated regularly.

Example values from the downloaded DSG ZIP:
"battery_state_report.soc": "30"
"battery_level_HV.value": "30.0"

At the same time, the package also contains obviously outdated charging information such as charging timer timestamps from previous days.

Because EVCC always prefers the vehicle-reported SoC, the displayed SoC can be far behind the actual battery level while charging.

Steps to Reproduce

1. Configure a Volkswagen/Cupra vehicle using the DSG / EU Data Act integration.

2. Enable continuous 15-minute data delivery in the DSG portal.

3. Start charging the vehicle.

4. Wait until the vehicle SoC increases significantly.

5. Compare:
   -Cupra App SoC
   -DSG ZIP package value (battery_state_report.soc)
   -EVCC displayed vehicle SoC

6. Observe that the DSG package still reports an older SoC value and EVCC continues to display that stale value although charging is ongoing and the estimated SoC is already higher.

Configuration (YAML)

no yaml configuration

Configuration (UI)

{
  "charger": [
    {"id":19,"name":"db:19","type":"template","config":{"template":"go-e-v3","host":"192.168.1.57"},"deviceProduct":"go-e Charger CORE"}
  ],
  "experimental": true,
  "influx": {"database":"","insecure":false,"org":"","password":"","token":"","url":"","user":""},
  "interval": 30,
  "loadpoints": [
    {"id":20,"name":"db:20","batteryBoostLimit":60,"charger":"db:19","defaultMode":"pv","limitEnergy":0,"limitSoc":0,"maxCurrent":32,"minCurrent":7,"minSoc":0,"phasesConfigured":0,"planEnergy":0,"planPrecondition":0,"planStrategy":{"continuous":false,"precondition":0},"planTime":"0001-01-01T00:00:00Z","priority":0,"smartCostLimit":null,"smartFeedInPriorityLimit":null,"soc":{"estimate":true,"poll":{"interval":3600000000000,"mode":"charging"}},"thresholds":{"disable":{"delay":180000000000,"threshold":0},"enable":{"delay":60000000000,"threshold":0}},"title":"Wallbox ","ui":{"maxTemp":100,"minTemp":0},"vehicle":"db:15"}
  ],
  "meter": [
    {"id":8,"name":"db:8","type":"template","config":{"id":85,"template":"alpha-ess-smile","baudrate":9600,"comset":"8N1","host":"192.168.1.185","maxacpower":"0","modbus":"tcpip","port":502,"usage":"grid"},"deviceProduct":"Alpha ESS Storion SMILE"},
    {"id":6,"name":"db:6","type":"template","config":{"id":85,"template":"alpha-ess-smile","baudrate":9600,"comset":"8N1","host":"192.168.1.185","maxacpower":"0","modbus":"tcpip","port":502,"usage":"pv"},"deviceProduct":"Alpha ESS Storion SMILE","deviceTitle":"Alpha-ESS"},
    {"id":7,"name":"db:7","type":"template","config":{"id":85,"template":"alpha-ess-smile","baudrate":9600,"capacity":8.19,"comset":"8N1","host":"192.168.1.185","maxacpower":"0","maxsoc":100,"minsoc":10,"modbus":"tcpip","port":502,"usage":"battery"},"deviceProduct":"Alpha ESS Storion SMILE","deviceTitle":"Alpha Batterie"}
  ],
  "mqtt": {"broker":"","caCert":"","clientCert":"","clientID":"","clientKey":"","insecure":false,"password":"","topic":"evcc","user":""},
  "residualPower": 100,
  "shm": {"deviceId":"","deviceSerial":"","vendorId":""},
  "site": {"aux":null,"battery":["db:7"],"consumer":null,"ext":null,"grid":"db:8","pv":["db:6"],"title":"Zuhause"},
  "tariff": [
    {"id":2,"name":"db:2","type":"template","config":{"template":"fixed","price":0.32539999999999997},"deviceProduct":"Fester Preis"},
    {"id":1,"name":"db:1","type":"template","config":{"template":"fixed","price":0.07780000000000001},"deviceProduct":"Fester Preis"},
    {"id":4,"name":"db:4","type":"template","config":{"template":"open-meteo","ac":"1000","alphatemp":"-0.004","az":-50,"de":"0","dec":45,"dm":"0","efficiency":"100","interval":"1h","kwp":10,"lat":"***","lon":"***","rossmodel":"0.0342"},"deviceProduct":"Open-Meteo","deviceTitle":"Pv"},
    {"id":12,"name":"db:12","type":"template","config":{"template":"energypriceforecast-co2","horizon":"120","region":"DE"},"deviceProduct":"Energy Price Forecast EU CO₂"}
  ],
  "tariffRefs": {"co2":"db:12","feedIn":"db:1","grid":"db:2","planner":"","solar":["db:4"],"temperature":""},
  "vehicle": [
    {"id":15,"name":"db:15","type":"template","config":{"template":"cupra","autodetectdisabled":false,"cache":10000000000,"capacity":58,"climaterdisabled":false,"coarsecurrent":false,"icon":"car","maxCurrent":32,"maxPower":11000,"minCurrent":6,"mode":"pv","password":"***","phases":"3","priority":0,"streaming":false,"title":"BORN","user":"***","vin":"***","wakeupdisabled":false,"welcomecharge":false},"deviceProduct":"Cupra EU Data Act"}
  ]
}

Logs

[lp-1  ] DEBUG 2026/08/24 13:33:43 set charge current limit: 12A
[site  ] DEBUG 2026/08/24 13:33:43 solar forecast: produced 17.800kWh, forecasted 26.107kWh, scale 0.682
[site  ] DEBUG 2026/08/24 13:34:12 ----
[lp-1  ] DEBUG 2026/08/24 13:34:12 charge power: 2516W
[lp-1  ] DEBUG 2026/08/24 13:34:12 charge currents: [11.3 0 0]A
[site  ] DEBUG 2026/08/24 13:34:13 grid power: 220W
[site  ] DEBUG 2026/08/24 13:34:13 battery 1 power: 559W
[site  ] DEBUG 2026/08/24 13:34:13 grid currents: [2.7 6.7 6.4]A
[site  ] DEBUG 2026/08/24 13:34:13 battery 1 soc: 100%
[site  ] DEBUG 2026/08/24 13:34:13 pv 1 power: 3136W
[site  ] DEBUG 2026/08/24 13:34:13 site power: 879W
[lp-1  ] DEBUG 2026/08/24 13:34:13 charge voltages: [222 222 224]V
[lp-1  ] DEBUG 2026/08/24 13:34:13 detected active phases: 1p
[lp-1  ] DEBUG 2026/08/24 13:34:13 session energy: 6.051kWh
[lp-1  ] DEBUG 2026/08/24 13:34:13 charge total import: 462.488kWh
[lp-1  ] DEBUG 2026/08/24 13:34:13 charger status: C
[lp-1  ] DEBUG 2026/08/24 13:34:13 vehicle soc: 30%
[lp-1  ] DEBUG 2026/08/24 13:34:13 vehicle soc limit: 0%
[lp-1  ] DEBUG 2026/08/24 13:34:13 vehicle range: 125km
[lp-1  ] DEBUG 2026/08/24 13:34:13 soc estimated: 38.87% (vehicle: 30.00%)
[lp-1  ] DEBUG 2026/08/24 13:34:13 vehicle soc (estimator): 39%
[lp-1  ] DEBUG 2026/08/24 13:34:13 !! plan: plan time zero
[lp-1  ] DEBUG 2026/08/24 13:34:13 pv charge current: 8.18A = 12A + -3.82A (879W @ 1p)
[lp-1  ] DEBUG 2026/08/24 13:34:13 set charge current limit: 8A
[site  ] DEBUG 2026/08/24 13:34:13 solar forecast: produced 17.800kWh, forecasted 26.107kWh, scale 0.682

Version

v0.313.2

System

linux/amd64, CEST +02:00

[github-actions]

Thanks for the detailed report and the debug log.

Looking at the code (vehicle/vw/eudataact/store.go, vehicle/vw/eudataact/provider.go), evcc already does two things to mitigate exactly this kind of staleness:

1. store.merge() always keeps the value from the most recently delivered dataset for each field (per-field Seq, see Vehicle (EU Data Act): prefer most recently delivered value per field #30916/Vehicle (EU Data Act): merge datasets in delivery order #30805) — it deliberately ignores each field's own in-dataset timestamp because that was found to be unreliable. So evcc is already surfacing the newest battery_state_report.soc/battery_level_HV.value it has received from the portal.
2. The core/soc estimator then interpolates from charged energy once the reported SoC stops changing between polls — which your own log shows working: soc estimated: 38.87% (vehicle: 30.00%) → vehicle soc (estimator): 39%. That 39% (not the raw 30%) is what gets published as the loadpoint's vehicle SoC.

So the gap you're seeing (30% → 38% estimated vs. 60% in the Cupra app) doesn't look like a parsing/selection bug on evcc's side — it looks like the DSG/EU Data Act portal itself is delivering new dataset packages every 15 minutes without actually refreshing the battery_state_report/battery_level_HV payload (you noticed the same for charging-timer timestamps), i.e. the batch export lags the vehicle's live telemetry that the manufacturer app uses. Evcc can only use what's in the delivered datasets and interpolate the rest via charged energy, which it is already doing.

If you have datasets where a newer delivery actually contains a fresher SoC value that evcc failed to pick up (rather than the portal simply re-sending the same stale value), that would point to an actual selection bug — could you share such an example (with dataset delivery timestamps)? Otherwise this looks like an upstream data-freshness limitation of the DSG/EU Data Act export rather than something fixable in evcc.

🤖 Generated with Claude Code

[blackperform]

Thanks for the clarification.

In my case I do not have an example where EVCC ignores a newer SoC value from DSG.
What I see is:

11:00 UTC dataset:
battery_state_report.soc = 30

11:30 UTC:
no_content_found

11:45 UTC:
no_content_found

11:59 UTC dataset:
battery_state_report.soc = 30

12:16 UTC:
no_content_found

12:30 UTC:
no_content_found

During that time the vehicle was actively charging and the Cupra app showed about 65% SoC, while the DSG datasets continued to report 30%.

So based on the datasets themselves, it looks like the portal is repeatedly delivering stale SoC data (or no data at all), rather than EVCC selecting the wrong value from newer deliveries.

[andig]

Unfortunately your report is missing a detailed log file. Without log, we don‘t have the information for diagnosing the issue described. See https://docs.evcc.io/docs/faq#wie-kann-ich-ein-logfile-zur-fehleranalyse-erstellen.

[andig]

@blackperform see #33122. I think this is the same case, fixed in tomorrow's nightly. If not please reopen with trace log.

[blackperform]

@andig should be the same case. Thanks