09-18-2022
08:38
- last edited on
12-18-2022
17:12
by
MatthewFitbit
09-18-2022
08:38
- last edited on
12-18-2022
17:12
by
MatthewFitbit
I recently got a Versa3 as part of the safety recall notice on my previous fitbit, though my previous fitbit worked fine. It seems to have a problem in that I start a run and start the watch in run mode, the display indicates it is tracking me. When I finish and synchronize with my phone and Strava it shows that my run started between 1/2 and 1Km after I actually started. It seems to be accurate after that. This problem is intermittent, but it is happening on about 20% of my runs. Any software upgrades I'm missing or other suggestion? I am on V36.128.6.17
Moderator Edit: Clarified subject
Answered! Go to the Best Answer.
09-18-2022 11:39 - edited 11-17-2023 04:32
09-18-2022 11:39 - edited 11-17-2023 04:32
Hi there, @trappist99. Thanks for stopping by in the Community Forums and sharing the details about the issue with your Versa 3.
Please note that if you're in a new location farther away from where you normally walk, it may take a few minutes to connect.
With that being said, I'd like to know if you've recently changed your normally location? How long do you wait for the GPS signal to connect? If you've noticed it's less than 5 minutes, please let your watch try to connect for at least 5 minutes before cancelling the exercise. Your Versa 3 will continue to try connecting and you can go about your walk.
Also, please make sure your Versa 3 meets the requirements for connecting to GPS. For more information, see Why isn't GPS working on my Fitbit device?
As @Guy_ has mentioned, please be advised that environmental factors, including tall buildings, dense forest, steep hills, and thick cloud cover, can interfere with your device’s ability to connect to GPS satellites. If the signal is blocked—either because you're indoors, underground, or due to another reason—GPS won't work.
Hope this helps.
Was my post helpful? Give it a thumbs up to show your appreciation! Of course, if this was the answer you were looking for, don't forget to make it the Best Answer! Als...
09-18-2022 09:53
09-18-2022 09:53
Hi @trappist99 - try restarting the watch to work with a fresh situation. It may be a GPS problem, if you are using it, that it doesn't get a signal. You could try without GPS or with (the contrary of what you use normally) and see if it makes a difference.
Author | ch, passion for improvement.
09-18-2022 11:39 - edited 11-17-2023 04:32
09-18-2022 11:39 - edited 11-17-2023 04:32
Hi there, @trappist99. Thanks for stopping by in the Community Forums and sharing the details about the issue with your Versa 3.
Please note that if you're in a new location farther away from where you normally walk, it may take a few minutes to connect.
With that being said, I'd like to know if you've recently changed your normally location? How long do you wait for the GPS signal to connect? If you've noticed it's less than 5 minutes, please let your watch try to connect for at least 5 minutes before cancelling the exercise. Your Versa 3 will continue to try connecting and you can go about your walk.
Also, please make sure your Versa 3 meets the requirements for connecting to GPS. For more information, see Why isn't GPS working on my Fitbit device?
As @Guy_ has mentioned, please be advised that environmental factors, including tall buildings, dense forest, steep hills, and thick cloud cover, can interfere with your device’s ability to connect to GPS satellites. If the signal is blocked—either because you're indoors, underground, or due to another reason—GPS won't work.
Hope this helps.
Was my post helpful? Give it a thumbs up to show your appreciation! Of course, if this was the answer you were looking for, don't forget to make it the Best Answer! Als...
09-19-2022 18:35 - edited 09-19-2022 18:36
09-19-2022 18:35 - edited 09-19-2022 18:36
Thanks for the suggestions. I only run on 3 loop trails, about 6 miles apart and close to town with clear sky visibility so GPS should be fine, however, I'll try starting the watch as I head out, then clear and restart when I actually start the run.