@c0rtez
Sorry, but OH3 is too old. The code from 3.4 binding doesn’t match witht this OH version and also compiler version changed.
@akashkumar proto-update is an advanced channel. It’s not necessary for this binding functionality but necessary to debug faults. Switch in your vehicle thing to channels and mark the Checkbos Show
advanced (see picture below)
Ok, thanks. Anyway planned to startet a new installation based on OH4. Have the Pi on my desk for 2 month now I guess… Now I have a reason to finally do it.
Thanks @weymann. Somehow, my thing wasn’t showing it at all. I deleted it and added a new thing which indeed shows a lot of channels now, including the ‘Advanced’ option, with the proto channel.
I checked the proto channel. It seems the proto-channel data is there, but it doesn’t immediately get transferred to the other channels like odometer. Any reason? Would it help to paste the proto-channel output - it is a lot though.
Yes, polling interval is set to 15 minutes. I’ll add a config value in order to configure it
Not sure if this is the right way.
In my use case, I would like to determine if the vehicle is connected to my wallbox. If yes, then I am interested in the SOC more often, eg. once per min, because I want to know how fast the car is charging. When the car is on the road or just in the parking garage, it’s enough for me to get an update every 15 minutes. I’m not familiar with the new SDK, are there any events available instead of polling?
Of course you want frequent updates - fully understandable.
The problem is I use for this bidning an unofficial API.Same case for MyBMW. It’s based on the Smartphone App and nobody has his Smartphone MercedesMe App open 24/7 all the day. So updates shall be “unfrequent”. If updates are requested each minute there’s risk to be banned. Believe me I was several times banned during my development because I placed too many requests. Luckily just temporarily.
But Mercedes App is based on Websocket which can be held open for some quite amount of time. So in the next version I’ll keep it open while
charging - live updates during charging time to keep track of SoC
ignition - live updates during driving to keep updates e.g. of GPS coordinates
In this case updates depends on “push messages” from Mercedes site and not on polling of the binding.
Thanks for the reply. That’s very useful to understand.
I am using evcc to control the wallbox and I use these values via rest API there. Is it possible to directly use the token in evcc from Openhab?
I saw that someone has done it for home assistant.
Thanks @weymann. Everything works out for me using OH 3.4.4.
Have one small issue: use dynamic icons for windows states open/closed or lock states. Unfortunately for windows status the coding for open/closed (1=Closed, 2=Open) is vice versa as for the single windows (1=Open, 2=Closed). This leads to the icons as within the attached screenshot.
Understood. At the moment i use the same dynamic icon for all six. If the numbers are fix, i would have to create an extra icon set for the vehicle status.
Hello,
Thanks for making that available so quick!
Unfortunately I still get the old version through the marketplace.
I had upgraded to openhab 4.1.0-SNAPSHOT, then I deinstalled the old binding (Things and Items deleted) and reinstalled. Even clean-cache and reboot does not help, I still get the old UI:
Yes, that’s what I did, too. I was on 4.0 stable and switched to 4.1 snapshot. Also did the openhab-cli clean-cache and rebooted the server.
Update: I replaced the jar with the downloaded jar. Still the same. Tried another browser to be sure it’s not the browser cache. Still the wrong page. Don’t understand what’s happening there
Update 2: switch log level to debug, removed and reinstalled. Now it works. Go figure…
I understand that there might be confusion regarding versions. MercedesMe binding which stopped working end of August is still delivered in the official distribution. Check which version you installed as shown in the below screenshot.
Ensure you don’t installed MercedesMe binding from openHAB Distribution! It is still available in the official distribution and snapshots.
Check if MercedesMe binding is available at Community Marketplace For Snapshot 4.1 I didn’t checked but 3.x and 4.0.x it’s available.
You can check which version is installed via Settings -> Bindings in UI. As you can see in the picture below I dropped the jar into addons folder and the binding is shown in section Other Add-ons
I now get data. And I can actually open sun roof, windows and lock/unlock, which wasn’t possible via the oold binding (API). So that opens a lot of opportunities.
Unfortunately the most interesting (foe me ) data like charging status, battery level and end time are missing. I can see them in the proto_data (B250e plug-in hybrid):
Yes, please send me your complete proto-update as direct message. No personal information or VIN of vehicle is included.
Binding is tested only with my electric vehicle so I’m missing data from
hybrid
combustion
and features like sunroof as you mentioned I’m really surprised that sunroof commands are working without any tests. Great to hear but I still have no mapping values regarding sunroof states
If you can send me the proto.update when it’s opened, lifted or closed will definitelly help to complete the binding!
Addition: Is your Vehicle UID named as mercedesme:hybrid:XXX?
Yes, it’s mercedesme:hybrid:xxx
I can try to figure out the sunroof states.
What is funny: according to the command capabilities, ventilation is not supported for my car but it works anyway. I already realised at many occasions that the mercedes software is far from mature, in particular the assistance systems.
) data like charging status, battery level and end time are missing. I can see them in the proto_data (B250e plug-in hybrid):