Mercedes Me Binding

Add-ons Bindings
208

I see, sorry for the confusion

  • yes, it is merged but due to scheduled OH update cycles it isn’t part of any OH milestone or official release right now.
    It will be part of the next release in July!
  • that’s why I keeping the drops repo / Marketplace up to date with latest release candidate versions in order to test in between the OH release cycles
2 Likes
209

Thanks for your response.

I just updated to the latest OH 4.2.0 release. Now it’s working :slight_smile:

1 Like
210

Hey, about SOC state not getting updated - I reinstalled the bundle and now got the latest version → was still on 3.4. Thx for the hint!

Question: why is in OpenHAB 4.1.1 still the old MercedesMe bundle “default” → it is no longer usable…

211

Correct, openHAB update cycles are scheduled 6 months and sadly the new binding wasn’t ready till this release. OH4.2 is the first official release containing the new changes.
Please note that bindings like mercedesme and also mybmw are not based on an official Mercedes or BMW API with change announcements. Changes may break them quickly and we need some time to adapt. So there are OH releases which contains not working bindings.

212

Since this morning I’m getting status 418. Anyone else, too?

2024-10-17 09:21:26.423 [WARN ] [rcedesme.internal.server.MBWebsocket] - onError Failed to upgrade to websocket: Unexpected HTTP Response Status Code: 418 I'm a teapot
213

Seeing the same issue also here… :face_with_thermometer:

onError Failed to upgrade to websocket: Unexpected HTTP Response Status Code: 418 I'm a teapot`
214

I have the same error messages … what happens?

215

Same for me…

216

Me too

217

Hi there, probably related but I get “COMMUNICATION_ERROR; Websocket Exception: Reason: {0}”. I did everything I could think off, cleaning cache, rebooting, Mercedes auth but no change. Any updates for others?

218

And when I try disabling and reenabling the account thing, it persistently shows status Unknown

219

same here (COMMUNICATION_ERROR): Websocket Exception: Reason: {0}

220

The HTTP error suggest that the issue is with the Mercedes API endpoint, rather than with the adapter.

The home automation hub IObroker has a similar Mercedes Me adapter which was updated just two days ago with a change in the WebSocket endpoint which now requires an additional v2 designator.

So I presume we need to wait for the author of the binding to release an update. I opened a github issue to suggest the change.

3 Likes
221

Thanks for doing this. Although I think strictly you should have opened the Issue on the OH repo rather than on @weymann 's private repo…

222

Hi all,

I fixed this bug and started a pull request on the OH repo here: [mercedesme] fix websocket endpoint by rogrun · Pull Request #17594 · openhab/openhab-addons · GitHub

You can find a pre-release for testing here:
https://github.com/rogrun/openhab-addons/releases/tag/MercedesMe

Let me know when it works.

2 Likes
223

The new jar file v4.3.0 works now again. I am on OpenHab release 4.2.2. Thank you for your efforts Ronny!

1 Like
224

+1

The new Jar also works again for me (I am on OpenHab release 4.2.1).

THANKS A LOT Ronny!

1 Like
225

+1 Working again, many thanks.

226

I have used the binding successfully for a couple of weeks but so far I have been reading car status information using the OH Rest API. Currently I am controlling charge power on/off by controlling my wallbox (Garo). Is it possible to control charging on/off via the OH Rest API? Any example available somewhere, e.g using curl?

227

Thanks, perfect! I’m off for several days with no ability to test!

I follow Rene Nulsch and there seems to be some upcoming changes regarding authorization:

2 Likes