Mercedes Me Component

ReneNulschDE · September 1, 2025, 10:00pm

Looking for New Maintainer(s)

Hi everyone,

This is not an easy message for me to write and I wrote it multiple times without saving already… but its the time now - After more than 8 years of developing and maintaining the various Mercedes-Benz/Smart integrations for Home Assistant / EVCC, it’s time for me to step back.
I released the first version of the integration with Home Assistant 0.63 (February 2018) and since then I’ve seen many improvements, faced challenges on the Mercedes side as well as within Home Assistant, and learned a lot along the way.

Now I’m facing an important decision: I’m selling my last Mercedes and will no longer be able to meaningfully develop or test the integration. I also need to shift focus to new priorities like the usual life and business…

Current Status

The integration is more or less stable and actively used by 4,600+ Home Assistant installations.

What I’m Looking For

I’d like to hand over responsibility to one or more new maintainers who bring:

A Mercedes-Benz vehicle (for testing!)
Python/Home Assistant development experience
Time and motivation for regular maintenance
GitHub/Git knowledge
Commitment to long-term support

What I Offer

Full onboarding and knowledge transfer
A gradual handover of responsibilities
Support during the transition period
Transfer of all repository rights

Timeline

I’ll be on vacation for the next 6 weeks (until mid-October). After that, I’d like to approach the transition in a structured way:

October 2025: Introductory calls/emails and onboarding
November–December: Collaborative work on issues/features
January 2026: Full handover
Q1 2026: Backup support if needed

Important note: For those who have kindly shared access to their vehicles for testing – please rest assured that your data will not be passed on to any new maintainer.

Without a Successor?

If no maintainer is found, I would deprecate the integration after a 6-month notice period. That would be unfortunate, but better than leaving it unmaintained.

Interested?

If you’d like to take over, please reach out by mid-October via direct message or mail: [email protected]

It would be helpful if you could include:

Your development experience
How you’d like to collaborate

Thank you for all the support over the years! This community has been fantastic, and I hope the integration will continue to help Mercedes drivers integrate their vehicles smartly into Home Assistant.

firstcolle · September 2, 2025, 4:47pm

I feel really sad after reading your message.
The truth is, I don’t have the experience and I’m just not able to handle this job, even if I’d really love

AlexMPH · September 3, 2025, 4:45am

Very sad but understandable, thank you for everything!
sadly, I have 0 coding skills, but I hope the right person pops up here!

Have you considered asking the home assistant dev team to absorb?

alexr544 · September 8, 2025, 2:20am

By chance does anyone know why i keep getting this error? I have tried to log in to me.mercedes using incognito mode. But there is nothing for me to accept. Truly.

ReneNulschDE · September 8, 2025, 6:50am

Please try it on the German website www.mercedes-Benz.de and login with your US account

alexr544 · September 8, 2025, 12:43pm

It eventually started working last night. I think they were having issues yesterday with their websites (Mercedes).

Thomas01 · September 10, 2025, 7:24pm

Hi @VietNgoc ,

are you aware of this issue with ApexCharts card:
https://github.com/RomRider/apexcharts-card/issues/945#issuecomment-3211936301

I can confirm that I have the issue (Core 2025.9.1 and Vehicle Info Card v1.11.0) as well, removing the Vehicle Info Card does have the ApexCharts card working again.

VietNgoc · September 11, 2025, 5:51pm

Hi @Thomas01 I recently changed my fleet My wife is still waiting for a new car and I no longer have access to any MB accounts.

I’ve released a beta version of this fix, could you please test it? v1.11.3-0

Thomas01 · September 11, 2025, 6:45pm

Workes on my end.

And sorry for your change of fleet.

VietNgoc · September 11, 2025, 11:44pm

Great, I’ll prepare a release for this fix… I’ve wanted to try a different car brand for a long time, so the MB had to go… but another one is coming, so I’ll keep updating the card as long as possible.

Patch · September 15, 2025, 11:43am

I was wondering if it is possible in the HA integration to access and set the maximum charge level you see in the Mercedes Me app?

Thomas01 · September 15, 2025, 12:42pm

Yes.
Setting: Action mbapi2020.battery_max_soc_configure
Reading: State sensor.XXX_max_state_of_charge

Example (my) implementation:

template:
  number:
  - name: "EQS Maximum Charge"
    unique_id: aa52703f-1194-4a49-a8c7-d59fee70508f
    state: "{{ states('sensor.XXX_max_state_of_charge')|int(0) }}"
    icon: >
      mdi:battery-charging-{{ states('sensor.XXX_max_state_of_charge')|int(0) }}
    unit_of_measurement: "%"
    min: 0
    max: 100
    step: 10
    set_value:
      action: mbapi2020.battery_max_soc_configure
      data:
        max_soc: "{{ [value|int(0), 50] | max }}"
        vin: "{{ state_attr('sensor.XXX_car', 'vin') }}"
        charge_program: "{{ state_attr('sensor.XXX_max_state_of_charge', 'selectedChargeProgram') }}"

With that you can use the number as a slider in the frontend. Displays the values, and lets you change the value of the current charge program.

janvda · September 29, 2025, 3:41pm

I can edit the Action for the Template number as specified above but when clicking on Submit it didn’t save it:

So before clicking on submit I see:

ReneNulschDE · October 2, 2025, 7:39am

Is there a driver of a new CLA 2025 here who would register me as a secondary driver? If yes, please send a email to [email protected] and we can discuss it offline. Background: There are some new functions/data that need to be implemented and I would like to test.

ReneNulschDE · October 9, 2025, 10:07pm

I’m back from vacation and spend some hours to better support the new CLA 2025 Models. Special thanks to Benjamin for sharing the access to his new CLA.

What’s New in v0.30.0

- New binary sensor "Charging active" (click for more details)

Cars: All hybrid/electric car types

Type: Boolean

Values: Charging, Not charging

Device class: BinarySensorDeviceClass.BATTERY_CHARGING

- New sensor "Charge Flap" (click for more details)

Cars: CLA 2025 and newer

Values:

open
closed
pressed
unknown

- New sensor "Charge Inlet Coupler" (click for more details)

Cars: CLA 2025 and newer

Values:

plugged
vehicle plugged
vehicle not plugged
defect
unknown

- New sensor "Charge Inlet Lock" (click for more details)

Cars: CLA 2025 and newer

Values:

unlocked
locked
state not clear
state not available
unknown

Breaking Change

The type of sensor “End of charge” was changed to Timestamp to support the new CLA 2025 cars too. This affects the attribute “Endofchargetime” of the “Range Electric”-Sensor too.

Note: For CLA2025 the value is not reseted by the MB-API sometimes and the sensor will show a timestamp even that the charging was stopped. Something that needs some special handling in a future release.

Fixes

None

China is still not available. I have no access to a car in China and can’t test the needed changes.

ReneNulschDE · October 19, 2025, 6:51am

I have published a small bug fix release v0.30.1…

Fixes

“End of charge” broken for some old models (fix: #377)
Improved input validation for email addresses (fix: #375)

GeertC · October 21, 2025, 10:26pm

Looking nice, could you share the images again?

rofspark · October 23, 2025, 2:19am

Sure. See if you can download them here.

kkapchin · November 12, 2025, 7:00am

Hi René,

Since this morning (around 07:00 EET / 05:00 UTC), the integration started failing with continuous 429 (Too Many Requests) errors on the WebSocket endpoint:
WSS Connection blocked: 429, message=‘Invalid response status’,
url=‘wss://websocket.emea-prod.mobilesdk.mercedes-benz.com/v2/ws’
The retry delay keeps increasing (160s, 250s, 360s, 490s, 640s, etc.), and no data or commands are passing through anymore.

After that, every lock/unlock attempt fails with the following error:

Failed to perform the action lock/unlock. ‘NoneType’ object has no attribute ‘send_bytes’
Traceback (most recent call last):
File “/config/custom_components/mbapi2020/websocket.py”, line 251, in call
await self._connection.send_bytes(message)
AttributeError: ‘NoneType’ object has no attribute ‘send_bytes’

It looks like the WebSocket connection never reinitializes properly after receiving 429 from the server.
The issue appeared suddenly today — it was working fine yesterday without any configuration changes.

Setup details:
• Integration: MercedesME 2020 (latest HACS release)
• Home Assistant OS running on HA Green
• Region: EMEA (Bulgaria)
• VIN: WDD2052141F806082 (C-Class W205 Facelift)
• Remote lock/unlock commands enabled and active in Mercedes Me app
• Started failing around 07:00 Bulgarian time

What I tried so far:
• Restarted Home Assistant
• Signed out/in from Mercedes Me app
• Reauthenticated integration
• Same behavior persists

Could this be a new rate-limit or WebSocket policy change on the Mercedes servers that’s not being handled gracefully by the component?
If you need more debug logs, I can enable full logging and share them.

Thanks a lot for your great work on this integration,
Konstantin Kapchin

ReneNulschDE · November 12, 2025, 7:20am

MB has changed a setting in the Auth-Flow. You can see an additional step in the auth-flow when you logout/login in the official app. (They want you to approve non-existing documents)

I’m on it… See ERROR - Relogin after 429 failed: Acceptance of legal terms is required. · Issue #379 · ReneNulschDE/mbapi2020 · GitHub for progress updates…