EU Data Act: Škoda Enyaq delivers SoC as `currentSoc` — key not mapped, Soc() returns not available

[rufinus]

Describe the bug

Skoda Enyaq (2025) configured via the generic drivesomethinggreater template with brand: Skoda. Portal login, vehicle discovery and dataset download all work. The delivered dataset contains the SoC, but under Skoda's own data point key/name (0a18a053-b4b0-3db1-be44-a6c5dba629b1 / currentSoc), which Provider.Soc() does not look up — it only checks battery_level_HV.value, state_of_charge, hv_soc and the VW ID.3-specific key 506cb83e-f99f-3af3-bbeb-0429b69a78d9.

Result: the provider logs the received currentSoc point at DEBUG level and immediately afterwards Soc() fails with not available. Vehicle SoC stays at 0 in the UI, which breaks min+pv planning (worst-case assumption, immediate full-power charge).

Suggested fix: add the Enyaq key 0a18a053-b4b0-3db1-be44-a6c5dba629b1 (name currentSoc) to the Soc() lookup in vehicle/vw/eudataact/provider.go. The Enyaq presumably also delivers range/odometer under own keys — happy to provide full dataset logs for mapping those too.

Steps to reproduce

1. Enable a continuous data request (15 min, Charging cluster) for a Skoda Enyaq on https://eu-data-act.drivesomethinggreater.com
2. Configure the vehicle with template: drivesomethinggreater, brand: Skoda (evcc 0.312.1)
3. Wait for a dataset with content (generated after driving the car)
4. Observe [dsg] DEBUG recv ... currentSoc: 60 in the log, followed by [dsg] ERROR not available; vehicle SoC remains 0

Configuration details

vehicles:
  - name: enyaq
    type: template
    template: drivesomethinggreater
    brand: Skoda
    user: *****
    password: *****
    vin: TMBGH9*********
    title: Skoda Enyaq
    capacity: 82
    cache: 15m

Log details

[dsg   ] DEBUG 2026/07/22 19:28:30 recv 5150d35f-9f5d-3f61-b8d5-8bdca8178448 tripId: 3f84df5b-59b7-45e0-878b-29e6acc113f5 (2026-07-22 17:04:22)
[dsg   ] DEBUG 2026/07/22 19:28:30 recv 8a5df67d-839f-3117-be3b-6f09d345ebfa shortTermAverageConsumption: 16.6 kWh/100km (2026-07-22 17:55:33)
[dsg   ] DEBUG 2026/07/22 19:28:30 recv 85807008-0add-3e9c-86a7-949a07334e8c ignition: keyContact (2026-07-22 17:55:33)
[dsg   ] DEBUG 2026/07/22 19:28:30 recv bfd914a7-e030-3dc1-99f4-93d3b945da07 speed: 0 (2026-07-22 17:55:32)
[dsg   ] DEBUG 2026/07/22 19:28:30 recv 0a18a053-b4b0-3db1-be44-a6c5dba629b1 currentSoc: 60 (2026-07-22 17:55:22)
[dsg   ] DEBUG 2026/07/22 19:28:30 recv 56bc8dc1-e326-3da8-b0d0-8c5519001c17 heading: 33 (2026-07-22 17:55:32)
[dsg   ] DEBUG 2026/07/22 19:28:30 recv 62a0652d-2dae-32af-9404-4879cf6f669a persLocation: [redacted] (2026-07-22 17:55:22)
[dsg   ] ERROR 2026/07/22 19:28:30 not available

(location coordinates redacted; full unredacted dataset logs available on request)

What type of operating system or environment does evcc run on?

Linux

External automation

• I have made sure that no external automation like HomeAssistant or Node-RED is active or accessing any of the mentioned devices when this issue occurs.

Nightly build

• I have verified that the issue is reproducible with the latest nightly build

Version

evcc 0.312.1 (Docker, evcc/evcc:latest)

[github-actions]

Confirmed. The Škoda Enyaq (and possibly other non-ID.3 models) delivers SoC under its own data point key 0a18a053-b4b0-3db1-be44-a6c5dba629b1 (field name currentSoc), which isn't in the Soc() lookup in vehicle/vw/eudataact/provider.go. That lookup only checks battery_level_HV.value, state_of_charge, hv_soc and the VW ID.3-specific key 506cb83e-f99f-3af3-bbeb-0429b69a78d9, so the Enyaq's SoC point is stored but never matched, and Soc() returns not available.

This matches the existing pattern for model-specific keys (KeyBatteryStateReportSoc for the ID.3), so I added KeyEnyaqSoc for this Enyaq key and included it in the Soc() lookup. Opening a fix PR.

Range/odometer for the Enyaq would need the same treatment once their keys are known — happy to take the full dataset logs if you want to follow up with a separate issue/PR for those.

🤖 Generated with Claude Code

[rufinus]

Can confirm nightly displayed SoC again. Trying to get the other Fields working for an updated PR.