Fitbit Blaze: Calorie count on Fitbit device v Fitbit app

[Mariannehagan]

Hey guys!

So whenever I work out, I have some calorie confusion. After I click that I've finished on my actual device, the calorie readout is usually between 260 and 300. However, once I pull up the very same exercise on my app, it drops down to somewhere in the 80s. If someone could explain this, I'd be very grateful. I have a friend with the Charge HR and she says her calorie count remains the same on both the device and also the exercise details on the app. I'm just wondering if it's an error or setting somewhere to be changed, or if it's just something I don't understand. Thanks, friends!

[AlejandraFitbit]

A warm welcome to the Community @Mariannehagan. I found this post, where our friend @Colinm39 is giving a good explanation about how calories work and think that there is all the information you are looking for. If it isn't, let me know.

See you around! 

[Brackforce]

I don't think she's referring to the calories tile on the dashboard. She's talking about discrepancies between workout results on the actual Blaze versus the dashboard. I have the same issue with the Blaze telling me one thing but the activity details on the dashboard say something else (differences in calories burned, average speed, etc.). Thus far, no one has given me an answer as to why this happens. Instead, we get pointed to posts that have nothing to do with what we're talking about.

For example,

Let's say I do 30 bike ride. At the end of my ride, when I stop my Blaze and it shows me a results summary on the actual watch, it might say I burned 500 calories and biked 10 miles at an average speed of 19.5 mph. When I sync to my dashboard, however, the results often differ. The activity on my dashboard might say I biked for 30 minutes, burned 478 calories, and biked 10 miles at an average speed of 20.1 mph. This happens pretty much every time I do a workout. Why do the results differ?

[FerdinandFitbit]

Hey there guys @Brackforce @Mariannehagan. Happy to see you around!

This is a strange situation and thanks for bringing that up guys. I wanted to make sure from what @Mariannehagan said if you were syncing your activity from your tracker and also entering the activity manually or if it was just the synced activity giving different results on the watch and on the dashboard after synced.

What I could recommend right now, would be to restart your trackers by pressing and holding the left and lower right buttons. This will  reboot the tracker and also try to log out and log back in to your Fitbit account and after doing this, try it out and see if you  get to experience the same situation.

Let me know how it goes.

[Brackforce]

Ferdin,

I did what you suggested by restarting my Blaze and logging out/in to both my online dashboard and app (on an iPhone 6+ running iOS 9.3.5). Afterwards I did a very small test. I started a "walk" exercise using GPS and paced around my kitchen for a couple of minutes. Here are the results:

Blaze Summary:

3:58 total

.03 miles

63 average HR

71 max HR

18 calories

281 steps

Dashboard Exercise Summary:

3:58 total

.03 miles

64 average HR

67 max HR

18 cals

281 steps

I found something even more odd. I checked the exercise summary on my phone app and it says the average HR was 62, so none of them agree completely.

This morning I walked my dog and recorded it as a walk. My Blaze said I walked for 57:19 and did 2.54 miles with an average HR of 71, a max HR of 105, burned 412 calories, and walked 5,229 steps. My dashboard agrees with most of the stats, but lists the average HR as 73 and gives e 5,256 steps instead. It just doesn't make any sense. On a side note, I wore my Polar H7 chest strap and recorded the same walk with Polar Beat on my phone. It recorded the same time (57:19) but said I went 2.67 miles with an average HR of 90 and a max of 116. It also said I only burned 216 calories (it has the same user settings height and weight wise and was set on "walking"). That is a huge difference in HR, calorie burn, and a pretty big distance discrepancy. In the grand scheme of things, it probably doesn't matter much, but it's still a bit frustrating. I'm not sure which device to trust (if any).