Hi,
I got the binding to work after following the very well detailed readme. All worked fine until a reboot of my rpi. Since then, both things (the mercedes me account & the car) have the status UNINITIALIZED. I don’t see any errors in the log, and what is strange, is that I can’t change a thing in the settings of the mercedes me binding. I can only delete the things, all other settings have dissappeared. It didn’t change after another reboot.
Any ideas what went wrong or what to do? (Openhab 3.2.0)
I don’t know which version you installed but during the first version 0.1 and the current v1.0 release candidate several changes were made which are not 100% compatible. That’s somehow not avoidable because I got some valuable input from the Community and also from the maintainer reviews.
I suggest the following:
Delete your things and items
if you’ve files rename .things file to something like .things-orig
in UI go to MercedesMe things to Channels and Unlink all and Remove Items. Then delete all things. Note: Removing items doesn’t delete history data!
In Marketplace uninstall MeredesMe binding. Give it a minute for proper deinstallation
Install it again from Marketplace to have the latest version
rename your .things-orig file back to .things or create them in UI with the same labels and your history won’t be lost
Maybe you need to authorize once again calling the http://YOUR_IP:YOUR_PORT/mb-callback URL but after you’ve performed the painful first setup this is one click now.
Is there a reason to maintain this binding as published in the marketplace, with a risk of confusion for the users, while the binding is now part of the official distribution?
Sometimes it’s nice to have such a space to test changes like v1.1 which required changes to handling API.
But ok for me to close it to avoid confusion.
Do I have to perform some actions to remove this from Marketplace?
@Spaceman_Spiff
Can you provide some more information besides this one liner? There’s no hint MercedesMe binding is causing this message. E.g. openHAB version?
THX, found it: “tankLevelAdBlue”:{“display_value”:“29”,“timestamp_in_ms”:1731353728000,“ratio_unit”:“PERCENT”,“timestamp”:1731353728,“int_value”:29}
Will exptract it for the time being by transformation profile.
May be you can include this information offically in your binding.
Please update your OH @dk8pn!
Nevertheless there are just some minor compatibility errors so I was able to build a compatible version. But no warranties!
Many thanks for the compatible version. It works out great and has more channels than my previous version .
Upgrading is not that easy with my existing environment. My productive OH is running on a 64bit Intel Compute Stick (Windows10). Acc. to other OH users JAVA17 would likely create resource issues. OH 4 also had multiple issues initially which might have been improved or solved now.
Nevertheless i will envisage such change on a new Smarthome computer over time.
Ok,it’s the websocket from MercedesMe. The log belongs to jetty http component and it’s a general message “Websocket closed before reading everything”. I see this message occasionally, but not regular as you described.
For further checks:
If you say seconds something is deeply wrong. The Websocket runs for 1 minute within the configured refreshInterval which is per default 15 minutes. Did you just dropped the bundle into addons folder? Did you reboot? Maybe the old websocket instance is still running in the background … whyever.
Enable TRACE log level. There are some traces in websocket if e.g. exceptions are thrown.
I’ve installed it directly from ui and set refreshInterval=10 in the thing config.
After a restart the behavior is still the same but the binding was somehow downloaded again.