K-A

Sometimes when I turn the car off, the same way I always do (Park, E-Brake, turn the car off by pressing the button once), I'll get out, and notice my headlights and I/C Display haven't gone off yet, which means the car hasn't registered that it's "off". I'll have to go back, and unlock the car (sometimes it allows me to lock it when this happens, and sometimes it doesn't), then the I/C Display will read "Key Not Detected". I'll have to sit back down in the car, and hit the Start button 3 times (no starting up the motor though), to get the lights to shut off, and have it turn off properly.

Also, every now and then, when I go to unlock the car, it will say "Key Not Detected" on the I/C, and I'll have to unlock it manually, then everything works properly for a while. I'm also positive that this isn't battery related.

Ctrl+alt+Elite

havent had any issues, i have pretty much the MO when I get out of mine. The headlights and dash stay lit for a about 2 minutes and then go out. I always thought that was standard

K-A

Hmm. Weird. Mine usually go off right when I turn the car off (the way I like). However, I DO have the "light delay" activated, but it only works when I manually lock or unlock the car from my Key Fob (the way I like).

DHI

"Key Not Detected"... happened to me a handful of times.
Not nearly as alarming as transmission not engaging in D or R though. Happened to me once. MY heart sank.

hyperion667

geez, no concerns here yet, sometimes I get the key not detected note, but that's about it.......this keyless business has ruined me with my three other vehicles, LOL.......

petee1997

I sometimes have to unlock car with key fob and then keyless goes back to normal operation.

K-A

^^ Yeah that's exactly what happens to me sometimes as well. When I unlock with the Key it goes back to normal.

Tonight again it did the whole "not turning off the lights thing" when I turned the car off. I had to sit there and hit the button 3 times to get it to turn off. I keep trying to figure out if there's some different little thing I do that activates the light-delay, since it usually turns them off immediately (lately it's doing the delay thing more, oddly).

BudC

Please read about the LOCATOR LIGHTING function in your manual. You can turn it on and the lights will delay turning off for 15 seconds when it's dark. You can turn it on but temporarily cancel it until you restart the car or you can simply disable it.

This function is active when the lights are set to Automatic.

silviang

I posted something similar in an earlier thread and it did not get better for me. I have replaced the batteries on the remotes but it did not make a difference. I did not visit the dealer yet as this happens sporadically and I am not able to reproduce this at all.

As you said the solution is to go all manual on this when it happens. But I am hoping that either somebody from the mailing list figures out a solution or I will get bothered enough such that I can go back-n-forth to the dealer on this one.

Quite puzzled by all this...

scfishnman

I had a similar problem with my 2005 CLK500 Cabriolet. The first time it happened replacing the battery in the remote seemed to fix it. However, later it happened again but on an intermittent basis. Sold the car before the problem was solved, therefore, have no other suggestions.

cvinfig

See this bulletin post by konigstiger:
https://mbworld.org/forums/4607576-post34.html

I occasionally have the 'key not recognized' thing happen so will mention it at my first service...

Dooty

My E350 Bluetec had a similar Key less go problem that was solved by the dealer. The symptoms were, I could not get into the car unless I unlocked it manually. Once inside the key was not detected. I either removed the key less go from the ignition and started the car. Or I left the key less go in the ignition and lock/unlocked the doors using the door mounted switch. In both cases, the car started. After the car started, I had one more glitch. It would not shift out of P. I stop and started it 3 times then I could get it out of P. The dealer replaced the ignition switch and a tranny control module. It has not happened again!

Camel1970

Read postings under "E-Class(w212)>ipad interfering with keyless Go" for some real horror stories on this option.

golfster

Although not keyless go, my Porsche does this when parked for a period of one to two weeks. I have to unlock the door manually with the key, then it is fine after that. This was addressed in the manual for that car as normal.

By chance, does your experience occur after your car has been parked for any length of time?

hyperion667

sometimes I get the 'key not detected' but that's after I've already gotten in, hehe....
and the key is in my pocket not 24 inches from the ignition.....

go figure.....

konigstiger

If vehicle is equipped with part 2129055400 or 2129055600, there may be a software error electronic ignition lock (EZS). When a CAN wakeup event occurs, a faulty EZS detects a reset instead of wakeup and initiates a circuit restoration sequence. Mention bulletin LI54.10-P-051681 – KG, vehicle battery discharged and/or vehicle cannot be unlocked and locked

hyperion667

Konigstiger: god amoung men

jrobgood71

K-A: that whole debacle is still plaguing me as well. Several EISes and Keyless-Go modules have been swapped, but no resolution yet.

K-A

That sucks. Fortunately mine hasn't acted up in a while. I'm trying to figure out if there's some rhyme or reason to this, but don't think so.

Back in the day, someone posted a Thread where their I/C screen would come on all by itself, randomly when the car was locked and sitting. I think there was a Bulletin on that, but I'm assuming it may have only affected very early models.

B6JoeS4

Same thing happened to my dad's '11 E550. We have all the symptoms still after many trips to the dealer replacing various modules, keys, batteries, etc. Symptoms we have experienced, car will not unlock by putting your hand on the handle, nor will it unlock by pressing unlock on the fobs. To unlock the car, we have to use the "skeleton key". once in the car, it will say "key not detected' but it will still start. sometimes it will go into drive or reverse, but sometimes it won't. Pretty sporadic as far as that goes. Other issue that has killed the battery 3 times, including today, is the radio turning on and the wipers sticking in the up position. Keys are nowhere near the car and there is no iPod in the car. If you get lucky and catch it on before it has killed the battery, you can open the door (because it also unlocks itself) and turn everything off with the start/stop button. Then if you want to start the car, it won't detect a key. to remedy this, you either have to pull the button out and start it the old fashioned way OR you can get out of the car, lock the doors with the sensor on the handle, then get back in the car and start it. whether it goes into drive or not is the next surprise. sometimes it does, sometimes it doesn't. if it doesn't, you have to turn the car off again and re-start it.

So needless to say, there is no real "pattern" to what happens. MB is aware of the issue as it is present on both the late '10 to all of "11 E and S class cars with keyless-go. Because of the issues we have, MB is buying back the car as it is practically useless and about as reliable as an old Jaguar.

silviang

Hello,
I have an update for the group with respect to this issue as well. I went to the dealer and he identified (through the fault codes) and replaced the ignition module. So far (for 2 days) things seem okay but it is too early to tell I think.

I'll update again if i encounter any additional bad behavior.

B6JoeS4

^dealer replaced the ICM on my dads too. That was the first thing they did. Give it a few days, the problem will come back

jrobgood71

Yeah, me too. EIS, Keyless Go, CAN stuff, firmware reflashes... it came back a few days later.

jrobgood71

@Silviang: Any further issues with your Keyless-Go?

silviang

I have a few weeks of experience now and things seems to be working correctly now. I am not having any of the problems I reported earlier. It looks like in my case the ignition module was the problem.

Silvian