Volkswagen We Connect - Unfortunately, it doesn't work in version 0.307.2 either

[Christian-Tausch]

Description

[main ] ERROR 2026/05/29 11:00:46 creating vehicle db:41 failed: cannot create vehicle type 'template': cannot create vehicle type 'vw': unexpected status: 400 (Bad Request) POST https://emea.bff.cariad.digital/auth/v1/idk/oidc/token

The latest Docker nightly build (nightly.20260529-8ea620d) was used.
And, of course, the password was verified multiple times.
In yesterday's nightly build (nightly.20260528-ec830ef), the error message also looked like this:

[main ] ERROR 2026/05/29 11:39:24 creating vehicle db:41 failed: cannot create vehicle type 'template': cannot create vehicle type 'vw': state parameter not found

Steps to Reproduce

Logs

[main  ] INFO 2026/05/29 11:43:26 evcc 0.307.2 (8ea620d36)
[main  ] INFO 2026/05/29 11:43:26 config file not found, database-only mode
[main  ] INFO 2026/05/29 11:43:26 using sqlite database: /root/.evcc/evcc.db?_pragma=foreign_keys(1)&_pragma=auto_vacuum(INCREMENTAL)
[main  ] INFO 2026/05/29 11:43:26 OCPP local url:    ws://127.0.0.1:8887/<stationId>
[main  ] INFO 2026/05/29 11:43:26 UI local url:      http://127.0.0.1:7070
[main  ] ERROR 2026/05/29 11:43:31 creating vehicle db:41 failed: cannot create vehicle type 'template': cannot create vehicle type 'vw': unexpected status: 400 (Bad Request) POST https://emea.bff.cariad.digital/auth/v1/idk/oidc/token

Version

v0.307.2 (8ea620d)

System

linux/arm64, CEST +02:00

[Funzinator]

I just tried the same version/commit, also doesn't work for me.

Happy to assist with testing.

[klrth]

Having the same problem with my ID4 I moved my Raspberry to evcc/unstable and updated to v0.307.2 (8ea620d).
I hope that is the current nightly build. (BTW where can I look that up?)

Issue still present.

[Ingo-Vetter]

Mein EVCC (HA App) bekommt auch keine Verbindung zu Volkswagen Connect.

EVCC Version: v0.307.2
HA Core Version: 2026.5.4
Supervisor: 2026.05.1
Operating System: 15.1

[Funzinator]

where can I look that up?

For example, in the UI:

If not, you have to build it yourself in the meantime.

[Christian-Tausch]

Having the same problem with my ID4 I moved my Raspberry to evcc/unstable and updated to v0.307.2 (8ea620d). I hope that is the current nightly build. (BTW where can I look that up?)

Issue still present.

I check Docker Hub for this.
Under "Tags," you can then see the various builds.

https://hub.docker.com/r/evcc/evcc

[klrth]

Just found out that nightly builds are done in Github Actions, so you can check here

https://github.com/evcc-io/evcc/actions/workflows/nightly.yml

Click on the commit hash to see what has changed.

[irqnet]

Same here with an VW Tiguan on latest version v0.307.2 (8ea620d) nightly.

[michelesilla02]

tillsteinbach/CarConnectivity#154

[klrth]

Not sure the transition announcement is relevant. That looks more like giving data access to other businesses for their own purposes, like charge point providers to get consumption data for planning.

In our case I as a car owner want access to my cars data and evcc is only the agent I use for that.

[Funzinator]

I just noticed that Tibber is still able to read charging state and SoC once I added the "Volkswagen PowerUp" and authenticated. My car (well, only 5 entities) is now available in HomeAssistant via the Tibber integration.
At least I can make it work to some extent again - but it keeps pretty annoying overall

[Christian-Tausch]

It looks like @andig made another change in vehicle/vag/idkproxy/endpoint.go. Link
It seems the old path was still present there.

[andig]

Unfortunately unrelated :(