Heart rate accuracy concern

[stantonarch]

In noticed that while watching my heart rate in real-time and then checking the history graph later it does not record the heart rate accurately. I also question the real-time accuracy of the heart rate, especially at high heart rates.

For example, yesterday it said my heart rate reached 170, which seems really high. And then when I checked the history graph it said my heart rate only reached 128.

So, which was the accurate reading, 170 or 128?

Maybe it only briefly reached around 170 and it wasn't long enough to record it and it only records sustained heart rates?

Moderator Edit: Clarified subject

[RicardoFitbit]

Hi @stantonarch, welcome to the Community Forums!

Thanks for bringing this to our attention and for the details that were shared in your post.  Let me share with you that heart-rate tracking can be affected by several factors including air temperature and device location on your arm For more information, I recommend you to check this help article and let me know if the issue persists after taking into consideration the details that are specified there.

I'll be here if further assistance is needed.

[MrMarv]

@RicardoFitbit -

What I believe @stantonarch was pointing out was the discrepancy in the reporting of heart rate history, not how the device may or may not recognize the heart rate.

@stantonarch - 

What you see in the historical heart rate graphs are averages. In both the iOS app and the web Dashboards's "Activity plus Stats" tile the reporting averages over five-minute slices.

So, if you indeed spiked to 170 but over a five-minute period were mainly hovering around 130 bpm, you can see where it would report 128 as a single five-minute average.

I have had a treadmill session where my device reports a very high bpm of 151 for eight straight seconds of the exercise record, but my daily heart rate graphic shows a five-minute average of 124. The exercise record starts that five-minute block at 100 and ends it at 104, with the 151 spike pretty much in the middle of the five-minute block. It is easy to see with the exercise starting at the beginning of a five-minute block.

I hope this explains what you have seen.

Good luck and welcome to the boards.

[MrMarv]

Actually, my apologies to @stantonarch and @RicardoFitbit .

Realtime and reporting were being brought to task.

My statement regarding reporting stand.

However - - - remember the 151 bpm for eight seconds?

I would suspect my heart is not capable of making that happen unless I am in fibrillation, not with taking Beta Blockers. In fact, taking Beta Blockers, which throttle your heart rate even during exercise, make it so that my current Max HR is defined as 120 bpm, instead of the normal 152 bpm of a 68 year old. My cardiologist has cautioned me from exceeding 110 bpm for any sustained period of time.

As a retired "geek" I test stuff like crazy. FitBit devices, and I have owned HR reporting devices since June of 2017, mostly represent my heart rate honestly. However, I have documented cases where the exercise apps tend to go a little crazy with heart rate reporting - like the previously posted treadmill exercise. FitBit isn't the only company with the issue; Apple, who has repeatedly been rated as the best at heart rate tracking, reportedly has the same issue when in "exercise mode".

[askmrhp]

The only time my watch reported that my heart rate was too high,is when my pulse went up to 170. I had carried a kayak up a steep hill. I would not known this. I am in the fitbit heart study and that data went to the study and emailed it to me.

some hours later my pulse went back to normal. I check my pulse and Spo2 with my pulse oxymeter every morning.

I am 71 and pretty healthy I want to keep it that way.

[stantonarch]

@MrMarv 

Thanks for clarifying both of my inquiries.

[MrMarv]

@stantonarch -

Glad to be of help.

And again, welcome to the boards.

[stantonarch]

@MrMarv 

Thanks and hello to a fellow "geek" and IT guy 🙂