HeartRateZones Ranges are WRONG!

[rollingstrong]

When running queries Fitbit always returns this STRUCTURE

{"caloriesOut":0,"max":86,"min":30,"minutes":0,"name":"Out of Range"},{"caloriesOut":0,"max":120,"min":86,"minutes":0,"name":"Fat Burn"},{"caloriesOut":0,"max":146,"min":120,"minutes":0,"name":"Cardio"},{"caloriesOut":0,"max":220,"min":146,"minutes":0,"name":"Peak"}

"restingHeartRate":67

You know the resting heart Rate, and users age

Why is the range 30 - 86 and 86 - 120 Fixed / predefined and not user specific

220 - 48 (age) = 172  Max HR for a user aged 48 years old.

172 * 0.50 + 67 (Resting) = 153  Fat Burn Minimum

172 * 0.75 + 67 (Resting) = 196 Fat Burn Maximum

172 * 0.85 + 67 (Resting) =  213 Cardio Max

172 * 1.0   + 67 (Resting) = 239 Peak Max

Why does Fitbit not define the range for the individual user ?

Instead Fitbit used a fixed predefined range that in fact max this data useless.

For example I spend over 300 minutes "Fat Burning" according to my fitbit, while sitting at my desk coding.

Simply because my Fat Burn range is 153 - 196 bpm  and NOT 86 - 120 bpm

Can this be corrected in a future update ?

Thanks

[Gordon-C]

Hi @rollingstrong

Those heart rate zones are the default.  You can create custom heart rate zones in your Fitbit profile settings, https://www.fitbit.com/settings/profile.   The custom heart rate zones should be returned through the Web APIs.  

If you would like the default heart rate zones to be specific for each user based on their biometric data, please request the enhancement here, https://community.fitbit.com/t5/Feature-Suggestions/idb-p/features. 

Gordon