MMM-MercedesMe

ashishtank

@pyrophoenix can you please restart the mirror and check if it works ? did you login to get the token ?

pyrophoenix

Yes I did reboot and it ask to authenticate everytime that I reboot it. I have to click on it then it goes blank page and the picture I’ve sent appear

ashishtank

@pyrophoenix can you delete the tokens.json file in MercedesMe directory and then restart the mirror ? it should show you login button and then you should be able to login and get token. after that check if tokens.json file is created or not…

pyrophoenix

@ashishtank Thanks for your reply!

I think I was looking the finger instead of the sky…I found the issue but couldn’t resolve it. It request EV while I have a petrol (But my config as you saw earlier was correct). On the logs I have that part saying:

[07.04.2021 22:13.34.301] [LOG]   Vehicle data url https://api.mercedes-benz.com/vehicledata/v2/vehicles/W1************9/containers/electricvehicle

Then I missed that part (That I thought was for another modules):

[07.04.2021 22:13.34.785] [LOG]   403 - Forbidden

On request it says:

[07.04.2021 21:53.39.767] [LOG]   Handle OAuth request
[07.04.2021 21:53.39.784] [LOG]   https://id.mercedes-benz.com/as/authorization.oauth2?response_type=code&client_id=d***********eb&&redirect_uri=http://localhost:8080/MMM-MercedesMe/callback&scope=mb:vehicle:mbdata:vehiclestatus offline_access&state=7********************************f
[07.04.2021 21:53.41.314] [LOG]   Handle OAuth callback
[07.04.2021 21:53.41.844] [LOG]   OAuth callback Success

Meaning that now the token is indeed good but it request EV status rather then the rangeliquid and tankvalue (as mentioned here: https://developer.mercedes-benz.com/products/fuel_status/docs). M’I missing something?

pyrophoenix

@ashishtank Just one thing that I saw…Step 7 has your Client ID and Secret uncovered. I highly recommend to blur it if it’s still an active account :/

ashishtank

@pyrophoenix Hi Looks like you found the issue for me :) the vehicle type right now i am checking is only Electric (default) and Diesel. I will improve the code to check for petrol as well but you can have a work around and can configure your vehicle type as 'diesel' and it will work as api is same for diesel and petrol !

getVehicleDataUrl: function (config) {
......
  var vehicleStatus = 'electricvehicle';
  switch (config.vehicleType.toLowerCase()) {
    case 'diesel': <-----------------------------------------------------------------------------
      vehicleStatus = 'fuelstatus'; 
......

About my sample client id and secret in guide they are fine as I do not have a Car :D and also that account and app are throw away account with out any real car linked to it.

Let me know if changing the config to diesel and restarting mirror solves the issue.

pyrophoenix

@ashishtank Thanks for the reply!

I have erased token and reboot it with Diesel…Still the same issue but this time it goes to the correct URL

[08.04.2021 13:38.22.939] [LOG]   Handle OAuth request
[08.04.2021 13:38.22.946] [LOG]   https://id.mercedes-benz.com/as/authorization.oauth2?response_type=code&client_id=c****************4a&&redirect_uri=http://localhost:8080/MMM-MercedesMe/callback&scope=mb:vehicle:mbdata:vehiclestatus offline_access&state=d*************************e
[08.04.2021 13:38.25.124] [INFO]  Newsfeed-Fetcher: Broadcasting 66 items.
[08.04.2021 13:38.26.049] [LOG]   Handle OAuth callback
[08.04.2021 13:38.26.982] [LOG]   OAuth callback Success
[08.04.2021 13:38.34.388] [LOG]   Vehicle data url https://api.mercedes-benz.com/vehicledata/v2/vehicles/W1****************9/containers/fuelstatus
[08.04.2021 13:38.35.647] [LOG]   403 - Forbidden

It is still saying error 403

ashishtank

@pyrophoenix did you followed the step 3 correctly ? did you linked fuel status scope with app ? as shown in image below you should see
Fuel Status BYOCAR

pyrophoenix

Thanks! Great that YOU point it out! I cheated a bit and directly put the “fuel” on the URL as so

https://developer.mercedes-benz.com/products/fuel_status/get_access?pm=free

I just added it and I’ll try now.

pyrophoenix

Not working…But it seems that the Bearer is not generated properly. If I try the test curl provided by the Mercedes Dev, it does work…

ashishtank

@pyrophoenix Can you delete the app in Mercedes dev portal and create new one with correct scope ? also delete tokens.json file and restart the mirror. I think it is some caching issue.

pyrophoenix

@ashishtank Remove and did a brand new app on console. Removed tokens.json and reboot…Same problem

There is one thing that is on your step (Right from step 1) saying:

AUTH CALLBACK URL: http://localhost

Where that needs to be introduced?

pyrophoenix

image url)

ashishtank

@pyrophoenix things looks correct, http://localhost:8080/MMM_MercedesMe/callback is important other localhost urls in callback are optional. I have sent you PM what we can do next.

ashishtank

@pyrophoenix Let me know if changing the scope solves the issue. I will update the documentation accordingly.

pyrophoenix

@ashishtank Hi! Unfortunatly it didn’t :/ Mercedes are looking at this matter and they will get back to me normally on Monday.

Thanks again for your help and I’ll keep you informed!

Andreas Heins

When i press “Authenticate” i only get “Handle OAuth callback” in the Log and nothing more.

Any Ideas?

Mit freundlichen Grüßen
Andreas

ashishtank

@andreas-heins Is your configuration correct ? if you have already logged in then it will not display login screen and will directly get token. Did you check if tokens.json file is created and updated after authentication ?

Andreas Heins

@ashishtank i checkend my configuration and now i have another error „ 400 - Invalid redirect_uri“.

ashishtank

@andreas-heins looks like you are missing Step 7 from https://github.com/ashishtank/MMM-MercedesMe documentation. Please check, also which version of Magic Mirror are you using ? there are breaking changes in v2.15 in MM core and issue i have not fixed for my module yet.