Luxe is showing Fat Burn zone minutes at a lower Heart Rate

[srtninc]

Hi All,

One of our user's Luxe device is showing Zone minutes even when the user is not really active. Please find the relevant screenshots. Let us know what could be the issue here and how this could be fixed.

[JohnnyRow]

For Zone Minutes, the issue is not whether or not the user was active, per se.  Zone Minutes are totally based on heart rate.  Any time someone says 'zone minutes are wrong', the answer is 'look at heart rate'.  It is entirely possible the end result is wrong, but if so, almost certainly because heart rate is wrong, not because zone minute were calculate incorrectly.  Users have all the tools available to look at heart rate and see for themselves.  They well might conclude heart rate was recorded incorrectly, or it could be their heart rate was elevated for some reason other than being active.  Perhaps they were nervous or excited; these can raise the heart rate without really being exercise; debatable whether leads to increased calorie burn but to Fitbit algorithm based on heart rate, that can give zone minutes.  Or could even be heart rhythm issue.  But it's all in the heart rate record.

2 more pieces of info needed:

• What are the limits of the heart rate zones? Can be seen by tapping "Zone Minutes" circle near top of phone app.  Without this info don't know what heart rate is required for reaching fat-burn zone.
• All-day graph doesn't show enough detail to tell.  Need to see more detailed graph from workout summary or, if didn't qualify as workout, generate a workout for time period in question by logging an activity.  That will show more detailed heart rate graph of that time period.

[srtninc]

The issue is the zone ranges itself. If you see the attached screenshot from the user, the Fatburn zone is from 86 onwards, which looks wrong. Attaching the zone categorization for this user whose RHR is around 63. 

[LZeeW]

@srtninc   How old is the user?  The active zone minute equation isn’t as simple as the active minute equation, but calculating and verifying the zones is doable.

[srtninc]

Hi @LZeeW , we've found the issue. The user's DOB is somehow set to Jan 1st 1900 and the user's age is calculated as 123. We've asked the user to update the dob and the zone categorisation is correct now. 

There should be a default way of calculating zone minutes if the DOB looks wrong or not set. Not sure how many other Fitbit users have the same problem and think that Fitbit is showing wrong data. 

Thanks for all your help @JohnnyRow @LZeeW 

[LZeeW]

@srtninc   Fitbit explains how active zone minutes are calculated in this Help article.  The user's age and RHR are used in the equation.

I almost added the advice to check the birth date, but then I thought, "Who gets their own birth date wrong?"  I guess I was right.  😉