Hi Rene, there have been a lot of changes to the frontend. I know the card has quite a few bugs because of that. I have a lot of fixes in the works and am working on a complete rewrite of the code, similar to what I did for vehicle-status-card.
I’ll take a look at it, but it’ll take a while, since I’m expecting another addition to the family any day now. 
I sense a HomeAssistant baby rocker project as being of higher importance to give you quiet time during your scheduled hours of minding the newborn to be able to maintain your Mercedes integration changes.
So, I’ve currently tested with Version v0.37.0-beta.2. With custom cards, I only encountered a problem with the previously mentioned change, where attribute values are converted from string/boolean to int. If in the offic release will includes only these changes, it won’t be a problem to update the card, to make it compatible.
It appears that the changes so far only affect attributes, not entity state? see below. For the lock sensor the raw state, it’s still the string “2" so, in the card it render correct translated value.
sensor.*_lock
state:
translated: Locked
raw: "2"
last_changed: "2026-06-30T20:02:14.975Z"
last_updated: "2026-06-30T20:02:14.975Z"
attributes:
retrievalstatus: VALID
timestamp: "2026-06-30T17:05:16"
decklidstatus: 0
doorStatusOverall: 1
doorlockstatusdecklid: 0
doorlockstatusfrontleft: 0
doorlockstatusfrontright: 0
doorlockstatusgas: 1
doorlockstatusrearleft: 0
doorlockstatusrearright: 0
doorlockstatusvehicle: 2
doorstatusfrontleft: 0
doorstatusfrontright: 0
doorstatusrearleft: 0
doorstatusrearright: 0
icon: mdi:car-key
I have published release to address the login problems for a limited set of people. Looks like MB is testing some new login methods like passkeys. The release had limited test cycle.
Specials thanks to @phedoreanu for the login fix and the other people how supported this release… the first one that I could create just on my mobile. (I‘m traveling without a laptop on hand.)
Most important Bug Fix
disablePasskeyDemo), and retry transient gateway errors (502/503/504) with backoff. Fixes #418. (Thanks to @phedoreanu )
Breaking Changesvehicle_status_updates (VSU) message type, several sensor/binary_sensor attributes are delivered as integers rather than strings. For example, doorlockstatusvehicle now reports 2 instead of "2". Templates that compare against quoted values need to be updated:# before
is_state_attr('sensor.XXX_lock', 'doorlockstatusvehicle', '2')
# after
is_state_attr('sensor.XXX_lock', 'doorlockstatusvehicle', 2)
New Featuresvehicle_status_updates (VSU). Adds handling for Mercedes-Benz’s VSU stream, including new enum/helper modules (vsu_enums.py, vsu_helper.py) and extended protobuf diagnostics (proto_diag.py). Bug Fixesunknown/unavailable after an unlock. VSU maps DOORLOCKSTATUSVEHICLE_UNLOCKED to the integer 0, which the previous truthiness check treated as missing data.disablePasskeyDemo), and retry transient gateway errors (502/503/504) with backoff. Fixes #418.CancelledError suppression bug in the cleanup task (#411).proto_diag logging from info to debug to reduce log noise.
Translationschargeflapstate sensor states and fix a language mix (#396, #415).Full Changelog: Comparing v0.36.0...v0.38.0 · ReneNulschDE/mbapi2020 · GitHub
Compatibility Update for the New Version of Integration.
Full Changelog: Comparing v1.11.0...v1.12.1 · ngocjohn/vehicle-info-card · GitHub
Hi, I recently got a new car and integrated it with Home Assistant. I’m wondering why there are both buttons and a switch for “Preclimate.” Is there a reason for this?
Hello everyone,
If you’re interested in integrating EVBox with Home Assistant, you can find the solution here: Home Assistant | evcc - smart charging
There’s no reason other than that the component has been around for a few years now, and certain features were added to Home Assistant over time → First there were services (today: actions), later switches, and then buttons… If you search through this thread, you’ll surely find the reason why the buttons or switches were added — I can’t remember anymore…
I have published an update v0.38.1:
New Features Bug Fixes
mbapi2020.temperature_configure is working again (fixes #421)Full Changelog: v0.38.0…v0.38.1
Known Issue: Connection to MB-Servers fails with SSL certificate error (since July 23, 2026)Affected: All users of this integration, all regions using *.*-prod.mobilesdk.mercedes-benz.com
Symptom: The integration cannot connect and Home Assistant logs show:
Could not connect: Cannot connect to host *.*-prod.mobilesdk.mercedes-benz.com:443 ssl:True[SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed:unable to get local issuer certificate (_ssl.c:1082)')], retry in 20 seconds...
On July 23, 2026 (~04:00 UTC), Mercedes-Benz rotated the TLS certificate of their Web endpoint. The new certificate uses Let’s Encrypt’s new “Generation Y” certificate hierarchy (intermediate “YR2” → root “ISRG Root YR”).
certifi does NOT fix it. Even the latest certifi release (2026.07.22) does not contain the new root yet.I am currently testing a fix that ships the official Let’s Encrypt cross-sign certificate with the integration and adds it to the verification context — this keeps full certificate verification intact and works regardless of when Mercedes fixes their server chain or when trust stores add the new root. A release will follow as soon as testing is complete.
Update: 2026-07-23 09:25 - Version v0.38.2 released…
Update: 2026-07-23 11:10 - MB has solved the problems on the server side. Update not needed anymore. But reloading of the integration makes sense.
Hey, great component!
I had a question, is there a way to trigger a beep similar to how the car beeps when you lock it using the FOB? I see there is a sigpos_start in the documentation but that only triggers the light? Not the horn?
Thanks!
I would like this too, but I doubt that such an option would be possible through official channels.
L Blinker followed by R Blinker?
Are they exposed?
No, just the lights. ( The horn is exposed in the API but in all cars that I have seen so far, it is not allowed to use)
And I love it, there are only few things on this planet (like war and hunger) that I hate more then the horn in the cars…
Ah okay. I was trying to see if I can get the car to do the acoustic sound after locking the same way you get it when you lock the car from the key fob.
Sorry, no chance - In case you are a nerd 
you could put a connected box in your car and use a HA automation to play the sound (and no, I’m not such a nerd)
Nothing wrong with a relay across the horn contacts connected to a spare GPIO port onboard to toggle the horn if you cannot get the existing ‘flash light’ automation to work. Do the same for your hazard switch on another GPIO port. You may find that is the method third-party car alarms interface to the vehicle wiring.
Another question, is the remote engine start functionality subject to the same conditions like the minimum 20% fuel that the official Mercedes app does?
I can’t test it but it looks like that is checked on the MB-Backend side. The expected command error codes are 6807 (FuelLow) and 6818 (FuelTankTooLow).
May I please ask where did you get those error codes (6807, 6818) from? I don’t see them in your repository.