-
-
Notifications
You must be signed in to change notification settings - Fork 259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't log in any more #706
Comments
I also started having errors a few days ago, and eventually just deleted the addon from Home Assistant and started from scratch because nothing else worked. I'm now unable to sign in and getting the following errors:
Thinking the target api version error might be pointing to the same issue? |
API level error is quite normal, the Warning show up earlier - #181 (comment)
Maybe the used APP Version 1.33.0 (APK in GIT) is to old and need to replace with 1.43.0 (not sure, but we have similar issue #416 (comment)) |
@robotfishe do you have an error in the log ? These warnings should be ignored. |
Pretty sure my issue is the same as #674 , logs look the same. |
duplicate with #674 |
The system was working fine for months, but recently the SoC for my car stopped updating and just reported the same value. Figuring their servers had probably gone strange again I tried generating a new OTP code but never received it. I then decided it probably just needed logging back in again. I entered my details into "user config" but now all that happens is I get a red box underneath the submit button...
If I look in the logs I see the following message repeated every time it tries to refresh the car's data.
I am using the correct email address and password though, it works in the phone app.
If only Type 2 AC charge connectors could also communicate with the car's BMS to read battery state like the CCS ones do.
HTTP response headers: HTTPHeaderDict({'Content-Type': 'application/json', 'X-Client-IP': '10.128.158.240', 'X-Global-Transaction-ID': 'xxxxxxxxxxxxxxxxx, 'Strict-Transport-Security': 'max-age=31536000; includeSubDomains', 'WWW-Authenticate': "Bearer error='invalid_token'", 'Date': 'Sat, 09 Dec 2023 15:15:48 GMT', 'Connection': 'close', 'Set-Cookie': 'PSACountry=GB; Domain=.groupe-psa.com; Path=/', 'Vary': 'Accept-Encoding'}) HTTP response body: {"httpCode":"401","httpMessage":"Unauthorized","moreInformation":"Cannot pass the security checks that are required by the target API or operation, Enable debug headers for more details."}
The text was updated successfully, but these errors were encountered: