PAAK

[Sparsons59]

My PAAK used to work quite well. Recently it’s become very wonky. The car no longer lights up when I get close with my phone. It will still unlock the car but it takes 15-20 seconds to do so. It won’t turn on the car. I get “No Key Detected” on the dash display. Anyone else had this issue? Looking for a solution.

Sponsored

 

[tomthetenacious]

What phone are you using?

 

[Sparsons59]

iPhone 12 Pro

 

[ryano7700]

Happens sporadically to me. Have to unlock phone and open Ford app.

 

[tomthetenacious]

Do you have all the optimizations enabled including location services set to “Always Allow”?

 

[Sparsons59]

I deleted the app and reinstalled it and re-paired it to the car. That worked! All good. Thanks for the responses.

 

[Flint302]

When you look up the word "wonky" in a dictionary, it shows a picture of a Mach E.

 

[Mach En Cheese]

I had a lot of connections issues a few months back and took it to the dealer after the Ford EV support dept couldn't figure it out. Dealer had it for 3 1/2 weeks, mostly just sitting on the lot, before finally updating some modules that became faulty following a series of OTA updates. The faulty modules were not visible remotely so the dealer has to physically connect to the car to see it.

Glad I was still barely under warranty because they couldn't tell me who would be responsible for technical issues following an OTA update. That might be a good question for anyone from Ford Corp to answer......Who is responsible for faulty OTA updates? Should I disable all OTAs once I'm out of warranty?

My dealer experience was such a nightmare (Fritts in Riverside, CA) that Ford gave me a free comprehensive (75k/5yrs total) extended warranty for my troubles. Yes, it was that bad and the dealer doesn't care!

Back to the original topic......

A month or two ago, my Mach E had several updates within a short time and now I'm experiencing similar issues with my lights not turning on as I approach, doors not unlocking unless I manually press the button on the app and the "no key" message when I press start.

PAAK has been around long enough that they should have figured it out by now. My wife's Tesla has other issues but at least we've never been locked out of it.

 

[dah]

I had a lot of connections issues a few months back and took it to the dealer after the Ford EV support dept couldn't figure it out. Dealer had it for 3 1/2 weeks, mostly just sitting on the lot, before finally updating some modules that became faulty following a series of OTA updates. The faulty modules were not visible remotely so the dealer has to physically connect to the car to see it.

Glad I was still barely under warranty because they couldn't tell me who would be responsible for technical issues following an OTA update. That might be a good question for anyone from Ford Corp to answer......Who is responsible for faulty OTA updates? Should I disable all OTAs once I'm out of warranty?

My dealer experience was such a nightmare (Fritts in Riverside, CA) that Ford gave me a free comprehensive (75k/5yrs total) extended warranty for my troubles. Yes, it was that bad and the dealer doesn't care!

Back to the original topic......

A month or two ago, my Mach E had several updates within a short time and now I'm experiencing similar issues with my lights not turning on as I approach, doors not unlocking unless I manually press the button on the app and the "no key" message when I press start.

PAAK has been around long enough that they should have figured it out by now. My wife's Tesla has other issues but at least we've never been locked out of it.

One thing to check on the phone side that FordPass location permissions are set to "Always" and "Precise Location". The text isn't clear about this, but it's also required to have those permissions otherwise the bluetooth beacon in the vehicle won't properly and reliably communicate with the FordPass app.

FordPass prompts you to set these when you do Paak setup, but iOS itself will confrim later on "Do you want to continue to allow FordPass to ___?" or something like that, and if you accidentally hit the wrong selection on those modals, these might get flipped to "While Using the App" or to turn or "Precise Location" which means Paak will then probably only work if the app is in the foreground in your hand.

 

[Mach En Cheese]

One thing to check on the phone side that FordPass location permissions are set to "Always" and "Precise Location". The text isn't clear about this, but it's also required to have those permissions otherwise the bluetooth beacon in the vehicle won't properly and reliably communicate with the FordPass app.

FordPass prompts you to set these when you do Paak setup, but iOS itself will confrim later on "Do you want to continue to allow FordPass to ___?" or something like that, and if you accidentally hit the wrong selection on those modals, these might get flipped to "While Using the App" or to turn or "Precise Location" which means Paak will then probably only work if the app is in the foreground in your hand.

Yes, I have permissions set to allow everything but access to photos and videos, since I couldn't see a reason for it. I also have battery saving mode turned off.

Wasn't much fun today as i was standing in the rain, while trying to open my door. Again no lights and had to use my phone to unlock manually.

Sponsored