Versa 4 refusing to pair with my phone.

[Townie71]

bought a new Versa 4 on Dec 30th 2022. It paired with my Samsung Galaxy with no problems and it has been working perfectly until yesterday, (Jan 19th 2023). Went out for a walk, (recovering from a mini-stroke in Oct 2022), it recorded the walk paces, (around 6,000) and also recorded the GPS route on my phone. At around 17:00 it stopped updating my paces on the app, but continued recording paces on the Versa. I've tried all the suggestions from Fitbit, (force closing the App on my phone) and even resorted to removing the App from my phone entirely. I then re-installed the App and tried pairing the Versa again. All I get is a message telling me that "Bluetooth pairing is taking longer than usual. Please be patient, we're on it". 2 hours last night and an hour this morning (so far). The Versa is fully charged as is the phone and the versa is within 2 inches of the phone. This is the second Fitbit watch I've had problems with, my first was a Charge which simply stopped working after around 12 months and now this Versa which was bought for me by my wife as an early birthday present. What is going on with this watch? Shallowing I return it to the seller, (Amazon) and give it a less than favourable review?

[Guy_]

Hi @Townie71 - often logout of the Fitbit App and restarting both watch and phone resolves syncing problems.

[Townie71]

Thanks for your interest Guy. I've logged out and restarted the phone and the watch. It's pairing and dropping out now after a few hours. This afternoons walk was mapped, but the display with the number of steps has disappeared from my phone and my iPad. The number of steps is still registering on the watch though. I'm beginning to think that it's got something to do with the switchover to Google, ( but Fitbit will never admit that there's a problem will they!!) I'll give it until next week and if nothing gets sorted, (or even gets admitted that there's a problem,) then the phone goes back and Fitbit loses a customer forever. I'm sorry that Fitbit seem to act in this fashion, as the watch is fine apart from this problem. I'm just getting a bit fed up waiting to see what will go wrong next. I'm 73 years old and am currently getting over a mini-stroke last October. Learning to walk again is enough of a task without technology giving me another headache!! Once again, thanks for your interest.

[Guy_]

@Townie71 - thanks. I note you have 2 devices, this can be source of concern.

Can you try using just the phone.

Remove the Versa 4 from the iPad Bluetooth, then do the restart process again.

[Townie71]

Hi Guy, following your advice, I have this morning, (Sat 21st), completely deleted the Fitbit App from my iPad, and I have been into settings and told it not to pair with the Versa 4. I have completely deleted the Fitbit App from my phone and then re-installed it. The Versa 4 has now (eventually ) paired with the phone, however there is STILL no record of steps taken on the phone App. I'll keep wearing the Versa this weekend to see if the thing starts registering properly, if not, it's back to Amazon on monday. Once again, thank you for your attempts to help.

[Guy_ · Accepted solution]

@Townie71- on the phone try logout of the Fitbit App and swipe the window off and login again and sync, it may clear things that the reinstall didn't and it may improve the syncing.

If by chance the Steps icon is not showing in the Fitbit App, click Edit and add it back.

[Townie71]

Following your advice, I went into the Fitbit App and pressed the Edit button and the "Steps" icon is back where it was instead of a blank space. All seems to be back to how it was, Thanks for taking the time to help this old technodummy!!!😃

[Townie71]

MORE problems with my Versa 4, this morning after my usual 20 mins exercise bike session, I wen to have a shower and noticed that the Versa was stuck on the "find my phone" app. Pressing the button or swiping the face did nothing, so I held the button in and did a factory reset. Since then, I've had no more problems, (so far!!) Factory reset now seems to resolve most problems.