API capturing high step count but zero active minutes

[Kigo]

We have a situation where our web API with Fitbit is capturing high step count but zero active minutes ( for instance 17K steps but zero light, active or highly active minutes- all using Fitbit charge 5). In some cases we have 15k steps, 140 light activity and zero active or very active minutes. We have looked at the associated heart rates and a number of them are in the fat burn zone for over 10 minutes in several instances. Any idea what could be wrong? Our system has worked well over the last two years so this is a recent development. Currently, we have about 90 people using Fitbit Charge 5 which are connected to our web platform interfaced with Fitbit.

[JohnnyRow]

Which device?

[Kigo]

Fair enough. Fitbit charge 5

[JohnnyRow · Accepted solution]

Charge 5 tracks AZM (Active Zone Minutes, not Zone Minutes, which have been phased out except on a few remaining older devices.  Your description of 10 minutes in fat  burn zone sounds like you are thinking of the older Zone Minutes.  Perhaps you had a recent switch to Charge 5 which accounts for this.  AZM has a different criteria.  You can read more about it at https://support.google.com/fitbit/answer/14236509? and the following help articles.

[Kigo]

This is so helpful. Our API was set up when we were using Charge 2. For some reason, it worked well when we moved to Charge 4. We just started noticing problems after using Charge 5 for about 6 months.

[JohnnyRow]

Not sure if it was mentioned in that Help article, but the change from previous Zone Minutes to current AZM (Active Zone Minutes) was based on change in exercise recommendation from American Heart Association, and then adapted by others included CDC.

[Kigo]

Makes a lot of sense. Not sure how we missed the memo. Thank you so very much for your prompt help.