Just grabbed 4.3.3 from Github. Works. Thanks so much 
@anne_hh You’re so fast 
Binding is now updated on Marketplace.
It fixes the problem with authorization which is reflected in HTTP error messages with code 412 and 418. Users who passed the auth process everything should be fine.
For new users the above mentioned auth process is not working anymore!
Mercedes discontinued the PIN approach so you won’t receive an email anymore as described in readme. They’re using now also a captcha to avoid non-human data access - BMW users know this pain - thanks for that Mercedes!
I’m already in contact with Home Assistant & ioBroker developers to deliver a common solution.
Had enough pain, so, yes, i was looking often
Thanks for your efforts! I simply cannot understand why they (and others) put up barriers instead inviting guys that make their hardware more open and usable - but that’s another story.
4.3.3 is working now again, thank you for your efforts and further clarification work for the captcha based solution. 
sorry, stupid question: how can I trigger the upgrade to 4.3.3?
P
@olili Just replace the existing .jar file in your local oh addons folder - if any - by the new 4.3.3. version recently published by @weymann . If you are currently using the official meredesme binding maintained and distributed via Add-on Store (currently on version 4.3.2), deinstall it first bevor you put the 4.3.3 .jar file manually into your local oh addons folder.
The PIN request via mb-auth seems to be back again… The “Something went wrong” message is gone.
May i ask again for a working version for OH 3.4.5? Thank you in advance.
@Josef Yeah, seems the message is gone nevertheless at least I don’t recieve the PIN mail anymore.Maybe this works still for some users but I’m sure this will run step by step.
You are right, now the PIN mail is not running for me anymore too…
Thank you so much. Works out again. My goal is to upgrade to a new Smarthome PC and the latest OH version befores Win10 expires 
.
Hi There, My MB-auth is also not wokring anymore, so I downloaded the app token creation. This works fine as I get a token but I have no clue where to put the token in the binding, do I miss something?
Can correct myself as I had to update to the brand new binding. However, if I use the token (refreshed several times) I get “Handler missing error”. Any ideas?
Do you have deinstalled old version? Any screenshot or more infos on Handler Missing Error?
Marketplace is updated with new authorization process. Described in readme how to generate refresh token.
Many thanks to @Rene_Nulsch for providing this solution so fast!
For those already running this binding
You can enter abc or whatever you want into the mandatory refreshToken field. If the stored token is valid this will work. Otherwise follow the readme process.
Normally restart iOH sn’t necessary. Your screenshot shows a basic error so I assume there’s something wrong with the installation.
Please login on your openHAB machine and open the OH console and passowrd habopen. List bundles and state via bundle:list -s and check the result
- check that only one mercedesme entry is shown
- is the version matching 4.3.3.202502050109
- is state
Active - btw - which openHAB version do you run on?
ssh -p 8101 openhab@localhost
bundle:list -s
There is only one MercedesMe entry with status waiting, version is OK I think. Used OH version is 4.1.1