-
Notifications
You must be signed in to change notification settings - Fork 63
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
OAuth 2.0 for mercedes api is not possible #60
Comments
Nothing new here? |
Could you please try the OAuth 2.0 Redirect again with open Web Developers Toolbar and show us which requests fails and why? |
Hei! Ypu mean the integrated one from Chrome or Firefox? I can try my best :-)
Gesendet von AOL auf Android
Am Do., Apr. 13, 2023 at 17:09 schrieb Timo ***@***.***>:
Could you please try the OAuth 2.0 Redirect again with open Web Developers Toolbar and show us which requests fails and why?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Exactly. Otherwise it's impossible to troubleshoot this, because i don't own any MB car |
Got something from the debugger:
|
I now switched to an custom MQTT Sensor. Home Assistant, where my evcc is running on / for - is sending the Battery SOC and range all 15 minutes via MQTT. EVCC then reads these datapoints in and tada - here we go, i always get the important values without dealing with the MB oAuth in EVCC (Which was quite buggy on my side). |
not addon related, open it in : https://github.com/evcc-io/evcc or discuss it in https://github.com/evcc-io/evcc/discussions |
If evcc is hosted in a docker environment on home assistant the OAuth 2.0 redirecting is not working correctly, because the url of mercedes for the authentification process get's blocked in the home assistant container.
The text was updated successfully, but these errors were encountered: