Mercedes Me

Hmm. installed 4.3.7 from marketplace yesterday. For some reason it reset my location to North America. Fixed that, and it said I needed to auth but the auth endpoint wasn’t actually running. Disabled and reenabled and it came up successfully with no auth required. Today, unfortunately, it’s back to “Websocket Exception: Reason: Failed to upgrade to websocket: Unexpected HTTP Response Status Code: 429 Too Many Requests”

Events (anonymised slightly):


2025-08-05 21:17:02.007 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mercedesme:account:018e05972a' changed from OFFLINE (COMMUNICATION_ERROR): Manual Authorization needed at http://192.168.1.20:8099/mb-auth to UNINITIALIZED
2025-08-05 21:17:02.027 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mercedesme:account:018e05972a' changed from UNINITIALIZED to UNINITIALIZED (DISABLED)
2025-08-05 21:17:02.027 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mercedesme:bev:018e05972a:<my vin>' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2025-08-05 21:17:02.135 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mercedesme:account:018e05972a' changed from UNINITIALIZED (DISABLED) to INITIALIZING
2025-08-05 21:17:02.140 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mercedesme:account:018e05972a' changed from INITIALIZING to UNKNOWN
2025-08-05 21:17:02.210 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mercedesme:bev:018e05972a:<my vin>' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
2025-08-05 21:17:02.215 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mercedesme:bev:018e05972a:<my vin>' changed from INITIALIZING to UNKNOWN
2025-08-05 21:17:02.224 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mercedesme:bev:018e05972a:<my vin>' changed from UNKNOWN to UNINITIALIZED (HANDLER_INITIALIZING_ERROR): No value present
2025-08-05 21:17:02.929 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mercedesme:account:018e05972a' changed from UNKNOWN to ONLINE
2025-08-05 21:17:29.048 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mercedesme:account:018e05972a' changed from ONLINE to UNKNOWN
2025-08-05 21:17:29.259 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mercedesme:account:018e05972a' changed from UNKNOWN to ONLINE
2025-08-05 21:17:29.932 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mercedesme:bev:018e05972a:<my vin>' changed from UNINITIALIZED (HANDLER_INITIALIZING_ERROR): No value present to ONLINE
2025-08-05 21:17:30.197 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item '<proto update>
2025-08-05 21:28:29.418 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item '<proto update>
2025-08-06 15:04:37.647 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mercedesme:account:018e05972a' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Websocket Exception: Reason: Failed to upgrade to websocket: Unexpected HTTP Response Status Code: 429 Too Many Requests

The only things logged in openhab.log are from around the time I installed the upgraded version but I’m wondering if it didn’t actually upgrade. I’ll restart openhab and see if it’s reporting the correct version.

Nope. On restaring the plugin wanted a password from me, and when I entered it I’m back to the 429 error.

update:

OK! some progress.

  • I had a phantom install of 4.3.3.nnnnnn which didn’t appear to be doing anything but could not be removed from the UI. I had to resort to the console to get rid of it, and there was no trace of it other than its appearance in the module list, so I don’t know where its jar file actually was.
  • On removing and reinstalling 4.3.7, I now have: “Login failure, check credentials. Failed to login. HTTP 200 {result:GOTO_LOGIN_LEGAL_TEXTS”. I’m going to assume this means I need to manually truck through a login to the Mercedes website and acknowledge some legalese.

update

logged in manually via a browser, went back to the plugin and toggled it on and off, and now it’s working. I’ll see if it’s still going in 24h, per previous experiences. Thanks for the work you put into this, Bernd, and if there’s anything additional I can share to help debugging let me know.

Check 2 directories

  • /usr/share/openhab/addons if you manually copied a jar
  • /var/lib/openhab/marketplace/bundles/which contains numbers but within the jar with correct name is located

Btw, if you had two times the same binding running i would prefer to cleanup (like you did already) and perform one reboot. Otherwise there’s still the chance old stuff is connected

Sure, if everything is running with one binding installed you can enable TRACE log level then you’ll see more what’s happening.

If the car stands still and isn’t charging you’ll see lazy updates like this every refreshInterval

2025-08-07 00:07:13.445 [TRACE] [esme.internal.handler.AccountHandler] - Pull update delivered 150 updates
2025-08-07 00:07:13.446 [TRACE] [esme.internal.handler.AccountHandler] - Next schedule at 2025-08-06T22:22:07.446564293Z

While driving/charging websocket Websocket is active for frequent updates

Is the 4.3.7 SNAPSHOT the one with the 429 error fix ?

Is this running on openHAB 5 ?

Both yes. Official fix for OH5 is in review!

Hi Bernd, I have the snapshot running since 5 days. It’s working perfect. Thanks for the fixes. Uli

Have now upgraded my computer and openHAB to 5.0.3 and everything works out :grinning_face:. Many thanks to you for all your work and especially for providing me OH 3.4.6 versions of your binding for my Intel Compute Stick with a rather limited performance while this OH version was already outdated. Am really happy now to have carried out this step.

Wish you a nice Advent time.

Since some weeks the binding is offline. Reason:

Pretty sure the password hasn’t changed and i can still login via browser to mercedesme. Anything i could check?

Ok, let’s see. First I need some more infotmation.

  • Which OH and binding version. Any logs?
  • Was it running before and went offline?
  • Did you try something for recovery e.g. disable/enable thing?

Especially after enabling some trace logs are helpful.

Oh, of course. Sorry.

Yes, it was running for months and went offline somewhen i December. I first didn’t recognize it because we were not at home, so i don’t know when exactly.

Running openHab 5.1.0 and Binding 4.3.7 from Marketplace.

Yes, disabled it (had to, because it broke my MercedesMe Account by hammering wrong passwords) and couldn’t reenable it because of that.

Logs:

2026-01-25 10:27:38.098 [TRACE] [ercedesme.internal.api.Authorization] - No token for not set stored, stay on invalid token
2026-01-25 10:27:38.105 [INFO ] [enhab.core.model.script.Thing Status] - processing mercedesme:account:e5f71dc096 / INITIALIZING
2026-01-25 10:27:38.110 [INFO ] [enhab.core.model.script.Thing Status] - Set Timer for mercedesme:account:e5f71dc096
2026-01-25 10:27:38.111 [INFO ] [org.openhab.core.model.script.test ] - x {}
2026-01-25 10:27:38.113 [TRACE] [ercedesme.internal.api.Authorization] - No token for xx@xx.xx stored, stay on invalid token
2026-01-25 10:27:38.120 [INFO ] [enhab.core.model.script.Thing Status] - processing mercedesme:account:e5f71dc096 / UNKNOWN
2026-01-25 10:27:38.206 [INFO ] [enhab.core.model.script.Thing Status] - processing mercedesme:bev:8fdf62fca7:c387a58d2c / INITIALIZING
2026-01-25 10:27:38.207 [INFO ] [enhab.core.model.script.Thing Status] - Set Timer for mercedesme:bev:8fdf62fca7:c387a58d2c
2026-01-25 10:27:38.216 [INFO ] [org.openhab.core.model.script.test ] - x {}
2026-01-25 10:27:38.266 [INFO ] [enhab.core.model.script.Thing Status] - processing mercedesme:bev:8fdf62fca7:c387a58d2c / UNKNOWN
2026-01-25 10:27:38.314 [TRACE] [ding.mercedesme.internal.api.RestApi] - Get capabilities for VIN W1N9N0BB9SJ158298
2026-01-25 10:27:38.425 [WARN ] [ercedesme.internal.api.Authorization] - Failed request /v1/vehicle/W1N9N0BB9SJ158298/capabilitiesnull - org.eclipse.jetty.client.HttpResponseException: HTTP protocol violation: Authentication challenge without WWW-Authenticate header
2026-01-25 10:27:38.426 [TRACE] [ding.mercedesme.internal.api.RestApi] - Error retrieving capabilities: /v1/vehicle/W1N9N0BB9SJ158298/capabilitiesnull - org.eclipse.jetty.client.HttpResponseException: HTTP protocol violation: Authentication challenge without WWW-Authenticate header
2026-01-25 10:27:38.432 [TRACE] [esme.internal.handler.AccountHandler] - Next schedule at 2026-01-25T09:27:39.432274654Z
2026-01-25 10:27:39.434 [INFO ] [ercedesme.internal.api.Authorization] - Start login
2026-01-25 10:27:39.800 [TRACE] [ercedesme.internal.api.Authorization] - Step 1: Get resume code 200 - https://id.mercedes-benz.com/ciam/auth/login?resume=%2Fas%2F7g6UfTrLDz%2Fresume%2Fas%2Fauthorization.ping&request_info=eyJlbmMiOiJBMjU2Q0JDLUhTNTEyIiwia2lkIjoiRklSU1RfRU5DUllQVElPTl9JRCIsImFsZyI6IlBCRVMyLUhTNTEyK0EyNTZLVyIsImN0eSI6IkpXVCIsInAyYyI6NjU1MzYsInAycyI6IlFVWnVzbHYybEM4TW9LSWgifQ.bixF8bfBu5L-eYi7WAxxeFyo2vrfE--lcCDvt6lJZ_BlsaWkxWsDYOCCcfB57nEGXudzlcOALD-l3YFL2qpzmnTPA8816oqf.qdhTC-iFeEces_FjEXIllg.bF73BK5gImNwElVYm9J3C0ecZaTCgPUrtOMY9GuY27S7gpJ3g6IHnetdnB3YN9JBB3RxmgdmYV9v-6ZlPGS9pf5db1xzlNDMHgBPVht0foNG9nDxioPqDzdp7fGGAB0dFFiZ2i-mLHE9Q2GxMYd9Qs-NmKwWy_CkHKB46dBdW7FzLpu086cNC1BPSM2W31IjgnnQV_7uJ4YoTNzcyA-JAsRudGysGDSmGEYoo4g-wTvXIfkWua_s6nZo3BV4_XN6knLhJ_eUIsgMHALogDrGk_qUwyo65FNunIAztvClp5B0jM9VsAAp2n98SlBsURn0bpQCjuL6fNMSbpGcrzSfYBly0hVCGekJG1SBX26GHvE0iVWqppV3rBuq0S4Ru2B2RiPMF8pzUfbagI8l2gH3Zc8egSC28zi2Yc5qGSHVrUHEoIUPR1-IBmgk575fA4lI1XhShpUwAOflIa0uTfsaJ1Y5p1Nzk3gQDCAmVyt6fUplXzHXzuxZfNPYp9VtGdHxF3SI7n-EOoMwrRW5AR-HVOC1vkawPIOpzr6RJaHED0UwTUtkp2rkoMYJZv0bKH2_ceRR9UH_Lx3Wm_0mOr_kVqcwPOsfdS5CWJICt0etFk0tYu77pi8C4-RntntnfRHZJQWSaQYVcyilzNJJCK38O2gGTAXxWry6f-0-PA5tj86GZmzRYsgRZ1-3eCUTNpiwDm5sJLZfJiRVDd0LQ9JQjojGm3nu-ylrKG5JNTy9fypyKIBE9es1namuY72eqQ8HcJxiXV5DTePL9uUTZJONhN-vV7pTbOPIMORVYr6gdfEZfkVp9mg211xcQbzcIu4UFn2ZtFOHIeNnOCdk4FcSypysNjJ4qyZBkjEoN3641rla8pwp03DEvVrmZgDXhUfr5TmiBs2yJy957I6PRpsnU_Dd1jJU2QAPO58EHp2foKz1mHT35KL4hmMpYOSuHioJcyW51hp35WfCE0anDKV20Z1lG__bgo-wMnUFOpTt9Y0.pP_IgVALu01Tr-PS5gUBUlOtvYSPtAxfphDX-61L3gc
2026-01-25 10:27:39.831 [TRACE] [ercedesme.internal.api.Authorization] - Step 2: Post Agent 200 -
2026-01-25 10:27:39.855 [TRACE] [ercedesme.internal.api.Authorization] - Step 3: Post username 200 - {“result”:“GOTO_LOGIN_PASS”,“country”:“DE”,“lang”:“de”}
2026-01-25 10:27:39.887 [TRACE] [ercedesme.internal.api.Authorization] - Step 4: Login 401 - {“errors”:[{“key”:“errors.login.fail”}],“trackingId”:“6f4b2fa7f8b462c7f06e68f1696bba1e”}

So there is no token?

Just as side note: There’s no need anymore to take the Marketplace binding. All changes are in OH5.1.

No token available because login fails:

2026-01-25 10:27:39.800 [TRACE] [ercedesme.internal.api.Authorization] - Step 1: Get resume code 200 - [https://id.mercedes-benz.com/ciam/auth/login?](https://id.mercedes-benz.com/ciam/auth/login?
2026-01-25 10:27:39.831 [TRACE] [ercedesme.internal.api.Authorization] - Step 2: Post Agent 200 -
2026-01-25 10:27:39.855 [TRACE] [ercedesme.internal.api.Authorization] - Step 3: Post username 200 - {“result”:“GOTO_LOGIN_PASS”,“country”:“DE”,“lang”:“de”}
2026-01-25 10:27:39.887 [TRACE] [ercedesme.internal.api.Authorization] - Step 4: Login 401 - {“errors”:[{“key”:“errors.login.fail”}],“trackingId”:“6f4b2fa7f8b462c7f06e68f1696bba1e”}

Your usename is accepted in Step 3 so this is correct
Step 4 the real login reports error Login 401 - {“errors”:[{“key”:“errors.login.fail”}] so all points out the password is wrong.
Please triple check - any typos or password changed during the last weeks.

OK, used the openHAB official plugin, worked like a charm. WTF….but anyway, thanks so much for your help :slight_smile:

Have a CLA 220 4-matic “mild hybrid”. It has a small electrical motor (48V) integrated into the gear. Its battery doesn’t need an external charging.

Now to my question: Is this vehicle still covered by “combustion” w.r.t. this binding?

Yes. If you have this already and the vehicle is visible in your MercedesMe app on your account isn’t there a new thing discovered an put to your inbox?

Thanks for your quick response. The car is already active in the MercedesMe App but no new thing has been discovered in OH.

Please check /var/lib/openhab/jsondb/mercedesme.json. Is there an entry with your vehicle vin xxx-features?

Yes, for the VIN there is the following entry:

"xxx-features": {
    "class": "java.lang.String",
    "value": "{\"features\":{\"auxHeat\":false,\"bidirectionalCharging\":false,\"chargingClockTimer\":false,\"controllableRearWindowBlind\":false,\"controllableSunroof\":false,\"convertible\":false,\"dcCharging\":false,\"distronicPro\":false,\"doubleDoorLock\":false,\"driverAssistancePackageHigh\":false,\"driverAssistancePackagePlus\":true,\"ecoCharging\":false,\"fastCharging\":false,\"hepaFilter\":false,\"hybridEncryptedPictureTransfer\":false,\"mopf\":false,\"nacsToCcsAdapter\":false,\"pictureTransfer\":false,\"pluggedStateDependingPreEntryClimateControl\":false,\"precondNow\":false,\"rearSunProtectionBlinds\":false,\"remoteHornSingleHonk\":false,\"remoteSettingPersonalizedTemperature\":true,\"remoteSettingTemperature\":true,\"twinTire\":false,\"urbanGuard\":false,\"variableOpenableSunroof\":false,\"variableOpenableWindow\":true,\"weeklyProfile\":false},\"vehicle\":{\"acMaxChargingPower\":null,\"baumuster\":\"178347\",\"changeYearCodes\":[\"056\"],\"chargingSocket\":null,\"controllableSunroofBlindsCount\":null,\"dcMaxChargingPower\":null,\"dcMaxDischargingPower\":null,\"digitalVehicleKeys\":[\"APPLE\"],\"doorsCount\":4,\"doorsHandleType\":null,\"drivingSide\":\"LEFT\",\"electricVehicleType\":null,\"electricWindowLifts\":[\"FIRST_ROW_LEFT\",\"FIRST_ROW_RIGHT\",\"SECOND_ROW_LEFT\",\"SECOND_ROW_RIGHT\"],\"fuelTypes\":[\"GASOLINE\"],\"headUnitSoftwareVersion\":\"SOP\",\"headUnitSoftwareVersionRaw\":\"SOP\",\"headUnitType\":\"GEN20XI3\",\"mbOsVersion\":\"MBOS_VERSION_1_0\",\"modelYearCode\":\"806\",\"powertrainBatteryModel\":[],\"productGroup\":\"PASSENGER\",\"remoteSeatConfiguration\":\"EACH_SEAT_INDIVIDUAL\",\"starArchitecture\":\"STAR3_5\",\"sunroofType\":null,\"tcuType\":\"ARTEMIS\",\"tirePressureMonitorType\":\"TIRE_PRESSURE_MONITORING_SYSTEM\"}}\n"
  },

It seems to run still as combustion, similar to my last A 220 d. Is this conclusion right?

Features looks good. Did you already try to create a combustion thing manually with your vin?

Created a combustion manually. This works out :grinning_face: . Many thanks.