Mercedes-Benz EQA Charger Won't Start a Session
You connected the cable to your EQA's right rear charge port, but nothing happens. No charging animation on MBUX, no power flowing. This is one of the most frustrating situations at a public charger, but it is almost always fixable on the spot. The cause is usually authentication, cable locking, or the charger itself.
Quick Diagnosis
Is the charger screen on and showing a ready state?
Check if the charger display is lit and showing "Available" or a similar ready message.
Symptoms
- CCS2 connector plugged in but MBUX shows no charging activity
- Charger screen shows an error or stays on the start screen after tapping
- Plug & Charge does not authenticate automatically at a supported station
- Charge port LED on the EQA does not turn on or blinks red
- Mercedes me app shows the car as connected but not charging
Why This Happens
Authentication failed
Public chargers require authentication before they deliver power. If Plug & Charge did not activate, or your RFID card or app was not recognized, the charger will not start. The EQA supports Plug & Charge, but not every network supports it yet. You may need a charging app or RFID card as a backup.
Cable not fully seated in the charge port
The EQA's charge port is on the right rear. The CCS2 connector must click firmly into place. If it is slightly angled or not pushed in far enough, the car will not lock the cable and charging will not begin. You should hear and feel a distinct click.
Charge port door or latch issue
If the charge port door did not open fully or the locking mechanism is stuck (sometimes from ice or dirt), the connector cannot seat properly. The EQA will not start charging if it detects the cable is not securely locked.
Charger hardware fault
Public chargers fail regularly. A charger may appear operational on its screen but have a faulty contactor, damaged cable, or communication error. This is not your EQA's fault. The charger simply cannot deliver power.
Scheduled charging is active
If you set a departure time or scheduled charging window in MBUX or the Mercedes me app, the EQA may deliberately delay the start of charging. It will connect but not draw power until the scheduled time. This catches many drivers off guard at public chargers.
What to Do
- 1
Remove and reseat the CCS2 connector
Pull the connector out of the right rear charge port. Inspect it for visible damage or debris. Push it back in firmly until you hear a click. The charge port LED should respond. If the cable feels loose or wobbly, the connector or port may be dirty.
- 2
Authenticate manually if Plug & Charge failed
Open the charging network's app on your phone and start the session from there. Or tap your RFID card on the charger's reader. Plug & Charge is convenient but not universal. Many networks still require app-based or card-based authentication.
- 3
Check for scheduled charging in MBUX
Open the charging settings in MBUX. If a departure time or scheduled charging window is active, disable it. At public chargers, you want charging to start immediately. Scheduled charging is designed for home use where off-peak electricity rates matter.
- 4
Lock and unlock the EQA, then try again
Use the key or Mercedes me app to lock the car, wait 10 seconds, then unlock it. This resets the charge port locking mechanism and the onboard charging controller. Reconnect the cable after unlocking.
- 5
Try a different connector or charger
If the station has multiple connectors, try another one. If the entire unit seems unresponsive, move to a different charger. Report the faulty charger through the network's app so other drivers know it is down.
Prevention Tips
- Keep a charging RFID card in the car as a backup when Plug & Charge is not supported
- Disable scheduled charging before road trips so public charger sessions start immediately
- Clean the charge port area periodically, especially in winter when ice and salt can accumulate
- Download the apps for the charging networks you use most before you need them at the charger
- Check the Mercedes me app for any active charge settings that might delay or block sessions