I got my EQB last week and wanted to integrate into OpenHAB to basically track mileage and positions.
I finally found this extension which, after some struggling with OH, I got almost working. I authorized, the car was found, I entered the VIN and now I’m greeted with:
What can I do to help debug this?
Edit: As text for later reference:
HANDLER_INITIALIZING_ERROR
'void org.openhab.core.library.types.DecimalType.<init>(long)'
I assume you installed binding via marketplace, right?
Unfortunately there are some problems in marketplace evaluating the right binding version. From the error you reported I think the wrong binding version was installed.
Which version of openHAB do you run?
I’m running openHAB 4.1.1 -Release Build- (looks like your screenshot). The binding says “Updated At
November 26, 2023 3:33 PM”.
Should I try to install the version manually?
Sadly openHAB Marketplace is mixing up versions. So first cleanup everyting mentioned in post here. (Snippet below)
Afterwards put linked jar in addons folder
Hi Bernd,
I’ve updated to 4.2.0M1, and it seems that the manual binding in the addons folder (4.1) is not recognized anymore.
Do you have a new version? or did you plan to fix the marketplace?
thank you so much
Andrea
It is now part of the OH official bindings (so the marketplace version may not be needed any more).
well, actually in the official there is still the old version (not working), no the new one.
Hi Andrea,
I’ve also updated to 4.2.0M1 and the binding in the addons folder was recognised and is working well. Have you tried
openhab-cli stop
openhab-cli clean-cache
openhab-cli start
Regards,
Boris
yep thank you, it worked.
What I would like to say, is that till now the “official” version in the store is still the old one (not working anymore), and the version in the marketplace is the new one, but not the last one. If you like to use the last one (4.1), you need to put the jar file in the addons folder.
Hi Bernd,
thank you for this addon!
Unfortunately, I’ve some issues during the authorization phase. I’m running openHAB 4.1.1 and put the jar, linked above into the addons folder. It seems to be correctly initialized (anyhow, I’m wondering about the version 4.0.5, while the jar is 4.1.0-SNAPSHOT):
327 │ Active │ 80 │ 4.0.5.202311261329 │ openHAB Add-ons :: Bundles :: MercedesMe Binding
I entered the correct Mercedes Me E-Mail in the bridge properties and I’m able to access the /mb-auth page, but unfortunately I don’t receive an e-Mail with the code. The logs don’t contain any entry from this addon.
Any ideas why it’s not working?
Hi,
are you using the jar posted here right? not the version official, nor the version in the marketplace (both don’t work for me).
Andrea
Thanks for the answer. Yes, I’m not using the official version nor the version from the marked place. I used the jar linked above.
Surprisingly, in this post, the addon version is 4.1.0.202309262106 , while mine is 4.0.5.202311261329 (I also confirmed this with the MANIFEST.MF file of the jar).
Is there a newer version available?
I have your identical version of the binding, on OH 4.2.0M1, and it works like a charm
Andrea
Any update on the new binding?
No, 4.0.5 is fine - works for all 4.x.y versions.
You can set log level to TRACE to increase log output in console via
log:set TRACE org.openhab.binding.mercedesme
Hard to say with provided info. Did you
Hi,
I am succesfully using the binding since month. But I noticed a quite severe delay sometimes that e.g. the battery SOC is not updated for more than half an hour (this is crucial as I control charging via OpenHAB and want to stop at 90%).
When I look to the Mercedes App OR the MercedesMe Website I see updates in a range of max. 1 min delayed.
Is there any reason for that? (my bridge is configured to 5 min updates) Can I do here something?
Version: 4.1.1 (Release Build)
Thx
When you say since months it’s getting interesting which version you have installed.
In principle this problem was already addressed. Version 2.1-alpha keeps the websocket open while you’re driving or charging. This ensures real-time updates.
After checking your version activate TRACE level in order to see if anything happens during the updates.
PS:
Please note you’ve the max-soc channel in charge group as described here which is writable! This sends the command towards the vehicle to stop at a certain soc level.
I am on OH v4.2 latest Milestone. Does that version of the binding support the ‘new’ account model? The doc seems to imply that the binding has not yet been updated to support that. Or??
Sorry, I don’t know what the new account model is. Do you mean the switch to Mercedes SDK?
It’s merged and the documentation is up to date in my drops repo referenced in Marketplace
Yes.
This is the point where I got confused. On one hand you say the new SDK is ‘merged’ (presumably meaning that it is part of the official OH binding), and on the other hand you say it is a ‘drop’ on the marketplace (presumably meaning that it is not part of the official OH binding).
If it is not part of the official binding, then I wonder why not, and when it will finally become part of the official release. (There seems to be no point in OH publishing an official release which is admitted by all parties now to be not working…)
