Closed hlinden closed 8 months ago
We cant help Stellantis ;)
I know, but is it possible that something about their API changed a while ago and EVCC kept using the old whateveritwas until it finally broke now?
Are there any more insights why Stellantis doesn't work and how it is different to the Opel template?
@hlinden @flarno11 is it working for you? For me it is not working in EVCC, but Flobz Server in Home Assistant and also Opel app is working again.
I have the same problem with an Opel Mokka-e.
The "my.opel" was on server maintenance since Friday 12.01.24 till today 16.01.24. I checked the my.opel webpage with the browser, and as is said there was an info of an working process. Today i recognized that the app is different, and at afternoon the "my.opel"-Website is now reachable. But after login, which succeeded, there was a message that the server has moved and i should update my bookmark in the browser. I tried evcc if it connects to the server, but the server error persists. I think, they changed something bigger. Probably the evcc code needs to be changed. I hope the Target-Charging works again in the near future.
@hlinden @flarno11 is it working for you? For me it is not working in EVCC, but Flobz Server in Home Assistant and also Opel app is working again.
Same. Opel app works again, EVCC still gives up with...
[main ] ERROR 2024/01/17 09:50:48 creating vehicle ev1 failed: cannot create vehicle type 'template': cannot create vehicle type 'opel': login failed: oauth2: "server_error" "Internal Server Error"
Same here - Opel Mokka is not recognized, but accessible via the App.
Describe the bug
Currently, my Opel Corsa-e is marked as offline. It seems that something around the OAuth process fails on Stellantis' side.
Steps to reproduce
Configuration details
Log details
What type of operating system are you running?
HomeAssistant Add-on
Version
0.123.8