[APP][Pro] Mercedes-Benz - Stay connected to your Mercedes-Benz, wherever you are

Apps
, ,
128

I have run a couple more tests and fixed it in this version Mercedes-Benz | Homey

129

Hey. It work for me, but it seem like the continues refresh are failing. @Stian_Sorbotten could you please confirm my findings as well?

130

Is there a way to close the panoramic roof blind too when closing the panoramic roof?

131

Hey @Wouter

Maybe let me investigate it. Do you have the options to create a GitHub issue? Issues ¡ andersdissing/Mercedes-Benz-homey-app ¡ GitHub

132

Doors, ignition avd perhaps something more still days 6 days.

Engine running days 2 days, but i used the car today. I am not quite sure what the time here mean. Last time the device changed state?

133

I found a bug where the underlying (WebSocket) connection is not handled properly. This is fixed in 1.1.37: Mercedes-Benz | Homey

I have tested “sync” or device refresh this morning, and the connection is now reliable.

134

Thank you.

Everything work perfect again :grinning_face:

135

Super. I will move that version to production.

@Wouter, did you manage to create a GitHub issue? Otherwise, please email me at ameq@ameq.dk. We need to work out what you are after, and this forum is not my preferred way of aligning on requirements.

136

Mercedes-Benz app v1.1.41 — test version out, feedback welcome

Install it here: Mercedes-Benz | Homey

What’s fixed

  • Homey capabilities such as battery level could go several days without updating. They now follow what the car is actually doing.
  • A flow could report that a command worked when the car never carried it out.

There’s a new flow card, **Vehicle command failed**, that tells you when that happens and what went wrong.

Please help me test

  • Keep an eye on the values Homey shows for your car over a few days - battery level, range, doors, windows, odometer, tyre pressure. Do any of them stop updating or drift away from what the car really shows? If so, which ones, and roughly how long were they stuck?
  • Does the charging state match your car — plugged in, unplugged, and while actually charging?
  • Add the Vehicle command failed card to a flow and let it run for a few days. Does it ever appear? If it does, what did it say?
  • Anything else in the dashboard widget that doesn’t match your car.

Thanks! If something looks wrong, a diagnostic report helps me a lot more than a description on its own.

137

I got an error report this morning. That includes a bug I have not tested for, in essence. The user ended up in a “429 loop” that froze everything. I have published a new test version (1.1.43) that fixes this by backing off until the Mercedes-Benz backend APIs are available. So when installing the new version, it will take an hour or two for the app to start working normally again.

Get the newest test version here: Mercedes-Benz | Homey

138

Version 1.1.43 is now live :crossed_fingers: This version has fixed the non-updated capabilities.

139

Sorry, I haven’t had time to create a github issue.

I’m getting 429 issues though. I drove the car this afternoon and then again half an hour ago. The app still shows the data from 5 hours ago and as soon as I try to do something with a flow, for example close the roof, I get a 429 error. I’ve been on 1.1.43 since yesterday evening. I’m using a dedicated Homey user.

140

Hey @Wouter. Please deactivate the app for a couple of hours then enable the app again.

141

Version 1.1.44 is live, with additional guardrails to prevent a 429 loop. However, this means that for now, the speed of updating the various capabilities has been reduced.

Note. I got a timeout message after installing the new version, even though I had run the same version in testing over the weekend. My solution was to restart my Homey. However, I think that the disable/enable app should be enough if you experience a 429 error.