Mercedes Me

Hey @weymann , as of yesterday I get the message Websocket Exception: Reason: Failed to upgrade to websocket: Unexpected HTTP Response Status Code: 429 Too Many Requests"After reinstalling the marketplace “4.3.4-snapshot.jar” version it worked again but today the erro message is back again. I did pause it for a while today but did not help, any ideas?

I am getting the same.

I have the same trouble, since upgrade to 4.3.5 i get the same error, after deleting and reinstalling the Binding and setup it will work again for half a day, then the problem occurs again.

Websocket Exception: Reason: Failed to upgrade to websocket: Unexpected HTTP Response Status Code: 429 Too Many Requests

I am running openhab 4.3.5 with the official mercedes me binding on an Raspberry Pi5 with Debian bookworm.

I would appreciate if somebody could help me, Thanks in advance

I reinstalled the binding this morning and all fine but now I get the same error again. So indeed half a day it seems. Running on 4.3.3

I am also seeing the same issue.

As a possible clue, I remember seeing the same errors in the past with older versions when setting the refresh value lower than 10 minutes. I presume this error indicates that the API is refusing too many in-flight simultaneous requests. At that time, I stopped having problems by setting longer refresh cycles.

Unfortunately, this seems to happen now also with the refresh parameter set to the default 15 minutes.

My refresh rate is by 60 minutes, i think it’s something more essential

Same error here (from the Bridge):
COMMUNICATION_ERROR

Websocket Exception: Reason: Failed to upgrade to websocket: Unexpected HTTP Response Status Code: 429 Too Many Requests

Think alll have this issue, allso home assistant users are facing the same HTTP 429 response - too many requests. I could solve this with suspending updates over night but next day after some hours again OFFLINE.

Currently it’s unclear which new throttling mechanism is introduced by Mercedes. Analysis is ongoing.

Just an observation from my side: simply “disabling / enabling” the item doesn’t seem to help - the error keeps showing. However, if I change one of the letters in my login name to uppercase, the item turns green again for the next day (e.g. @blabla.com to @blabla.Com).

Have the same issue here still using OH 3.4.5 :slightly_smiling_face:. Observed the following: if i switch the region, the account thing is “Online” for North America and Asia Pacific while the web socket error occurs for Europe and China. Hope that this information helps you.

Today it works out again for me without doing something :slightly_smiling_face:.

It’s working since yesterday now, seems that the problem was on Mercedes side ? Does anybody heard something from Mercedes?

As an update from me, if you disable the binding overnight it will come back online the next morning. However, about 24 hrs later it give the error again. Currently it is offline again so have to wait again…Running openhab 4.3.3 and a Mercede Me refresh interval of 15 minutes

Can confirm this behaviour. Today the problem is present again.

Ok, just one day, then the same behaviour as before

Chiming in with a “me too” here. It seems like if I “pause/unpause” the binding it doesn’t actually try to reset in any way; it briefly changes the status to “unknown” then goes back to the previous error. Feature request: make a “log out” or “discard current login information” button to force the binding to reauthenticate from scratch?

Me too. Placing it offline for some hours seems to help.

Correct, unknown how many hours are necessary exactly but simply disable/enable account doesn’t work.

To say it bluntly: Doesn’t work, throttling is remembered.

This isn’t a binding appreciated by Mercedes. There’s no official API where you can ask questions or get prehand information. I think they are doing their best to avoid continuous bot requests.

Really a shitty issue and I’m still not able to provide a clean 24h run. Same as Home Assistant side where @Rene_Nulsch is trying with several falback machanisms to recover the situation. Give him a beer for his deep expertise which is needed for this binding!

Testing is hell because until it works again you need several hours plus 24 hours to check if the fallback mechanism works. Checking an idea is taking more than a day! I’m not running out of ideas but testing takes a lot of time :frowning:

Time to test!

Mercedes surprised us with some breaking changes

  1. Login procedure changed. Therefore configuration changed for Account. Please provide your email and password, refreshToken is gone as parameter - not longer needed. You may receive an email from Mercedes when successfully logged in.
  2. Throttling is introduced which causes 429 HTTP responses preventing continuous data updates. I changed the update strategy which runs now on my system 24h+ without any blockers.

Remove your running version first - not necessary to delete your things! install MercedesMe binding from Marketplace or drop bundle from top post into addons folder. The provide your password for Account thing in order to have configuration complete.

Thx Weyman, up a fix quickly.

I tried by:

  1. deinstalling Plugin
  2. installing from market place
    3 existing thing has Passwort Field
  3. filled in and verified multiple times that it is correct
  4. get error:
    HANDLER_INITIALIZING_ERROR

java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $

Any idea? Creating a new thing Shows Same error