Running heart rate discrepancy-Inspire 2

[FytbytUser64368]

After a run with Running app, In fitbit app there is heartbeat graph that makes sense, varying 60 bpm -160 bpm, but the summary figures make no sense, avg 23 bpm, no zones. In the daily pane the heartbeat graph shows 30 minutes gap. How it comes that for the same period there are two different values one showing measurement and other claiming measurent is missing, please?

Moderator edit: updated subject for clarity

[EdsonFitbit]

Welcome to the Fitbit Community, @FytbytUser64368.

I’m sorry to hear about the difficulties you experienced with your Fitbit Inspire 2.

To have a better understanding of the heart-rate discrepancy, please attach an image of your Fitbit app.

I'll be waiting for your response.

[FytbytUser64368]

Hi Edson,

on web dashboard it looks like:

on phone, the graph for the same exercise is different. Anyway both web and android app report average 23 bpm like I was almost dead.

My hypothesis is simple, for unknown pulse the app makes up a value: sometimes 0s (for avg bpm), sometimes linear approximation (for web graph), sometimes projection of recent (for android graph), ... and then it draws conclusion from the made up values.

By observation, if in the explicit exercise mode like a run the band exercise app tends to loose pulse till end of exercise after any transient measurement outage.   

[EdsonFitbit]

Thanks for your response, @FytbytUser64368.

There are some factors that can affect your heart-rate reading on your Fitbit device. Please follow these tips to resolve heart-rate tracking issues.

Our team has recently released a new version of the Fitbit app (3.62 for iOS and Android devices). For instructions on how to check your current version and update, please visit this article and open the menu "How do I update the Fitbit app?".

Hope this helps.

[FytbytUser64368]

Hi Edson,

the app upgrade changes the app behaviour but it does not fix it:

     

In the graph, 0:00 - 6:50 is stretched to 0:00 - 42:56. (6:50 - 42:56 were unknowns.)

The avg bpm is calculated from the stretched data.

BUT the active zones (the 11 mins above) are not calculated from the stretched data.

Handling of unknowns should be consistent across all interpretations.

Anyway it'd be better to have less unknowns by making the band Exercises app more robust and to better recover from transient measurement outages. By observation the pulse signal is immediately regained after closing the band Exercises app that pernamently lost the pulse signal.

  Best regards