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 
. 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 .
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