03-01-2017
12:54
- last edited on
03-02-2017
03:01
by
AlejandraFitbit
03-01-2017
12:54
- last edited on
03-02-2017
03:01
by
AlejandraFitbit
My Blaze is showing I've met my 250 steps for the last 7 hours; however, the app is showing I've only met my 250 steps for 5 of the 7 hours. What could be the issue?
Moderator edit: Subject for clarity
03-02-2017 03:06
03-02-2017 03:06
It's great to welcome you @anjc1977. Have you checked if your app updated? If you haven't, I recommend updating your iOS Fitbit app by following @MarreFitbit's instructions in the How do I update the Fitbit app for iOS? post.
I hope this helps, let me know how it goes.
03-02-2017 08:48
03-02-2017 08:48
Similar issue being discussed here: https://community.fitbit.com/t5/Blaze/Hourly-tracker/m-p/1849973#U1849973
03-02-2017 10:39
03-02-2017 10:39
It is also being discussed in the charge 2 forum, since this is an app error this should really be in the proper app forum. Posting in the hardware forum wont tell us which app the user is using. This gives us nothing to go on.
03-03-2017 12:03
03-03-2017 12:03
I have a similar issue - I've set up to track 250+ steps for 14 hours, and all too often the Blaze shows that I've completed an hour but the Android app shows that hour as incomplete.
It seems to happen more often when the 250 steps are completed late in the hour (perhaps it doesn't sync again during that hour?).
03-05-2017 03:39
03-05-2017 03:39
Thanks for the information guys @Rich_Laue, @LincolnHyde and @hollyhock.
I want to let you know that this inconvenience has been escalated to our team and that they are working in finding a fix to this. Your patience will be appreciated in this case.
See you around.
03-10-2017 05:31
03-10-2017 05:31
Looking forward to a solution to this annoying issue. I've had my Blaze for 1 week & this has now happened on 3 separate days, today included.
03-24-2017 15:27
03-24-2017 15:27
it also happening to me on my iPhone. its happened at least twice in the last week.
03-24-2017 15:33
03-24-2017 15:33
Hey Guys,
I just bought my FITBIT BLAZE, hope this community and the problems and the resolutions will help a lot .. keep doing it .... Kudos to Fitbit for such a good one
03-28-2017 13:23
03-28-2017 13:23
For what it's worth, the error is still occurring in the 17.8.401.3 firmware update.
04-10-2017 22:40
04-10-2017 22:40
I am having the same problem! Every time I get the full 12 hours it never says I do when I sync it! 😩
04-11-2017 09:42
04-11-2017 09:42
I think I've figured it out. I catch a bus at 8:03 every morning, so I start walking at 8:00 sharp - and the Blaze shows that I've completed the 250 steps, so I return to the bus stop and wait.
This morning, I started walking at 8:01 rather than 8:00, and the app recorded the walk successfully.
I think the Blaze starts each hour at x:00:00, and the app starts each hour at x:01:00, so any steps in the first minute of each hour are either not counted or counted towards the prior hour.
04-16-2017 05:29
04-16-2017 05:29
Hi guys, hope you are doing ok.
As mentioned in my previous post, this problem has been escalated to our team. They are working really hard in finding a solution for this inconvenience, I really hope this can be fixed as soon as possible.
See you around.
05-08-2017 19:00
05-08-2017 19:00
Same problem,Blaze says 10 out of 10 app says 8 out of 10
05-10-2017 04:13
05-10-2017 04:13
It's great to welcome you @chasingfurkids. Could you please check your app one more time? Since this inconvenience has already been resolved. If you continue having issues, let me know.
Hope to hear from you soon.
05-10-2017 09:54
05-10-2017 09:54
Make sure the app is at its latest version
06-28-2017 16:41
06-28-2017 16:41
I have the most updated version of the app, and I'm still having this problem. My Fitbit watch showed that I met my 250+ steps 10/10 twice this week. My app shows that I missed one hour on two different days this week. (After syncing it fully...all of the other data matches.)
06-29-2017 04:09
06-29-2017 04:09
A warm welcome to the Forums @EllaRose and thanks for the update with this issue, I just want to let you know that our team is working hard finding a solution for this inconvenience. I recommend checking this post where our friend @CallieM is providing updates about this.
Thanks for your patience and understanding.