Mercedes Me

[maihacke (Simon Spielmann)]

No update/reply?

[weymann (Bernd Weymann)]

@maihacke

My main problem is still that all values are updated only by refresh cycle (and 1 min afterwards → websocket). I understand that this is caused, by API limitation from what I see subscribing to the kafka topics would not be free.
Nevertheless for my use case it would be enough if there would be a way to trigger the updates via OH rules, so I could check the car status whenever my wallbox reports a change. Is this possible?

I see, Pull Request to solve the current problem took longer than I thought due to full cleanup and side effects.

Problem
Regarding your use case I already thought about this. Currently binding keeps websocket open during charging and driving but until it recognize this the refreshInterval is the limiting part - there’s no push from Mercedes side.

So push needs to be raised somewhere else, as you said a wallbox change. From my side I’ve a plugged notification from my wallbox. This shall trigger a wakeup towards the vehicle.

Technical concern
I agrree that this is a sound handling:

• Wakeup on wallbox trigger - immediate feedback.
• Sleep after charging ends

Sadly (some ) OEMs do their best on making life hard for the smarthome community. Authorization gets harder, long lasting HTTP 429 timeouts. So if you’re handling the wakeup triggers wrong I can literally feel the 429 complains!

Proposal
I’ll prepare a version with a new wakeup action. Readme will state to use it carefully! I’ll distribute via Marketplace and gain some test results, ok?

[maihacke (Simon Spielmann)]

Thank you very much @weymann for your answer and for putting effort into this.

A wakeup action would be great. My wallbox also triggers if the car is plugged in so I could call the wakeup action then. I currently I have it implemented in such way that the bridge thing is restarted when the cable is plugged, which is a bit ugly.

[weymann (Bernd Weymann)]

@maihacke

I currently I have it implemented in such way that the bridge thing is restarted when the cable is plugged, which is a bit ugly.

Users find always a way to force OH to do what they want

Marketplace jar in top post is updated. See readme with new introduced action forceUpdate.

The happy use case

• rule checks for change wallbox charging. Not plugged, unplugged, … whatever
• call rule action forceUpdate
• mercedesme binding will recognize vehicle is charging and updates stay active
• after charging ends normal refreshInterval takes place again

Manual test of action can be triggered via UI in things section:

[maihacke (Simon Spielmann)]

I downloaded the new version and modified my rules accordingly. First smoke test looked good. I will report here any updates. Thank you very much for your help.

[Spaceman_Spiff (Sebastian)]

@weymann

Marketplace jar in top post is updated. See readme with new introduced action forceUpdate.

Would it be possible to describe refreshInterval better in the docs? What does it do exactly?
Is it a strict poll interval or is it the interval which attempts to start a websocket connection which then can receives automatic updates when the vehicle is active (charging/driving?