PatrickCH4313
Member
Can you let Tesla (service Center) confirm the key fob fix availability date for v2 keys and the reason I got the message "already up to date" for key fobs I got in January 2019 ! Thanks in advance
Last edited:
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Fey fobs not found for 2019.32 security update
- Thread starter azred
- Start date
Will do on Friday. I spoke to my service center today. I was told that this issue was also reported by another owner and that they had kicked it up to somebody in engineering and we’re still waiting for an answer.
He also added my Model S remote update failure issue to the mobile service notes so that they could look at it when they come to my home to deal with our Model 3 on Friday as well. I’ll report back whenever I find out.
PatrickCH4313
Member
Suggestions:
1. Only have one fob in range at a time.
2. Put in a fresh battery.
3. Try placing the fob flat side up.
PatrickCH4313
Member
I moved the key fog light to the left and it recognized the key fob (refer to my previous post).
I've tried all this - just one fob in the car, CR2032 replaced, all imaginable locations & positions tried on the center console, mobile phone in airplane mode etc.
I started to get the "key not detected" error in the car quite frequently, hope the battery replacement solved that.
PatrickCH4313
Member
I tried several times and always failed.
Then I moved the key fog light to the left and the key fob was detected.
BTW, the message tells that my 2 key fog (v2) were already updated.
Message : Model S key fob (v2) : already updated
Last edited:
I've tried also that exact location and having the fob lengthways, sideways, wheels down, wheels up..... I guess I just have to let the service to fix this connection problem, it may also have something to do with those "key not detected" errors.
Mobile Tech that came today was not able provide any additional information. Also today I talked to my contact at the service center who escalated the issue. He said he had not gotten an answer back yet.
PatrickCH4313
Member
Thanks. I got firmware 2019.32.2.1 this morning and tried again to update my key fog. Same message : Already updated.
Not sure when exactly the change happened. (When they ran out of v1 Fobs?)
Production dates can be imprecise.
Each Tesla has a “Birthday”
When it appeared on their network...
I managed to find out what it was for my Model S100D before delivery as I was trying to find out if I got the new MCU. Got lucky.
It was born on March 12, 2018. Production completed on March 14, 2018.
As I mentioned in a prior post, I upgraded my March ‘18 to v2 Key Fobs allowing me to leave one of my old Key Fobs (v1) paired. (3 keys max)
Normally I leave it with the battery out for security. Put me in a unique position to test the update on both versions. Properly ID’d all 3. So it is very likely that yours was also.
I’m having the same problem. Ugh... after this new software update I’m getting “key fob not detected inside car”. I have to use my app to drive and unlock. I have V1 key fob, replaced the battery... no help
Just got 2019.32.2.2. Made another attempt to update a v2 fob. Same message:
“Model S key fob (v2): Already up to date”
“Model S key fob (v2): Already up to date”
I had the same problem with only one fob a few updates ago. Basically, the update (car update, not fob update) caused the car to lose pairing with the fob. The only way to do a re-pairing was with a mobile tech visit. Scheduled it, got the appointment for 3 days later. Tech initially warned me it could be a bad fob, but then confirmed it was just not paired with the car, and this wasn't the first time he'd seen this. 15 minutes later everything was working again.
The service fixed the problem on my car - the antenna inside the center console was not properly connected.
Similar threads
