05-01-2017 10:33
05-01-2017 10:33
I just recently switch the the Blaze before I was using the Alta I love both. But, my current problem is with the hourly activity goals. Most days it counts it just fine but some days the App will say I hit a certain hour but the watch does not and other days it is vice versa where the watch says I hit it but the Apps says I didn't. Now I do know that this has been a problem for some time now but is there any way to fix it? It really motivates me to move during the day as I sit at a desk and my coworkers and I battle to see who gets the most hours completed during the day.
Thank You for any help.
05-01-2017 11:58
05-01-2017 11:58
You are not alone with this problem. Since the last firmware update, the data between the Blaze and the phone app/browser dashboard frequently doesn't match. The data between the phone app and the browser dashboard consistently matches each other. It's not a failure to sync because parts of the Blaze data does appear accurately in the app/dashboard. The numbers on the Blaze itself seem to be the accurate info. However, with some of the data randomly different, it makes me distrustful of the whole system. Like you, I really like the hourly step goal. But lately one to FOUR hours a day where I meet the step goal are simply dropped by the app/dashboard. It's very frustrating.
We were discussing this problem in another message thread that a moderator shut down last week. I've reached out twice to customer support and been told that it was a known issue with no fix currently available. Per the moderator's direction, I was going to post a new thread about it when I saw yours.
05-01-2017 12:04
05-01-2017 12:04
With the last update Fotbit thought yhey had this fixed, the main thread is in the Android forum.
It was requested to provide more info on the phone and os version over there if you still are experiancing this.
Unfortunately the thread is full of "I have the same problem" posts, which is not of any help.
05-01-2017 12:19
05-01-2017 12:19
I'm using a Blaze (with firmware version 8.401.3) paired with my iPhone 6s (with iOS 10.3.1) with the FitBit app (last updated on April 25). I've reported the problem twice to customer support and less than two days ago was specifically told that this is a known issue that has NOT been fixed.