2023 Mercedes-Benz EQE 500

I was in bumper-to-bumper traffic traveling West on Interstate 376 in Pittsburgh, PA. The weather was clear and cool, and the pavement where I was driving was dry. I was proceeding through the Fort Pitt tunnel outbound. Given that traffic was stop and go and moving very slowly, I switched my recouperation setting from “normal” to “strong” to enable one-pedal driving using the paddles on the sides of the steering wheel. Immediately after doing so, traffic was inching forward just West of the Fort Pitt tunnel, starting up Greentree Hill. I saw the truck in front of me starting to move forward so I took my foot off my brake (up to that point it had functioned correctly) and the car started moving forward slowly. When the brake lights of the truck in front of me illuminated, I placed my foot on my brake. The brake pedal depressed but the car brakes did not function. I immediately noted that the brakes had not functioned and as a result I pressed harder with my foot on the brake pedal. Nothing happened–the brakes did not function. I then used both feet and pressed as hard as I could against the brake pedal. Again, nothing happened–the brakes did not function. I continued to press as hard as I could with two feet as the car proceeded forward into the back bumper of the truck in front of me. The collision occurred at approximately two miles per hour and the damage to my car was mainly caused by the rear hitch on the truck, which went into my front bumper. Mercedes-Benz USA has inspected the car and stated it did not malfunction, but they did not perform any tests in a manner to recreate the settings of the car that were in place at the time of the incident. The car is currently in their control and that of my dealer. No warning lamps or other symptoms of the problem appeared prior to or during this incident.

NHTSA ID

11671437

Incident

Apr 8, 2025

The contact owns a 2023 Mercedes- Benz EQE 500 equipped with Pirelli Tires, Tire Line: P-Zero All Season, Tire Size: 255/40/R20, and DOT Number: 1931H811J. The contact stated while driving at an undisclosed speed over a bump, the tires had either experienced a blow out or blisters. The contact stated that the failure had occurred on all four original tires and had recurred on several of the same replacement tires. The cause of the failures were not determined. The manufacturer and local dealer were notified of the failure, but no assistance was offered. The vehicle failure mileage was approximately 5,000. The tires failure mileage was approximately 5,000.

NHTSA ID

11666566

Incident

Mar 5, 2024

Mileage

5,000 mi

At 0820 AM on Monday, 23 SEP 24 while traveling South on interstate 95/495 in rush hour traffic the vehicle lost complete power and 3-4 messages appeared in the display. I recall one saying the rear differential is inoperable. I turned on the emergency flashers and was fortunate to allow the car to coast to the highway’s left shoulder without causing an accident. I don’t remember the other warnings as I was preoccupied trying to get the car safely off the highway. I was able to restart the vehicle after allowing it to sit for a minute or two. I have an appointment to have it inspected on Thursday at Mercedes of Annapolis, MD. This is the second time the vehicle has lost power while traveling on the beltway. A recall was eventually issued a few weeks after the first incident. I convinced my wife to purchase this vehicle to replace her 20 year old car thinking it would provide safe, reliable transportation. To the contrary the car has had to be towed twice, has lost power on the highway and was in the shop almost a month for a noise complaint. I was told the noise issue was due to 3 bad tires, likely due to potholes, and charged $1741 to replace them. I am totally convinced the issue was not related to potholes but had no recourse other than to pay the $1741. My wife feels totally unsafe driving the car, particularly when I am out of town for work.

NHTSA ID

11616107

Incident

Sep 23, 2024

The contact owns a 2023 Mercedes-Benz EQE500. The contact stated that while driving approximately 45 MPH, the vehicle lost propulsion and stalled. Moments later, the contact was able to restart the vehicle and continued driving. The next day the vehicle was driven to the local dealer who determined that the failure was related to NHTSA Campaign Number: 24V372000 (Electrical System); but the part to do the recall repair was not yet available. The vehicle was not repaired. The manufacturer was notified of the failure. The failure mileage was 2,500.

NHTSA ID

11592597

Incident

Jun 3, 2024

Mileage

2,500 mi

There have been 3 instances of the same incident of the Automatic Emergency Breaking system failing, the 3 times has happened over the 8 months I have owned the car. Mercedes has aknowledged the failure of the automatic breaking system but they do not have any fixes for it. When I am driving, if the safety system senses a police radar system a car may have installed (like an old school one on a civilian's car dashboard) the car's security system "shuts down" for a couple seconds and slams on the breaks nearly causing a crash. I have been driving at 15-20 MPH on a clear street and out of nowhere the car slams on the breaks because it detects someone's radar detector. As you can imagine, this is absolutley terrifying to be driving on a clear street and have the car slam on it's breaks. My heart rate goes up, I have been visibly shaken up. The feeling is as if I got into a car accident-but I didn't it was self-induced by the vehicle. I am worried if someone is driving behind me and is not prepared for the car to break, I will be rear-ended. Please help Mercedes owners fix this, it's horrible.

NHTSA ID

11584340

Incident

Dec 20, 2023

On [XXX] my wife was driving to a place of business here in Las Vegas, NV at approximately [XXX]. She proceeded to pull into a parking spot with her foot on the brake pulling up to the parking block. She never took her foot off the brake preparing to stop once she reached the parking block. Once she reached the parking block she applied the brakes firmly to bring the car to a stop, however, the car took off at a high rate of speed. The car then jumped over the parking block onto the sidewalk my wife continued to apply the brakes but they did not work the car tires kept spinning and eventually caused her to hit the wall of the building. At the time of the incident no warning lights came on the dash because everything went blank, no airbag deployed, no messages came on the car nor did it send any messages to me alerting me that my vehicle was involved in a accident. Due to this vehicle malfunctioning my wife has suffered a concussion, bruises to her breast and chest area and she also has a strain to her hips due to the seat belt malfunction. The seatbelt did not work properly it did not keep her restrained to the seat as designed. The building was of course damaged as a result of this vehicle malfunction. My wife unfortunately has suffered mental and bodily issues she has been traumatized due to this vehicle malfunction she has voiced over and over how this experience has affected her she also has repeatedly stated how this event took place and how it now makes her not ever want to ride in this car or any other electric car ever again. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

NHTSA ID

11579164

Incident

Mar 12, 2024

On 01/12/2024 the driver profile on my vehicle was remotely wiped with no authorization. This profile has settings for multiple automated driver functions including a creep function that I have always left off (On is the default). Once the driver profile was wiped, when I lifted my foot off the accelerator expecting the vehicle to come to a stop it did not. It continued traveling forward without any accelerator input.

NHTSA ID

11570356

Incident

Jan 12, 2024

Electrical interference with USB audio. There are loose connections that travel on the headliner all the way to the back of the car rear top speakers. Audio source suddenly gets disconnected and make a huge buzzing sound on the rear left speaker mounted to headliner. A potential fire hazard.

NHTSA ID

11536718

Incident

Aug 5, 2023

Complaint During part of the steering movement, it feels heavier or more difficult to steer in the same spot every time. OR Rattling, humming, dry sliding/gravel noise from the electric steering system when steering (see attachment). Complaint does not impact the ability to safely steer or control the vehicle. Cause Ball screw drive (KGT) of electric steering damaged by: 1. External force due to: ‑ Hitting the curb/posts with the front wheels. ‑ Driving over obstacles (e.g. pothole/ threshold/ speed bump/ gully) at an inappropriate speed. 2. Corrosion/ water ingress through a damaged boot (see attachment). ‑ Cracks (1) ‑ High pressure cleaner (2) ‑ Animal bite (3) See various examples listed in the attachments for examples of outside influence. Remedy Remove boot clamps closest to steering gear housing on both left and right (as seen in "Steering Rack Boot Clamp Location"). Pull back boot and inspect for rust, broken end stops, water, or any other anomalies. Replace electric steering. Note: Steering gears replaced due to outside influence or damage must not be claimed under warranty!

Complaint Tailgate opens unintentionally. Cause Accidental or unnoticed activation of the button to open the tailgate on the vehicle key. EXAMPLE: when stored in trouser pocket, handbag etc. Remedy As of the 6th generation, the vehicle key can be recoded so that the tailgate no longer opens as a result of a long press on the button, but by double‑clicking on the button instead. This reduces the likelihood of the button being activated accidentally or unintentionally. The recoding can be carried out as follows: 1. Add SA Code O19 into VeDoc (O for Oscar, not "zero") • an XSS ticket may be necessary to add the SA code 2. Perform SCN coding of EIS N73 control unit 3. Deactivate the vehicle key (a successful deactivation is indicated by the LED lighting up 2x briefly and then 1x for a long period). 4. Place the vehicle key in the storage compartment on the key symbol and turn on the ignition. IMPORTANT: all other vehicle keys must be outside the recognition range of the vehicle when doing this! Perform steps 3 and 4 successively for all vehicle keys. Notes: 6th, 7th and 8th generation keys can be deactivated as follows: Up to modification year 22/1 by double clicking the "Lock button" As of modification year 22/1, by press and holding the “Lock button", then double‑click the “Unlock button" at the same time. On model series 167, the storage compartment with the key symbol is located in the armrest. The SCN coding from the EZS is only transferred correctly to the vehicle key under the following conditions: Only one vehicle key is located in the vehicle, this key has been deactivated and it is positioned on the marking in the storage compartment for the data transfer. The costs for this adaptation are to be borne by the customer. For the newer BR 174, 178, 244, 248, 520, and 540, a software update must be initiated, as there is no way to perform SCN coding.

Complaint Traffic sign symbol for "Traffic Sign Assist" is blinking in instrument cluster without obvious cause usually with one of the following scenarios: • Flashing without a speed limit ("‑ ‑"). • Flashing when current vehicle speed is under speed limit. • Flashing between US speed limit symbol and European speed limit symbol. NOTE: • Verify that the concern falls under one of the attachment videos. If not, then it is outside of the scope of this LI. • This also does not cover "Traffic Sign Inoperative" messages on the instrument cluster. Cause There are two identified reasons for this concern: 1. Country code information stored incorrectly at a particular geographic latitude range. 2. Incorrect reference data when the vehicle is started and a GPS signal is not immediately available. Remedy Update head unit software to latest version and the re‑check function in the same location. If vehicle is still exhibiting one of the symptoms as described exactly as in the complaint section or as shown in the video attachments, open a TIPS case to the Body/Chassis/Entertainment inbox with the following: • Video of the concern. • Exact location (latitude and longitude is best)

Complaint The following most common complaints may be observed: • Brief connectivity interruptions when using Apple CarPlay over Wi-Fi • Audio cuts out • Device not recognized • No operation possible Cause There are multiple possible causes for an iPhone disconnecting from a vehicle’s head unit while using Apple CarPlay. These include hardware, software, and environmental factors: Environmental Interference External Sources: • Passing under toll bridges, driving near airports, or areas with heavy electronic interference (e.g., as described in LI82.85-P-076157) can cause connection drops. Cellular Networks: • Interference from nearby cell towers operating on similar frequencies (usually 2.4GHz or 5GHz) can disrupt the signal. Storage Location: • Keeping your phone in a handbag or surrounded by other objects inside the vehicle can create physical or electronic interference. Device and Software Issues Head Unit Software/Hardware: • Outdated firmware, bugs, or hardware faults in the vehicle’s head unit can prevent a stable connection. iPhone Software/Hardware: • Similar issues in the iPhone, including buggy iOS updates or hardware problems, may affect performance. Reset or Reboot:• Automatic rebooting or resetting of either the head unit or the iPhone will temporarily disrupt CarPlay. Connection and Settings Wired Connections: • Faulty Cable: A damaged or poor-quality USB cable can cause intermittent or total loss of connection. • USB Port Issues: Dust, debris, or physical damage in the USB port of either the head unit or the iPhone can also lead to disconnects. Wireless Connections: • Intermittent Bluetooth/Wi-Fi: Unstable wireless communication (Bluetooth/Wi-Fi) can frequently break the Car- Play connection. Power Management: • Battery Saver Mode: Enabling low power mode may restrict background processes, affecting CarPlay. • Vehicle’s Electrical System: Unstable power delivery from the car’s battery or electrical interruptions can cause the head unit to malfunction. Phone & App Configuration Phone Settings: • Incorrect or conflicting settings (especially Bluetooth or Wi-Fi) on your iPhone can interfere with the CarPlay link. • Third-Party Apps/Profiles: • Installed apps or configuration profiles may conflict with CarPlay’s operation. • Native apps are apple maps, apple music, audio books, apple news, podcasts, messages and phone. All other apps are considered third party apps. App Conflicts: • Running conflicting apps that require similar system resources as CarPlay can cause instability. Mobile Data Plan: • Streaming from online sources without sufficient mobile data can result in lost connectivity. Other Factors Heat & Overheating: • If either the phone or the head unit overheats, they may disable certain functions to prevent damage, leading to disconnection. User Actions: • Accidentally disconnecting the device in settings, or physically moving or bumping the phone or cable, may disrupt the connection. Remedy FUP6 (E605.8) software has been released for the following chassis: 118, 177, 243,247,206,254,167,294,295,296,223, 297. Flash available software for the head unit and test for function. The LI will be updated once available for the remaining chassis. If the complaint remains after the SW update please continue with the steps below. Guided Diagnostic Path for Apple CarPlay Connection Issues: Please follow the steps below to systematically diagnose and resolve CarPlay concerns:Update Devices: • Ensure the iPhone is updated to the latest available iOS version. • Ensure the vehicle’s head unit is updated to the latest software version available. Isolate the Issue: • Check whether the symptom persists with another iPhone running the latest iOS version. • Test both wireless and wired CarPlay connections: • Does the issue only occur with wireless CarPlay? • Does the wired connection to the phone function correctly? Further Troubleshooting Steps: • Reboot the iPhone. See attachment for further instructions.

Complaint 1. General Diagnostic Tips 2. One or More PARK Sensor Activations 3. Red Ring Around Vehicle 4. "Active Parking and Parking Assist Inoperative" on Instrument Cluster 5. Cameras 6. Other Park Topics. Cause Various root causes Remedy See attached diagnostic guide.

Complaint Customer Complaint: - AC charging is not possible. - The departure time, charging pause, location-based charging or target SOC limit is automatically set to 50% or to a random value in the Mercedes me application or in the charging settings on the head unit display. (Picture 1 & 3) - Incorrect notifications appear in the Mercedes me application for charging-related functions. (Picture 2) Related DTCs in quick test: No related fault codes (DTCs) are stored in the relevant control units. CPC3 - N127 (Drivetrain control unit) OBL223_GEN4 - N83/11 (Alternating current charger for high-voltage battery) DCB223 - N116/5 - Direct current charge connection unit (DCCU) Picture1 The target SOC limit is automatically set to 50% or any random values during charging. Picture 2 Incorrect notification Example “Unable to unlock charging cable. Picture 3 Incorrect settings of charge interruption or pause. (If applicable) Cause - The Customer shares their Mercedes me credentials (password) with a third-party application, for example, a wall box application. This causes the Mercedes Benz backend server to receive random requests to reset the maximum SOC, departure time, charging pause, etc. - Charging settings are set incorrectly, for example, incorrect departure time, charging program, charging interruption/ pause, etc. Remedy The remedies below may vary depending on the customer complaint. Refer to the remedy that best matches the customer complaint. Remedy 1: The target SOC limit is automatically set to 50% or to random values during charging. - Change the Mercedes me login password on the Mercedes me homepage. (My Account > Login and Security > Reset). (Refer to Annex 1). Previously granted authorizations should then be revoked so that the charging settings can no longer be changed by external applications. Advise customers not to share the new password again. - Are there any sub-users? If yes, revoke their rights and reassess the function. -If differences between the vehicle and the Mercedes me app are visible, a new synchronization is recommended. Turn off Digital Extras through the Mercedes me app or the MMCR portal, and then turn the services on again. Remedy 2: Incorrect notifications in the Mercedes me app for charging-related functions. - Restart synchronization between the app and backend. Turn off Digital Extras through the Mercedes me app or the MMCR portal, and then turn the services on again. (Refer to Annex 2) Remedy 3: Incorrect charge interruption or pause setting. - Perform a factory reset of the head unit (A26/17). (Home > Functions > System > Reset), or turn off/correct all charging settings. (Refer to Annex 3) Additional Information: (Good to know) The LED on the charging inlet or socket indicates whether charging is completed or paused. 1) If the target SOC is reached, the charging inlet LED lights up Blue/Green without flashing. 2) If charging is paused, the charging inlet LED lights up orange without flashing. Additionally, the head unit charging settings display a charging pause. Note: Do not replace any hardware components for these complaints. If the complaint cannot be solved, please contact via TIPS or CAC.