Change to the PSA API - Internal Error 400 #733
Comments
|
same here |
|
+1 |
|
Same problem here |
|
Hi, There might be a change in the authentification URLs? I tested under Home Assistant using 3.3.1 and 3.3.2 (fresh images, completly removed from DOCKER and deleted any trace of the app in HA). Here is the log, not sure how I can give more : One thing that I found strange was that my car was apparently configured to be in Switzerland instead of France.. I changed it yesterday on the website but didn't change anything. |
|
Just a little more information, the Android app continued to work during this maintenance stuff and there wasn't any client update (last one is 19 dec 2023). |
|
The API (see https://developer.groupe-psa.io/webapi/b2c/api-reference/specification) has changed in november: https://developer.groupe-psa.io/webapi/b2c/api-reference/changelog/#article so this would fit to updating the app...
|
It looks like, that you need a certificate to authenticate to the new base_url. maybe @flobz know a bit more about it |
|
I just use the |
|
@chr-engwer and in |
|
@chr-engwer |
|
I'm not sure how to find the URL in the apk, it is not extracted in the What I can say is, that the URL of the website has changed since the relaunch, it is now The docs also state is, that the |
Without decrypting https, I got idpcvs.opel.com as well as microservices.mym.awsmpsa.com and firebaselogging-pa.googleapis.com. I'll try to use wireguard to see if I can get more info on the sub stuff. However I'm pretty sure the link said by @chr-engwer is the same when logging through the Android app. ///Edit |
|
fwiw, we're seeing the same issue with sign in to Opel on openWB. Peugeot continues to work. There's also a report that openHAB integration continues to work with Opel. |
|
This issue seems the same as #674, might need to close this one and work in there other one? |
I can't confirm,
|
|
Tried again this morning and this time got another type of error :
|
|
Issues seems to be linked to another bug from Opel, I can't even log in the app anymore and the page doesn't seem to exist on myopel.fr xD |
Not for me... the form is at |
|
I now stored a full log in chrome from the login-form to the final login. What I just observed is, that two parameters seem to differ from what is used here:
I didn't yet test whether this makes any difference. |
Good point, I took a look into the APK 1.43.1 file and surprise, you will find both there :( in classses4.dex:
in parameters.json
The APK still contains the old ones: Since the app calls up a browser to log in, they can of course redirect as they wish... In openWB the "new" URL is already used since years and not working anymore too: |
|
After Update to V3.3.2 I have the internal error 400 again |
|
Facing same errors here (with DS auth realm for me).
It doesn't go any further compared to other logs shared higher. |
|
Same problem here. Error 400. What a fail company is Stellantis/PSA. (no bad words for @flobz and all people here for this great tool!). The app on the smartphone does not work most of time or very bad. Only bad reviews in the Playstore. And the don't fix anything about the apps. Sorry for my angry but i hope this app will work quckly again.... |
|
I started digging a bit deeper and tried to obtain a token manually via (A) currently the first step is to obtain the access_token, but according to Stellatis Web API documentation the first step is to get an autherization code (B) the autherization code should look as follows:
Any hints welcome 😉 |
|
PS: the android app uri |
|
if someone has |
I was trying the same and faced the same limit. Cannot find the right redirect. |
|
I thought about the same, using the documented flow from the PSA website. However, zhat would lead to a redirection of the user to the app to authorise the request and return the auth code. Wes need to register an app for that to work (doable, however client secrets won't be as secret as required as they need to get distributed). There has do be a different auth flow for the mobile app itself, that's what we're trying to replicate here. The mobile app can't redirect to itself to auth, as the user won't be signed in. |
Just scroll down the "Name"-section in the center of your screen, it's there under "authorize" after you press the "OK" button. Managed to get this far, but wasn't able to paste the retrieved code anywhere. Tried to paste it into the CLI I had opened the docker container in, but it did not do anything. |
|
Can someone please make this as simple as updating the app? Is this possible?I know people are trying to make work arounds, for the most it would seem they do/don’t work or are too complicated to follow and understand.From RobertSent from my iPhone On 26 Feb 2024, at 06:35, nuiler ***@***.***> wrote:
I can't find the code, are there any instructions?
image.png (view on web)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
I'm stumped - I can't find a "Name" section? |
Can you tell me how to stop? I do not have "ps" or such in the container. How should I stop the process? |
|
|
After pressing "OK". the code can be found from both of these items in the F12 -> Network inspection window. |
|
Finally got it right. Then the code was displayed under mymopsdk://oauth2redirect/de?code. |
|
For any of you running the app with docker compose, follow this steps to enter interactive console:
Follow the instructions for getting the code, paste it in the terminal... and it's done. ctrl-c twice to stop the container, then start it again with the |
|
After inserting the extracted code from Chrome Browser I run in that error: I run the car-controller in Docker on my Synology NAS. Any ideas? |
I see Author has just committed a change that lets you enter code from we interface. you could try using that now? |
Only press F12 when you get this page, that has the "OK" button. that way you only get 2 lines in network tab. |
I have installed the latest version (3.4.1) and the option to add the code via webinterface appears. But no Opel Login page will open... When I try to copy out the url from the logfile I think it contains wrong html UTF characters (e.g. %3D instead of = ). |
|
Hi @Apollon77 , I also had the same problems to stop the psa-car-controller within the docker container in order to restart it at the bash console.
You will get a running container where psacc is still not running yet. You may then start it by calling |
Put your URL here first and decode, then paste the decoded url in browser. |
That works! Many thanks @bennymamo |
|
Fix in v3.4.0 |
Do you have more details about updating to v3.4.0 / v3.4.1? Just making the update and using the login? Any migration guides? |
If installed via pip: |
|
Thanks, @TroisSix, but I think the process of updating the software via pip or docker is well-known and straightforward. The question refers if there are any manual config/database changes needed or just a re-login over the webinterface. (Edit: see next comment for update description. No database update needed) |
Update Guide
|
|
Hi, Thank you very much |
|
You still need to get the token using a webbrowser and devtools. Don't know if this counts as "simple" for you. |
|
Are there clear instructions that work? |
|
There are instructions now embedded in the normal psa controller release. With them and this: #733 (comment) And the information that the login window does not open by itself (at least it didn't for me) and you need to get the url out of the browser address bar and decode it yourself with e.g. https://www.urldecoder.org/ it is doable. But there is no one-click solution. |
|
Thanks everyone all works now for me! I hope there is also quick a solution for "Honk the horn" and "close the doors" :) |
|
It seems as if Opel changed the authentication method. |
|
@Cillian0305 have you tried the settings in the network tab to "persist logs"? |
|
I did now, but the code does not seem correct: replaced letters by x and numbers by 1 |
|
no further news? I would love to see the charge level of my Opel in Home Assistant again :-( |
and others
Apparently the PSA API has been fundamentally changed. When authenticating via the Webconfig, a "400 - server_error : Internal Server Error" is displayed. Other projects like evcc seem to have similar problems.
The text was updated successfully, but these errors were encountered: