Roxy'sHusband
Member
- First Name
- Shawn
- Joined
- Feb 28, 2022
- Threads
- 7
- Messages
- 20
- Reaction score
- 3
- Location
- Boston
- Vehicles
- 2021 RWD Standard Range
- Thread starter
- #1
My wife and I have had several problems with PaaK in the last couple of months. Advice on any would be appreciated!
There's probably other stuff, but this is what I can remember right now.
- First problem was car would recognize the phone on approach, would unlock other doors but not the driver's. We had to open the rear door, which would then unlock the driver's door. That problem has been overcome but the newest one:
- Car doesn't recognize phone on approach at all. We now have to unlock the car through the FordPass app unlock feature. Closing and reopening the app doesn't solve the problem.
- To try to clear those problems, I deleted the app from my phone and deleted my phone from the paired list on the car, and tried to create a whole new user profile. Now I get:
- Two Bluetooth devices connect once inside the car:
- Connection to Sync4 that uses the name I gave it. That connects automatically and stays connected, but I think it's only for phone calls, music, etc
- A numbered Mach E device like "12345 Mach E", which is unstable - automatically connects, then disconnects, then connects, the disconnects, repeat ad nauseum. I don't recognize this one but it seems to be related to PaaK in that, when it's connected, the car will start with my phone as a PaaK, when it's disconnected, I get the error message "Key Not Present" (or whatever it is, I can't remember exactly right now)
- I renamed the car as a device, thinking that would show up as the ID for the bluetooth connection, but it doesn't appear.
- Two Bluetooth devices connect once inside the car:
There's probably other stuff, but this is what I can remember right now.
Sponsored