05-15-2016 09:09
05-15-2016 09:09
Answered! Go to the Best Answer.
05-16-2016 10:10
05-16-2016 10:10
The fitbit Blaze does not have a GPS included in the watch. Instead, it uses a connected GPS. In order to establish the connection, when you begin a run, the Blaze looks for a paired phone. Once it finds the phone, the Blaze can then use the GPS throughout the duration of the run.
If you didn't have your phone with you, then the Blaze has no idea how fast you are traveling so it uses an average stride length. This is not as accurate as the GPS, which is why the miles ran wasn't the same as the expected miles ran.
I suggest that you connect your phone to your Blaze for all races and as many runs as possible. This will require you to run with your phone. You can either use a waist band or an arm band, or anything similar to that.
05-16-2016 08:05
05-16-2016 08:05
Welcome to the Community @Gibson7. If your information is not being accurate, I recommend logging out and logging back in to your account. Sometimes the information doesn't update as fast as we want it to. You can also Restart your Blaze and test it and if it keeps being inaccurate feel free to contact our Support Team since they have the proper tools to see the information that your tracker is registering. For a faster response you can contact them via phone or chat.
Let me know the outcome.
05-16-2016 08:29
05-16-2016 08:29
Were you connected to your phone's GPS? It is very possible that if you were not, the Blaze just guessed how far each stride was and wasn't exactly accurate. (Your fitbit profile has an option to adjust your stride length per step, running and walking.)
I have found that when not connected to a GPS via phone, the fitbit records a smaller distance than what was actually travelled.
05-16-2016 09:12
05-16-2016 09:12
@Gibson7 my first thought was the title is about steps and the message is about distance. Is your step count correct? For distance was the phone with you for the connected GPS to work?
05-16-2016 09:55
05-16-2016 09:55
05-16-2016 10:10
05-16-2016 10:10
The fitbit Blaze does not have a GPS included in the watch. Instead, it uses a connected GPS. In order to establish the connection, when you begin a run, the Blaze looks for a paired phone. Once it finds the phone, the Blaze can then use the GPS throughout the duration of the run.
If you didn't have your phone with you, then the Blaze has no idea how fast you are traveling so it uses an average stride length. This is not as accurate as the GPS, which is why the miles ran wasn't the same as the expected miles ran.
I suggest that you connect your phone to your Blaze for all races and as many runs as possible. This will require you to run with your phone. You can either use a waist band or an arm band, or anything similar to that.
05-16-2016 12:36 - edited 05-16-2016 12:37
05-16-2016 12:36 - edited 05-16-2016 12:37
I agree with @fudge22's assessment, but would like to add that it is possible to manually add your stride length.
@Gibson7 this is not hard and you already have all the info needed.
This should get your walking distance in the ball park without the phone on you.
Let us know if you need further help.