Manually logged exercises not using HR in calorie burn calculation

[AlexKahler]

Hey,
I've noticed a peculiar thing when manually logging exercises to the app - you have the ability to choose whether the calorie burn should be precise (I assume this is based on HR and/or activity - http://i.imgur.com/4u0oXK3.png) or estimated (http://i.imgur.com/Lm1oJsG.png).

However, the last few times when I've been logging weight training, the calorie burn/minute seems to be the same no matter the intensity or duration.

Proof:
Workout 1: http://i.imgur.com/2msg7pe.png
Calorie burn: http://i.imgur.com/gvp3dVh.png

Workout 2: http://i.imgur.com/LLQTuDB.png
Calorie burn: http://imgur.com/JDf1WLw

Workout 3: http://i.imgur.com/avMdYO9.png
Calorie burn: http://i.imgur.com/bb839go.jpg

This has lead me to believe that the Fitbit app doesn't take heartrate into account when calculating "precise" calories and is basing it in an arbitrary number.

[MakMak]

Hi, @AlexKahler! You're absolutely right, Fitbit does not use heart rate when adding manual exercise. The "precise" slider just allows you to adjust the intensity of your workout. I found this out recently, too. You would think it would be an easy enough thing for them to use heart rate for manual activities, but for whatever reason, they don't (much like allowing people to edit previously entered exercises).

[AlexKahler]

@MakMak - But this makes no sense? Why have a "precise" option and a separate "estimated" option, with the intensity scale, if the precise option doesn't take HR and activity into consideration? What is the precise option for then?

[MakMak]

I completely agree it makes no sense. If you have the heart rate available, why not use it?

The "precise" toggle activates a slider which allows you to identify the exercise as high/med/low intensity and adjusts the estimated calories based on that.