Closed Macrisu closed 1 year ago
Seems the switch to ne mercedes API didn‘t work. Will consult with MB developer support.
Probably caused by https://github.com/evcc-io/evcc/pull/6894. According to MB, mb:vehicle:mbdata:payasyoudrive
does not require additional contracting. We'll need to double-check.
Reverted 31201a9 for time being (in ebff68aa2d4de9d5dc4ab0179313e4008d2fdc79). Waiting for feedback from MB.
BTW: MB just confirmed, that they have an issue with their API anyway (contacted them because of https://github.com/evcc-io/evcc/issues/7465
" Sebastian Schempp commented:
Dear NAME , thank you for reaching out to us.
Unfortunately we detected a general issue for the BYOCAR API. Our developer team is on it. We will come back to you as soon as this issue has been resolved .
We apologize for the inconvenience
BR,
Sebastian
Sebastian Schempp changed the status to Under investigation.
View request · "
Seems to be solved, according to MB: :
Hello NAME , thank you for your patience.
We got informed that the incident has been resolved, the API should now work again.
Please check and provide your feedback if this is not the case.
Thank you in advance
BR,
Sebastian (mercedes Benz Devop)
Login works again. SoC is also displayed Target soc is adjustable
it seems to work fine at the moment... Thx.
Ahh, thanks for letting us know!
Hei,
still get the refresh token error .- where to put this ?
https://developer.mercedes-benz.com/content-page/oauth-documentation#
According to mercedes there might be something missing with "Please note that you will have to request an additional scope offline_access to receive a refresh token." - is this done in this integration? Because I still receive this error...
It is done:
oc := &oauth2.Config{
ClientID: id,
ClientSecret: secret,
Endpoint: provider.Endpoint(),
Scopes: []string{
oidc.ScopeOpenID,
oidc.ScopeOfflineAccess, // <---
"mb:vehicle:mbdata:evstatus",
},
}
If you need help troubleshooting please provide login details for info@evcc.io.
Seems MB had API issues that have been resolved. If we want to have odometer support (which is the reverted https://github.com/evcc-io/evcc/pull/6894) I would need help:
Does anyone want to try that?
installed 0.115.0, unfortunaltetly getting this "Internal Server error" error-message
With Additional api registration: No more error-message anymore when registering the vehicle in evcc, all seems to work.
Unfortunaletly, I did no screenshots when I registered the API, but it was pretty straightforward. only strange thing is, that MB lists it under "insurances"
But: I cannot see any Odometer-Information in the charging history, but probably because I haven't driven any yet:)
@HiroP77 inwiefern bezieht sich das auf https://github.com/evcc-io/evcc/issues/7156#issuecomment-1518037542? Hast Du den PR selbst gebaut und probiert?
Ich habe wie du oben geschrieben hast, "
Ich habe wie du oben geschrieben hast,
Ahh, jetzt check ichs- Du hast den PR getestet indem Du die 115 installiert hast? Super. Heisst also: wir könnten Odometer einbauen, es müssten aber alle Mercedesnutzer ihren Client im Developerportal aktualisieren. Bin mir nicht sicher, ob es das wert ist...
genau. den echten Mehrwert sehe ich auch nicht, zumal das "insurance pay-as-you-go"-anmelden für simple Odometer-werte bei MB echt kontraintuitiv ist. Vielleicht eher was für spätere Versionen, mit einer optionalen Aktivierung?
I am happy to test this feature. It should be possible to integrate it, since it does seem to work in my Openhab binding (with payasyoudrive for free). Alternatively, is it an option to use http based odometer value? One could then use the openhab Restapi to get the value.
Describe the bug
I've just made the upgrade to 0.115 I try to login for my Mercedes EQC and I get on the page this:
And the returned URL is like this:
https://ssoalpha.dvb.corpinter.net/v1/callback?error_description=The+requested+scope+is+invalid%2C+unknown%2C+malformed%2C+or+exceeds+that+which+the+client+is+permitted+to+request.&state=xxxx&error=invalid_scope#.
No problem in 0.114.1
Nothing was change in the config file!
Steps to reproduce
just upgrade
Configuration details
Log details
What type of operating system are you running?
Linux
Version
No response