Fiat 500e not connecting anymore - 403 forbidden - Missing Authentication Token

[schtzngrm]

Describe the bug

Cannot connect to Fiat 500e anymore since a few versions (cannot say which one exactly anymore).
Password / PIN have been changed and are correct. No connection when car is charging and when not connected.

Issue arises in docker AND in the normal DietPi environment

Error message in configuration tab:
cannot create vehicle type 'template': cannot create vehicle type 'fiat': cannot get vehicles: unexpected status: 403 (Forbidden) GET https://channels.sdpr-01.fcagcv.com/v4/accounts/***/vehicles?stage=ALL__

Error message when using the link above:
{
"name":"FORBIDDEN",
"message":"Missing Authentication Token"
}

Steps to reproduce

1. Delete Car configuration
2. Select new car - using template and entering all information required (Username, password, pin, VIN) - no advanced settings selected
3. Press validate
4. Error message: cannot create vehicle type 'template': cannot create vehicle type 'fiat': cannot get vehicles: unexpected status: 403 (Forbidden) GET https://channels.sdpr-01.fcagcv.com/v4/accounts/***/vehicles?stage=ALL
5. Restart
6. Check more - Vehicle settings - Fiat 500e connected to Charger
7. Charge - Fiat 500e (not connected )
   ...

Configuration details

evcc config:
[main  ] INFO 2026/07/22 14:56:30 config file not found, database-only mode
[main  ] INFO 2026/07/22 14:56:30 using sqlite database: /root/.evcc/evcc.db?_pragma=busy_timeout(5000)&_pragma=foreign_keys(1)&_pragma=auto_vacuum(INCREMENTAL)
charger
---
db:3 {Type:template Title: Icon: Product:go-e Charger HOME+} map[host:go-echarger-098497 template:go-e-v3]

meter
---
db:1 {Type:template Title:SolarEdge PV-Anlage Icon: Product:SolarEdge Hybrid Inverter} map[baudrate:9600 comset:8N1 host:SolarEdgeWR-WLAN id:1 maxacpower:8000 maxdischargepower:5000 modbus:tcpip port:1502 template:solaredge-hybrid usage:pv watchdog:60s]
db:2 {Type:template Title:SolarEdge Battery Icon: Product:SolarEdge Hybrid Inverter} map[baudrate:9600 capacity:8 comset:8N1 host:SolarEdgeWR-WLAN id:1 maxacpower:0 maxdischargepower:5000 modbus:tcpip port:1502 template:solaredge-hybrid usage:battery watchdog:60s]
db:6 {Type:template Title: Icon: Product:SolarEdge Hybrid Inverter} map[baudrate:9600 comset:8N1 host:SolarEdgeWR-WLAN id:1 maxacpower:0 maxdischargepower:5000 modbus:tcpip port:1502 template:solaredge-hybrid usage:grid watchdog:60s]

vehicle
---
db:14 {Type:template Title: Icon: Product:Fiat} map[autodetectdisabled:false cache:15m capacity:37 climaterdisabled:false coarsecurrent:false icon:car password:***** pin:***** priority:0 streaming:false template:fiat title:Fiat 500e user:***** vin:***** wakeupdisabled:false welcomecharge:false]

tariff
---
db:7 {Type:template Title:Solarvorhersage West Icon: Product:Forecast.Solar} map[az:260 dec:26 interval:1h kwp:8 lat:***** lon:***** template:forecast-solar]
db:8 {Type:template Title:Solarvorhersage Ost Icon: Product:Forecast.Solar} map[az:80 dec:26 interval:1h kwp:8 lat:***** lon:***** template:forecast-solar]
db:10 {Type:template Title: Icon: Product:Fester Preis} map[price:0.2706 template:fixed]
db:11 {Type:template Title: Icon: Product:Fester Preis} map[price:0.0725 template:fixed]

loadpoint
---
db:4 {Type: Title: Icon: Product:} map[batteryBoostLimit:75 charger:db:3 circuit: defaultMode:pv limitEnergy:0 limitSoc:0 maxCurrent:16 meter: mode:pv phasesConfigured:0 planStrategy:map[continuous:false precondition:0] soc:map[estimate:true poll:map[interval:3.6e+12 mode:charging]] thresholds:map[disable:map[delay:1.8e+11 threshold:0] enable:map[delay:6e+10 threshold:0]] title:Go-eCharger AGB ui:map[maxTemp:0 minTemp:0] vehicle:]

messenger
---
db:9 {Type:template Title: Icon: Product:Pushover} map[app:***** devices:[Pixel_8 Pixel_7a pixel10pro] recipients:***** template:pushover]



evcc dump --cfg:
[main  ] INFO 2026/07/22 14:55:24 config file not found, database-only mode
[main  ] INFO 2026/07/22 14:55:24 using sqlite database: /root/.evcc/evcc.db?_pragma=busy_timeout(5000)&_pragma=foreign_keys(1)&_pragma=auto_vacuum(INCREMENTAL)
[eebus ] INFO 2026/07/22 14:55:25 Local SKI: 6c4e4525c62942dac857cdd9eb18a34fbd62968d
[main  ] ERROR 2026/07/22 14:55:30 creating vehicle db:14 failed: cannot create vehicle type 'template': cannot create vehicle type 'fiat': cannot get vehicles: unexpected status: 403 (Forbidden) GET https://channels.sdpr-01.fcagcv.com/v4/accounts/66024dd909074455b775c0c1fa6532a9/vehicles?stage=ALL

Version: `0.312.1`

Log details

[main  ] INFO 2026/07/22 14:53:14 evcc 0.312.1
[main  ] INFO 2026/07/22 14:53:14 config file not found, database-only mode
[main  ] INFO 2026/07/22 14:53:14 using sqlite database: /root/.evcc/evcc.db?_pragma=busy_timeout(5000)&_pragma=foreign_keys(1)&_pragma=auto_vacuum(INCREMENTAL)
[eebus ] INFO 2026/07/22 14:53:14 Local SKI: ***
[main  ] INFO 2026/07/22 14:53:14 OCPP local url:    ws://127.0.0.1:8887/<stationId>
[main  ] INFO 2026/07/22 14:53:14 UI local url:      http://127.0.0.1:7070
[main  ] ERROR 2026/07/22 14:53:19 creating vehicle db:14 failed: cannot create vehicle type 'template': cannot create vehicle type 'fiat': cannot get vehicles: unexpected status: 403 (Forbidden) GET https://channels.sdpr-01.fcagcv.com/v4/accounts/66024dd909074455b775c0c1fa6532a9/vehicles?stage=ALL
[site  ] INFO 2026/07/22 14:53:20 site config:
[site  ] INFO 2026/07/22 14:53:20   meters:      grid ✓ pv ✓ battery ✓
[site  ] INFO 2026/07/22 14:53:20     grid:      power ✓ energy ✓ currents ✓
[site  ] INFO 2026/07/22 14:53:20     pv 1:      power ✓ energy ✗ currents ✗
[site  ] INFO 2026/07/22 14:53:20     battery 1: power ✓ energy ✓ currents ✗ soc ✓ capacity ✓
[site  ] INFO 2026/07/22 14:53:20   vehicles:
[site  ] INFO 2026/07/22 14:53:20     vehicle 1: range ✗ finish ✗ status ✗ climate ✗ wakeup ✗
[site  ] INFO 2026/07/22 14:53:20   tariffs:
[site  ] INFO 2026/07/22 14:53:20     grid:      pricestatic
[site  ] INFO 2026/07/22 14:53:20     feed-in:   pricestatic
[site  ] INFO 2026/07/22 14:53:20     co2:       ✗
[site  ] INFO 2026/07/22 14:53:20     solar:     ✓
[lp-1  ] INFO 2026/07/22 14:53:20 loadpoint 1:
[lp-1  ] INFO 2026/07/22 14:53:20   mode:        pv
[lp-1  ] INFO 2026/07/22 14:53:20   charger:     power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
[lp-1  ] INFO 2026/07/22 14:53:20   meters:      charge ✓
[lp-1  ] INFO 2026/07/22 14:53:20     charge:    power ✓ energy ✓ currents ✓
[lp-1  ] INFO 2026/07/22 14:53:22 vehicle updated: unknown -> Fiat 500e
[site  ] ERROR 2026/07/22 14:53:25 grid powers: model 203 block 0 point WphC: read tcp 172.17.0.3:48144->192.168.178.103:1502: i/o timeout
[lp-1  ] INFO 2026/07/22 14:53:26 car connected
[lp-1  ] INFO 2026/07/22 14:53:26 start charging ->

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

Docker container

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 version 0.312.1 (1656a76)

[github-actions]

Thanks for the detailed report. I looked at the Fiat integration (vehicle/fiat/identity.go, vehicle/fiat/api.go) and its history — there have been no code changes to the login/signing/Vehicles() logic since #27654 (merged well before 0.312.1), so this isn't caused by a recent evcc regression in that code.

The error is a 403 Forbidden with body "Missing Authentication Token" returned directly by FCA's AWS API Gateway (channels.sdpr-01.fcagcv.com) for the GET /v4/accounts/{uid}/vehicles?stage=ALL call. That specific message is what API Gateway returns when a request doesn't match any configured route/authorizer — i.e. it comes from FCA's backend, not from evcc's request validation. Since the account UID in your log (66024dd909074455b775c0c1fa6532a9) is populated, the username/password login step itself appears to succeed; the failure happens on the subsequent SigV4-signed request.

This could be caused either by an FCA-side change to this (undocumented/reverse-engineered) API, or by something going wrong in obtaining/using the Cognito credentials for your specific account, and I can't tell which from the info given.

To narrow this down, could you provide:

• Whether this fails for every attempt/restart, or only sometimes.
• Confirmation whether other Fiat 500e users are seeing the same error right now (a single report suggests it may be account-specific rather than a global API change).
• If possible, run evcc with --log debug (or -l debug) and share the relevant fiat log lines around the failing request — this would show whether the Cognito credential exchange itself is succeeding.

Without that, I can't confirm whether this is a genuine software defect vs. an upstream API/account issue, so I won't label it as a bug for now.

🤖 Generated with Claude Code

[schtzngrm]

Whether this fails for every attempt/restart, or only sometimes.
-> YES

Confirmation whether other Fiat 500e users are seeing the same error right now (a single report suggests it may be account-specific rather than a global API change).
-> I don't have access to another Fiat 500e
-> If a change was FCA-side, should affect multiple user.

Unfortunately, I cannot pull a --log at the moment.

[schtzngrm]

I tried "evcc --log debug", but there is no specific fiat log lines, just main, and eebus

[schtzngrm]

BTW: I could connect to Fiat (and get information on the car battery) for few seconds while testing, but now the connection is lost again with the same error message.

[thomash73]

Just as information: I am using 0.311.1 and I have no issues charging our Fiat 500e including using the connection to the Fiat API.

[schtzngrm]

Hi thomash73,
thank you for the information!
I downgraded (outside docker, DietPi environment), ...
... and it works (at the moment)! EVCC gets the information from the Fiat API!

[schtzngrm]

...and again - stopped working on both versions 0.311.1 and the newest beta. Same issue and error message as before. Fiat App works without problems.

[andig]

Ah

[schtzngrm]

Would it be possible to reopen the issue, as it is not solved yet?

[andig]

There's nothing to do. We're missing a full logfile (trace for Fiat) and a reference to another open source solution that actually works. Since Fiat does not provide an api (please complain at Fiat!) this is required.