01-30-2018 13:42
01-30-2018 13:42
When out on runs I have done before my blaze is logging them completely wrong and showing random darts across the map which I have not run and when running with a friend her watch was logging us running under 9 min/miles and when I finished I looked at mine and it's logged me running 14 min/miles which is very incorrect. I use the run function on my watch and the location support on my phone is on high accuracy. Getting frustrated as I'm training for a half marathon and none of my stats are correct.
02-01-2018
04:34
- last edited on
03-31-2025
08:46
by
MarreFitbit
02-01-2018
04:34
- last edited on
03-31-2025
08:46
by
MarreFitbit
Hi there @SunsetRunner. Great to see you in the Fitbit Community Forums! 🙂
I'm very sorry to hear that your Blaze seems not to be tracking your runs accurately 😕
Do you by any chance see any message on your tracker saying "Check Fitbit App"? If that was the case you can try going to the Fitbit app and here, tap on the icon of your Blaze at the top left corner. Then, tap Notifications and then turn on "Notification Widget".
I can also suggest two other things that I think would be better to perform together instead of separately and see if they work. The first one would be to restart your tracker. You can easily do this by pressing the left and lower right buttons for 10-12 seconds. This will make your tracker to reboot
Once you've restarted your tracker, try to set it up as a new device. For this, go to the Account section at the top right corner on the Fitbit app and select the option that says "Set up a new device". Follow the on-screen instructions and once you're done, your tracker should be syncing without a problem and your information should be recorded properly.
Hope this helps. Let me know if you need anything else!
Help others by giving votes and marking helpful solutions as Accepted
02-06-2018 13:43
02-06-2018 13:43
Thank you for your reply, I have tried all the things you have suggested and it is still not logging the runs it starts off of then just seems to give up. It stops tracking and counting the mileage. Some times it stops after ½ a mile tonight it was ok for nearly 3 miles counting but only showed 1½miles on the map.