Domoticz

Just after posting I have tried again and it works now.
So best is to renew your auth code with :
https://ssoalpha.dvb.corpinter.net/v1/a ... t_id=<your client ID>redirect_uri=https://localhost&scope=openid%20mb:vehicle:mbdata:vehiclestatus%20mb:vehicle:mbdata:fuelstatus%20mb:vehicle:mbdata:payasyoudrive%20mb:vehicle:mbdata:vehiclelock%20mb:vehicle:mbdata:evstatus%20offline_access&state=test&prompt=login%20consent

and to put the response code again as password in the Hardware definition in Domoticz.

@frankdep
I also use the new method,
but I also have some issues with the app on my iPhone, it's sometimes reacting very slow or not, when (example) open/close the windows.
perhaps the Mercedes api is sometimes overloaded....

frankdep wrote: ↑Tuesday 06 June 2023 12:48 Just after posting I have tried again and it works now.
So best is to renew your auth code with :
https://ssoalpha.dvb.corpinter.net/v1/a ... t_id=<your client ID>redirect_uri=https://localhost&scope=openid%20mb:vehicle:mbdata:vehiclestatus%20mb:vehicle:mbdata:fuelstatus%20mb:vehicle:mbdata:payasyoudrive%20mb:vehicle:mbdata:vehiclelock%20mb:vehicle:mbdata:evstatus%20offline_access&state=test&prompt=login%20consent

and to put the response code again as password in the Hardware definition in Domoticz.

Yes, I also use this, the new token works fine, but after some time, it failed again

I have had this issue for day or two also.
I get new authorization code and refresh token just fine, so that should indicate that authorization code is ok.

But, when I insert the new refresh token into uservariable and new authorization code into "password" field of domoticz, result is:

Jun 6 16:15:31 curder domoticz[28133]: 2023-06-06 16:15:31.850 Status: MyMersu: Worker started...
Jun 6 16:15:32 curder domoticz[28133]: 2023-06-06 16:15:32.850 MyMersu: Attempting (re)login (using stored refresh token!).
Jun 6 16:15:33 curder domoticz[28133]: 2023-06-06 16:15:33.371 Status: MyMersu: Received unhandled HTTP returncode 502 !
Jun 6 16:15:33 curder domoticz[28133]: 2023-06-06 16:15:33.372 #033[1;31mError: MyMersu: Failed to get token.#033[0;0m
Jun 6 16:15:33 curder domoticz[28133]: 2023-06-06 16:15:33.372 #033[1;31mError: MyMersu: Failed to refresh login credentials.#033[0;0m
Jun 6 16:15:34 curder domoticz[28133]: 2023-06-06 16:15:34.374 MyMersu: Attempting login (using provided Authorization code).
Jun 6 16:15:34 curder domoticz[28133]: 2023-06-06 16:15:34.660 Status: MyMersu: Received (400) Bad Request.. Unexpected unless something has changed! ({"error":"invalid_request","error_description":"invalid auth code"})

Hmm....now it works again, after couple of days and about 5 separate attempts re-do authorization during that period.

So, maybe it is a intermittent "Bad gateway" (502), let's see how long it keeps working.

problem seems solved now, it looks like it was a Mercedes api (overload?) problem.

Any 5xx response code means something went wrong at the mercedes API side. Nothing domoticz can do about except reporting it.

kiddigital wrote: ↑Wednesday 07 June 2023 21:40 Any 5xx response code means something went wrong at the mercedes API side. Nothing domoticz can do about except reporting it.

That's good to know @kiddigital, I already thought it was not a domoticz but an api problem, after a couple of day's the problem was gone.
(and after getting a new token)

Hello all,

Not sure if all/more users of the MercedesMe domoticz integration did receive an e-mail from Daimler/Mercedes-benz, but they announced the EOL of their BYOCAR product on which the integration is based!

The BYOCAR will be taken offline already by the end of August 2023!! (in just a few weeks after the announcement )

It is unknown if/when an alternative might be announced.

So unfortunately, it looks that we no longer can get information from our Mercedes vehicle in Domoticz and the integration will stop working

Very sad, that, in this case, Mercedes announce this at such a short-term, that nobody would be able to implement an alternative solution, if that would have existed.

See the full text below:

Dear BYOCAR users,

Since June 2020, we have been offering you and many other Mercedes-Benz customers the opportunity to access selected data of your own Mercedes-Benz vehicle with the BRING-YOUR-OWN-CAR initiative. The underlying technology has changed significantly during this time and the BYOCAR infrastructure no longer meets our current technical requirements. Therefore, we have to inform you that the BYOCAR data products will be switched off by us on 31.08.2023. Due to technical conditions, we will start the stepwise sundown on 28.08.2023 already.

We would like to thank you for your BYOCAR commitment over the past months and years.

We are working on a new solution and will provide information on this via our Mercedes-Benz /developers portal and via our newsletter.

Regards,
Your Mercedes-Benz /developers team

"We are working on a new solution and will provide information on this via our Mercedes-Benz /developers portal and via our newsletter."
Because the are German, this can take a long time......