Cupra Born stopped working #779
Replies: 9 comments
|
Hi romal, thanks for the detailed writeup and the config export. I want to be upfront: v2.18.0 doesn't specifically fix those 403s on the Born, so I can't promise this makes them disappear. What it does change is that the portal data-request failure now logs the real status and reason behind the error instead of the generic message we had before, so we can finally see what those 403s actually are. Could you update via HACS and then paste the new log line here? With that detail I should be able to figure out what's really going on. |
|
Hi Prash, config_entry-vag_connect-01KXFEA79TS1MQA5WCGHSFB4BJ.json cu romal |
|
Hi @rmalbrecht — since v2.18.0 the portal 403 is logged with its real status and reason. To tell whether this is a portal-auth rejection or the data request being refused, could you grab the debug log line behind the 403? Enable debug logging for custom_components.vag_connect, reproduce, and paste the line at the 403. That'll point straight at the fix. |
|
v2.19.1 bumps the CUPRA/SEAT app-version header to the current version — a stale header is the usual reason the backend suddenly starts refusing a channel that used to work, so this is the most likely fix. Please update and check whether the Born comes back. If it's still failing, paste the error from the log (mask your VIN to the last 6 chars) and I'll dig in. |
|
Still fails: 2026-07-19 10:35:53.861 DEBUG (MainThread) [custom_components.vag_connect.coordinator] VAG Connect: shutdown complete |
|
Tried the 2.20 but no change: 2026-07-20 20:43:11.473 WARNING (MainThread) [custom_components.vag_connect.cariad.api.seat_cupra] OLA 403 on .seat.cloud.vwgroup.com/v1/vehicles/VSSS123456/ranges — retrying with fallback header-set #1/1 (defense-in-depth Layer 3) Is there something I can help with in troubleshooting this? |
|
Thanks for sticking with it through 2.19.1 and 2.20 — and that last log actually gives us the answer. The 403 body decodes to "Forbidden device detected", which is VW's server-side device-attestation wall on the SEAT/CUPRA backend (the same lockdown that hit native CUPRA access around mid-2026). Notice it's rejecting the device, not your login — that's exactly why signing in manually works fine but every OLA endpoint still 403s. The honest part: this isn't something a header bump or an integration update can fix, which is why 2.19.1 and 2.20 didn't move the needle. There's no client-side way around that attestation check. The read path that still works for CUPRA is the EU Data Act portal, and your log shows it isn't set up yet ("Data Act kickoff: skipped … no supplementary portal"). If you request your vehicle data through SEAT/CUPRA's EU Data Act portal and then reconfigure the integration, it can serve what the portal exposes instead of hammering the blocked OLA backend. Happy to walk you through that if you want to go that route — just say the word. |
|
Strange. Didn't work. 2026-07-21 21:49:44.714 WARNING (MainThread) [custom_components.vag_connect.cariad.api.seat_cupra] OLA 403 on .seat.cloud.vwgroup.com/v1/vehicles/123456/ranges — retrying with fallback header-set #1/1 (defense-in-depth Layer 3) What I really need is the battery SOC and that is working :-) Parking location would be fine, but it's not provided by VW, nothing can be fine. Thanks for developing this integration! |
|
Good to hear it is working, and thanks for posting exactly what fixed it, that is a useful confirmation. The key bit is that a full removal and re-add forces a fresh login, whereas a reconfigure keeps the stored token, which is why the earlier attempts did not shift anything. Two notes on what you will keep seeing: The OLA 403 warnings will still appear on every poll. Those are the SEAT/CUPRA native backend rejecting the request at the device level, which is not something the integration can work around, and it is why the remote commands were hidden in 2.20.0 rather than left there to always fail (#464). Your actual data is coming from the EU Data Act portal instead, which is why the battery level is fine. That log noise is expected rather than a fault on your setup, and quietening it down is on the list. On the parking location, you are right that it is not there. The portal export contains no coordinate field at all, so on that channel there is simply no position to publish. That is a limit of what gets shared, not something being dropped on our side. Glad the part you needed is working. |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
my Cupra Born stopped working some days ago. It worked for some time just fine (#564) but then it stopped.
It shows me various 403 errors. But why? Manually logging in seems fine, username and pw is correct, the VIN and model is identified when I reconfigure the integration, ... but these 403 keeps popping up.
config_entry-vag_connect-01KXFEA79TS1MQA5WCGHSFB4BJ.json
Any ideas ?
cu romal
All reactions