Mercedes Me Component

Share your Projects! Custom Integrations
2683

I activated a geofencing zone in the Mercedes app and took a drive, leaving and re-entering the zone, but I don’t see any new sensors in the integration. What should I be looking for? Am I doing something wrong?

2684

Did you reloaded the component after creating the fence in the app? Please check that sensor “geofencing_violation” is created.

Do you see the geofence “violations” in the MB app?

2685

I have published a bugfix release v0.33.1:

:lady_beetle: Fixes

  • Disable automatic component reload every 30min whenever the connection is blocked (China only) - fixes: #387
1 Like
2686

I have published a new release v0.34.0:

:new_button: What’s New

  • Remove car from hub: Added the option to remove a car device from the integration directly through the Home Assistant device page. This is intended for cleaning up old or decommissioned vehicles that are no longer linked to your Mercedes-Benz account. If an active vehicle is removed, it will be automatically re-added on the next reload or restart of Home Assistant. (Fixes: #388)

    image
    image1003×499 19.7 KB

:lady_beetle: Fixes

  • Improved WebSocket reconnection error handling: Previously, unexpected errors during WebSocket reconnection attempts could cause the connection to fail permanently.

:memo: Documentation

  • Updated README with region guidance for Latin America (Mexico, Brazil, etc.) — users should select the “APAC” region.
2 Likes
2687

Unfortunately, I have already had the situation several times where my trunk was open in the morning, probably because someone unknowingly pressed the button on the remote control.
I now wanted to create an automation that alerts me if the tailgate is open for more than 5 minutes, but I can’t find a sensor that I could read for this.
From the vehicle-info-card, I know that such a sensor must exist, because the status of the tailgate is displayed there.
Can someone give me a tip from where I can get the status of the tailgate?

2688

I have created a new binary sensor for this:

 - binary_sensor:
   - default_entity_id: binary_sensor.xxxxxx_trunc_closed
     delay_on: 0:05:00
     name: xxxxxx_trunc_closed
     state: >-
       {{ state_attr('sensor.xxxxxx_lock','decklidstatus') }}

And an alert:

trunc_open:
  name: Trunc is open
  done_message: Trunc is closd
  entity_id: binary_sensor.xxxxxx_trunc_closed
  state: "on"
  repeat: 3600
  can_acknowledge: true
  skip_first: false
  notifiers:
    - mobile_app_xxxxxx
2 Likes
2689

Thank you so much, with this information I was able to create my automation :+1:

2690

I had this situation a lot in the past, and also used a Home Assistant alert to fix this. The more permanent solution was printing a small cover for the trunk button: https://makerworld.com/en/models/861784-mercedes-key-trunk-button-cover

2691

Nice idea.
I just called my Mercedes dealer to have the button reprogrammed from one long press to two short presses, as I saw in a YouTube video. This would probably solve the problem of accidental operation, but they seriously want €250 for the reprogramming. I politely declined and will now look for a friend with a 3D printer who can print it for me. Unfortunately, I don’t have one myself.
If I can’t find a friend, would you sell me 2 of those?

2692

Sure, I can do that. But note that this doesn’t fit all the different key types Mercedes has now. It fit the one on my EQB fine.

2693

Thanks, i have an EQA and will first try to search for a friend, but if I am out of luck I am sending you a mail.

2694

I have published a minor release v0.34.1.

:new_button: What’s New

  • Updated icon set: MB changed the design of their logo last year. The new icons are delivered from the local HA-system now. (HA version >= 2026.3.0 required, older versions will show the “old” logo) (Thanks @Thomas55555)

:lady_beetle: Fixes

  • Improved reconnection error handling: Previously, unexpected server-side errors during re-auth attempts could cause the connection to fail permanently.
  • Translation updates (Thanks @antsund)

Full Changelog: v0.34.0...v0.34.1

2 Likes
2695

Hello,
I got an A Class 2024 (latest Version) and I wonder why there is no PIN option for closing the windows? Because I can’t close my windows without the PIN. I only can open the windows, because there is an PIN option

I think for the windows_move option I also need a PIN Code

PIN
PIN1536×1400 98.6 KB

2696

Windows close should work without a PIN.

Windows move requires a PIN. This is a bug in the frontend. (Update: Fixed. will be part of the next release.)

Workaround:
You can setup the PIN in the options dialog of the config entry - the PIN will be used in all calls:

image
image860×368 16.7 KB

image
image578×750 32.2 KB

2697

Thank you! That works for me now.
I don’t know, but my car doesn’t close the windows without a PIN.Also in your describtion “Sicherheits-PIN, erforderlich wenn nicht in den Einstellungen gespeichert”…So i was thinking this option is required.
But your workaround is much better, so I don’t have put the PIN in all my scripts/automations.

I think my car doesn’t support windows move. I can only open/close all the windows.

2698

Thank you for the excellent work!

I am using the integration to program cheapest charging periods for my C300e, via configuring appropriate charging pauses. I use the service ‘mbapi2020.charging_break_clocktimer_configure’ and it works well for me. However, I have noticed that I cannot input the exact time ‘00:00’ into the service, it gets somehow compiled to ‘24:00’ which then fails when sent to the car. I wonder why this happens…

2699

No idea about the underlying reason, but as a workaround, try using 23:59 and 0:01 for denoting midnight.
You would not be the only one with this problem.

2700

Good evening, I tried to setup an automation to set the pre-Climate on a certain time based on some conditions. For testing purpose I did some time ago setup a automation, which just triggers one action (and it did work at this point in time, which maybe is a year ago):

        - action: mbapi2020.preheat_start_departure_time
          metadata: {}
          data:
            time: 390
            vin: XXXXXXXXXX

Now I recognized, that this doesn’t work anymore. I tried to trace the problem, but I’m stuck. The integration itself works and I can send commands to the API (e.g. if I press “Preclimate start” the heating starts immediately). Any idea, how I can identify the issue better?

2701

Hey @heikoHA ,

enable debug mode of the integration (docs) and share the logs. Share some details about your car type…

2702

Yes, I’m doing exactly that. Just feels a bit awkward.