help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Blaze sync drops calories burned to less than 100 at every sync

Replies are disabled for this topic. Start a new one or visit our Help Center.

‎09-23-2017 07:18

‎09-23-2017 07:18

My Blaze is having an issue with recording calories burned properly. Every time I synch to the mobile app, the calories drop to 70 or less.  I think this is a program error. It happens on my Alta HR too.  So, FitBit, your code is doing something wrong and needs to be fixed.

I restarted both devices, removed and replaced the FitBit app on my phone, so what next?  I would like to track calories burned, but if it always resets to 70 or less, that is not useful.

Thanks, any suggestions welcome.

Best Answer
0 Votes
2 REPLIES 2

‎09-25-2017 11:42

‎09-25-2017 11:42

It's great to have you here @Les45! Thanks for the troubleshooting that you've done. This seems pretty weird and shouldn't be happening. I would like you to provide me with a screenshot of what you're seeing, before syncing and after. 

 

Additionally, I would like you to make sure that you have the latest version of the app which is 2.40.1 for iOS and 2.57.3 for Android. 

 

Keep me posted. 

Want to get more active? Visit Get Moving in the Lifestyle Discussion Forum.


Best Answer
0 Votes

‎10-01-2017 10:53

In response to SilviaFitbit

‎10-01-2017 10:53

Hi,

I did get an answer, and it seems to be working.  I went into the Fitbit chat, and was told that the engineers know of this problem and were working on it.  In the mean-time, I was given a suggestion about turning off another fitbit device and updateing one at a time and that seems to be working. 

Best Answer