Mercedes Me Component

Update:
This morning, sensors and commands are not working on the integration, app works.

Only error I could see was:
ERROR (MainThread) [custom_components.mbapi2020.websocket] remote websocket connection closed: Cannot write to closing transport

The carsensor Last message received was 04:19:37 this morning.

Thx, my main account is working again. Could you reload the component (or restart HA)?

Restarted HA, works again.

1 Like

I have lost the connection too, but it did not help to restart Hass. I tried to update from HACS as well, the version info is v0.19.1. Is that the latest version, and is there anything else I could try? I don’t see anything in the logs except for the standard warning about using a custom integration. :grimacing:

Edit: Never mind, it suddenly came back, without me doing anything. :grin:

@ReneNulschDE: I have not received any updated GPS data via the device_tracker since 14.Nov.

{{ state_attr('device_tracker.eqa_device_tracker','latitude') }}
{{ state_attr('device_tracker.eqa_device_tracker','longitude') }}

At this point (approx.), the MB Fahrtenbuch Service (incl. iOS app) also expired and I had not extended it. Could there be a relation or any other reason?

@dirkcx: Check if the Digital Services License for Remote Services has expired. (is included for the first three years normally)

Same for me.

Please try to reload the component. I had multiple errors in the last days, where the MB Servers blocked the connection. (Maybe in relation to a change rolled out on Monday/Tuesdays - MB disconnects the websocket after 15min now - was 2-4 hours before…)

Error was: HTTP429 - Too many requests (per account - main account was blocked, dev account worked fine)

@ReneNulschDE (Mercedes Me Component - #2165 by ReneNulschDE)
Indeed, “Geobasierte Online-Informationen für Fahrfunktionen” and “Individuelle Verbrauchsanzeige” were set inactive. I do not know, if they have been in an inactive state before, but I activated them now. Especially that they are part of the “Sicherheit und Service” package, for which I already have payed for the full 3 years.
And, after reactivating both Services, I get the GPS data again as expected. It’s pretty cheeky when services are simply deactivated, even though they are part of a paid package. Thanks for your hint!

1 Like

Hi,

Sorry if this is a silly question, been a while since I’ve used HA.

I’ve installed this integration via HACS, restarted my HA instance and browser… but at which point do I get prompted to login? Or where exactly should I configure my credentials?

  • Use the “Add Integration” in Home Assistant, Settings, Devices & Services and select “MercedesME 2020”.
  • ???
  • Use your MB-login email address. Your will receive a 6-digit code via email (valid for 15min)

EDIT: Nvmmmmm, found it. I still had to click “Add integration” once it got installed via HACS

Go to: Home Assistant, Settings, Devices & Services
Click on the plus sign in the lower right corner.
Search for mbapi2020

In case you can’t find the integration, refresh your browser window

1 Like

Got things working. Thank you, amazing work both you and @VietNgoc ! :heart_eyes:

Hi,
First of all, thank you very much for this great integration.
With my EQV I cannot start the preclimate (Vorklimatisierung) in HA.
The current status is displayed correctly in HA, but when you start the air conditioning in HA, the button switches back after a few seconds and the vehicle does not receive the command.
Any idea what I can set differently?

Try to use the service (I think it’s now called “Action”) from the Developer tools directly: mbapi2020.preheat_start.
If it doesn’t work, try mbapi2020.auxheat_start.

Thanks for the quick reply.
I have already tested three options (Preclimate start, auxhead and Vorklimatisierung). Unfortunately, the preclimate does not start.

an EQV does not have a auxheater. So please start again the service preclimate_start (this is the same like the switch “Vorklimatisierung”). Then check the sensor “car” - this one has some attributes with the result of the last service call or enable the debug logging and check the homeassistant log.


According to the protocol, the preclimate starts, but end itself after a minute. And in reality, it doesn’t start at all.

Please enable the debug log:

start the service,
wait 30 seconds,
stop the debug logging.
A textfile is downloaded.
Send this file and a diagnostic report to [email protected]

and, please check if this is working in your official MB app.

Hi,

my MercedesMe app still thinks the car is at work (I’ve definitively driven the car home earlier).
Needless to say, the Mercedes integration failed to set up.

Anyone else have the same outage? Is Mercedes fiddling with the API?