New Ford Pass / PAAK BT Bug that may strand you.

[Robob]

Within the past few months in the retail and beta (test flight) versions of Ford Pass there seems to be a Bluetooth(BT) key / PAAK bug. I have posted this in other threads but I am making a thread for info so people don’t end up stranded by this randomly striking bug.

My car is fully updated in FDRS and iPhone 14 Pro is also updated fully to 17.5.1, app is now retail 5.0 version and have removed the beta versions. PAAK has worked great ever since I got the car almost a year ago with this same phone so nothing has changed other than updates.

After a random amount of time the PAAK key in app will just stay disconnected in BT status, the Bluetooth audio and CarPlay connections will work fine. But there seems to be no way to force BT to connect with a refresh, log out/in, reset phone, reset car, etc. Nothing will make it re-connect and you must use the backup password. Remote start and all other non BT functions still work in the app as well.

The BT connection with the last of the VIN + MACH E in the phones Bluetooth connections will not connect no matter what. If you search for connections after removing this you will see the car is still broadcasting the connection but the phone won’t validate and connect to it.

The only way to get it back is to reset PAAK in car settings/general, reset ford pass PAAK, then remove the BT connections in phone, delete and reinstall app and re-pair PAAK but it still happens randomly again.

Just FYI in case someone gets this bug, make sure you have your password set and test it regularly after car and app updates.

Do NOT delete the app or Bluetooth connections before getting to a key fob first. As once you remove the app the PAAK backup code can sometimes reset or not work in my testing until re-paired with the app.

I reported this each time it happened in beta and also in retail testing so hopefully a fix will come from ford or an iOS update soon. I also hope they add a manual way to force connect the BT key or even disable it if you are working near the car and don’t want to have it always connecting when you walk by.

TLDR- Ford Pass can randomly not connect your Bluetooth key, do not delete the app or Bluetooth connections until your back to a key fob. Then delete/reset in car and app, then re-pair PAAK. Always test your backup code after app and car updates.

Sponsored

 

[BMT1071]

I have experienced most of what you describe on Android as well. The big difference being that when the BT won't connect the backup passcode screen will not come up. Fortunately restarting my phone has always fixed the BT connection. This was happening for about a month before I got the 5.0 update and I never had the beta.
After the 5.0 update I foolishly logged out of FP in the hopes of fixing another issue where it can't turn P&C back on. I then had to re-pair my phone for PaaK and it was a nightmare. I finally had success after deleting all of the Ford related BT profiles in my phone. Very frustrating.
Samsung Galaxy S22 Ultra & Galaxy Watch.

 

[DoogleMac]

I have a very similar problem. There are 2 BT addresses which show up on my iPhone. One has a 5 digit number in front of MACHE and the other is what I have named BT in Sync. My iPhone wants to connect intermittently with the one with the number but drops it regularly. The BT address that I named will not connect.

PAAK does not work but Apple CarPlay does connect sometimes. FP works to lock, unlock and control the A/C but the remote controls (frunk, tailgate and windows) don’t work and show BT is disconnected.

I was on the phone with ford technical support for 45 min yesterday and Sync was reset, but there was no solution (I also haven’t been getting updates). They transferred me to FP but I gave up waiting.

Edit: I figured out the workarounds but I’m afraid I’ll mess things up more without FP help.

 

[Mach-Lee]

Within the past few months in the retail and beta (test flight) versions of Ford Pass there seems to be a Bluetooth(BT) key / PAAK bug. I have posted this in other threads but I am making a thread for info so people don’t end up stranded by this randomly striking bug.

My car is fully updated in FDRS and iPhone 14 Pro is also updated fully to 17.5.1, app is now retail 5.0 version and have removed the beta versions. PAAK has worked great ever since I got the car almost a year ago with this same phone so nothing has changed other than updates.

After a random amount of time the PAAK key in app will just stay disconnected in BT status, the Bluetooth audio and CarPlay connections will work fine. But there seems to be no way to force BT to connect with a refresh, log out/in, reset phone, reset car, etc. Nothing will make it re-connect and you must use the backup password. Remote start and all other non BT functions still work in the app as well.

The BT connection with the last of the VIN + MACH E in the phones Bluetooth connections will not connect no matter what. If you search for connections after removing this you will see the car is still broadcasting the connection but the phone won’t validate and connect to it.

The only way to get it back is to reset PAAK in car settings/general, reset ford pass PAAK, then remove the BT connections in phone, delete and reinstall app and re-pair PAAK but it still happens randomly again.

Just FYI in case someone gets this bug, make sure you have your password set and test it regularly after car and app updates.

Do NOT delete the app or Bluetooth connections before getting to a key fob first. As once you remove the app the PAAK backup code can sometimes reset or not work in my testing until re-paired with the app.

I reported this each time it happened in beta and also in retail testing so hopefully a fix will come from ford or an iOS update soon. I also hope they add a manual way to force connect the BT key or even disable it if you are working near the car and don’t want to have it always connecting when you walk by.

TLDR- Ford Pass can randomly not connect your Bluetooth key, do not delete the app or Bluetooth connections until your back to a key fob. Then delete/reset in car and app, then re-pair PAAK. Always test your backup code after app and car updates.

Question, do you think this is related to 12V status? If the phone being connected constantly drains the 12V battery, the Bluetooth module in the car might go into a sleep mode and not connect until the car is woken up again. Pressing the open button on the door or the start button should make it wake up and connect though.

 

[Robob]

I have checked in FDRS when it happens it’s usually all green and at ~12.8v on Lv battery, some random history DTC sometimes but nothing set in red. I tried re-writing the RFA config the time before last failure. I also went back inside for 20-30 min and re-attempted and still no connecting.

I also thought it was due to walking around it too much and locking me out or going to sleep but this last time I just went out to garage in the morning and it was locked up no connecting.

There are 2 BT addresses which show up on my iPhone. One has a 5 digit number in front of MACHE and the other is what I have named BT in Sync

The one with the numbers is the last part of your vin + Mach E is the Bluetooth key part that you pair with the code when setting up PAAK. That connection is the issue that is causing the whole mess, you cannot manually connect it in the phone settings, the request has to come from the app. When we had access to the old version of the app even attempting to refresh didn’t cause it to try to reconnect either.

having had PAAK work great for so long I hope they get it sorted soon.

 

[phil]

The only way to get it back is to reset PAAK in car settings/general, reset ford pass PAAK, then remove the BT connections in phone, delete and reinstall app and re-pair PAAK but it still happens randomly again.

If the bug randomly recurs even AFTER the suggested remedy, I think it is better to just stop using PAAK. Repeatedly patching the same bug and waiting for the next failure is a recipe for frustration. Better to wait for a durable solution from the manufacturer.

 

[dtbaker61]

I am gonna be pissed off if the FP 5.0 update, which I did not ask for, is less reliable for PAAK which has worked 100% for the last 18 months.

 

[Robob]

For now I just leave a fob at work and with the one at home I’m usually not far from one of the two places.
It has only failed while away at a shop once but the password worked fine. The other 4 times have been at work or home so I‘ve been trying random things to get it to connect, and scanning the heck out of it with FDRS when it does it trying to get it to set a code but nothing seems to be car side.

Something must have changed in the app or something that changed in the back end OS stuff on iOS and android if both have seen this happen.

This thread is mostly a PSA for: Do not delete the app or the BT key connection until you have a fob, and aways do a door pillar code and backup password check after app or car updates. Key fobs and phones get lost, smashed, and or stolen so it’s best to be prepared.

 

[DoogleMac]

The one with the numbers is the last part of your vin + Mach E is the Bluetooth key part that you pair with the code when setting up PAAK. That connection is the issue that is causing the whole mess, you cannot manually connect it in the phone settings, the request has to come from the app. When we had access to the old version of the app even attempting to refresh didn’t cause it to try to reconnect either.

having had PAAK work great for so long I hope they get it sorted soon.

Thanks, that helps explain what is going on.

 

[Snakebitten]

I will spend a short amount of energy troubleshooting PAAK if/when it fails in the future. I can delete the failed setup in mere seconds now that I have a better understanding of the "pieces". And rebuilding it fresh only takes a couple of minutes too.

The first time PAAK failed, I chased that rabbit thoroughly and stubbornly. And it was worth the effort just to become more familiar with the processes. But that same familiarity now moved the line for addressing a failure.

(Note: The first time PAAK flaked out, it flaked for 2 phones simultaneously. That's could be a significant clue if bundled with others)

If it sounds like PAAK has been brittle for me, not so. But it has suddenly failed and refused to connect with both a long session of FDRS updates (first time), and then once again with the recently retired beta 5.0 update. Interestingly PAAK survived the beta being replaced with the production build of V5.

Oh, and neither failure would have been due to low voltage on mine.

Android
Samsung Galaxy 22FE
Samsung Galaxy A13 (No SIM)

Neither phone is flagship quality.

 

[Robob]

Until this issue the new app and RFA module updates had it connecting faster when it does work in my experience as well. I hope they can get this sorted quickly, thankfully it’s not just me going crazy others have had the issue as well.

 

[Jtbuster]

I will spend a short amount of energy troubleshooting PAAK if/when it fails in the future. I can delete the failed setup in mere seconds now that I have a better understanding of the "pieces". And rebuilding it fresh only takes a couple of minutes too.

The first time PAAK failed, I chased that rabbit thoroughly and stubbornly. And it was worth the effort just to become more familiar with the processes. But that same familiarity now moved the line for addressing a failure.

(Note: The first time PAAK flaked out, it flaked for 2 phones simultaneously. That's could be a significant clue if bundled with others)

If it sounds like PAAK has been brittle for me, not so. But it has suddenly failed and refused to connect with both a long session of FDRS updates (first time), and then once again with the recently retired beta 5.0 update. Interestingly PAAK survived the beta being replaced with the production build of V5.

Oh, and neither failure would have been due to low voltage on mine.

Android
Samsung Galaxy 22FE
Samsung Galaxy A13 (No SIM)

Neither phone is flagship quality.

So you have the cure but you will not give it to us. Go away.

 

[Snakebitten]

So you have the cure but you will not give it to us. Go away.

Cure?

I didn't mean to imply such.
I just stated that I would delete a failed PAAK configure and build a new one quickly.

It's really easy if I just get in the car, with a FOB, and with a phone.

Nothing secret.
And I wouldn't keep a secret from anyone here anyway. I owe this forum

 

[rrobe53]

I just had this issue today as well, PaaK bluetooth network just randomly not broadcasting.

 

[Norcolboulder]

Cure?

I didn't mean to imply such.
I just stated that I would delete a failed PAAK configure and build a new one quickly.

It's really easy if I just get in the car, with a FOB, and with a phone.

Nothing secret.
And I wouldn't keep a secret from anyone here anyway. I owe this forum

I have been out of the country for 2 weeks so few updates . And yes I love the information and community on this forum.

so I missed some of the noise and challenges . My plan is to charge and update my GTPE . Noise there as well.
then update our ford pass apps and with key fobs activate Paak
if I have an issue delete and reinstall fordpass

try again - sounds reasonable?

Sponsored