05-21-2016 10:35
05-21-2016 10:35
went for bike ride this morning, using Blaze for first time on my normal 17.75 mi route. Blaze connected to my iPhone, but showed final distance 0.5 mi short
05-22-2016 05:42 - edited 05-22-2016 07:44
05-22-2016 05:42 - edited 05-22-2016 07:44
This is within 3%, most cars after they change their tires can be this far off.
Ok truthfully there are several things that can affect distance. Cloud and tree cover, or walking by a tall building, may affect the time the signal arrives, losing a satellite lock my straighten out turns and shorten the distance.
I've noticed the Surge,Blaze, Fitbit App, MapMyFitness, and Charity Run never agree in distance, but they all seem to be close, within few percent.
05-22-2016 07:09
05-22-2016 07:09
@jmmrph first welcome to the community... I have to agree with @Rich_Laue as I have found even with my high end GPS devices distance vary with usage But I would recomment that you keep a log and see if this is a consistant difference or varying. If consistant you need to look at other items like the straight away and turning of the bike ride itself.
Having said this also exam the tracking on the dashboard it will help some too.
05-27-2016 09:55
05-27-2016 09:55
Hello @jmmrph welcome to the Fitbit Community! As mentioned by @Andhanniand @Rich_Laue there are several factors that can affect the accuracy of your information. Take a look at this post from @AndrewFitbit.
Hope this helps! 🙂
It is health that is real wealth and not pieces of silver and gold! Share your story!
05-27-2016 10:13
05-27-2016 10:13
05-28-2016 09:53
05-28-2016 09:53
Hello @jmmrph thanks for the update. I would suggest to contact customer support so they can review your tracker's back-end information and provide you a personalized troubleshoot.
Let me know how it goes. 😉
It is health that is real wealth and not pieces of silver and gold! Share your story!
05-28-2016 11:02
05-28-2016 11:02