Fitbit - Resting Heart Rate??

One of my granddaughters gave Gramps (and me) Fitbit watches for Fathers Day. My resting heart rate for the last few days is shown below. It's been running in the range of 67 - 72.

However, when I sit quietly at the end of the day reading or watching TV, the Fitbit shows my HR is usually running in the range of 60 - 63. Why is this not used as my RHR?

Beats me...I wonder if it is taking an average low point and calling it the resting rate and you spent more time at 67?????

I've got a mild case of Bradycardia. No treatment needed yet.

I'm happy when the resting rate is above 45.

Denial Dave wrote: ↑

Fri Jul 17, 2020 5:05 pm

I've got a mild case of Bradycardia. No treatment needed yet.

I'm happy when the resting rate is above 45.

One day, I overheard some runners boasting. One of them said his RHR was 45.

Many of us register higher heart rates in the clinic because of white coat syndrome.

Is it possible that your fitbit thinks that you are asleep at night when you are reading and watching TV? Does it calculate RHR using only waking values? I track my sleep with my apple watch, and it often thinks I'm asleep at the end of the day when I'm sitting at the computer or watching a show. Maybe that's happening with you, and it isn't including those measurements for that reason?

Again, we must remember that devices like fitbit, apple watch, and Misfit are not medical devices.
They are intended for entertainment, so serious use is at your own risk.

Ramie wrote: ↑

Mon Jul 20, 2020 9:40 pm

Is it possible that your fitbit thinks that you are asleep at night when you are reading and watching TV? Does it calculate RHR using only waking values?

??? You seem to have reversed the issue I reported.

Hi ChicagoGranny,

It seems you are not the only one with this anomaly.

https://community.fitbit.com/t5/Charge- ... -p/1095262

Thanks, Rick!

rick blaine wrote: ↑

Tue Jul 21, 2020 12:02 pm

Hi ChicagoGranny,

It seems you are not the only one with this anomaly.

https://community.fitbit.com/t5/Charge- ... -p/1095262

---->

I'm finding this very frustrating to be sitting at my desk, and see my HR showing as 74, but my Resting HR being 80.

He has an easy job!

This answer seems to best fit my personal observations --->

‎07-18-2020 06:51

Hello @ChicagoGranny and welcome to the Help forums. We all have many time periods throughout the day when we are "at rest" and Fitbit uses all of those time periods to calculate our resting heart rate. It is the average throughout the day, not the lowest one measured.

Community Council Member
Laurie | Maryland, USA

https://community.fitbit.com/t5/Charge- ... 123#M13806

ChicagoGranny wrote: ↑

Tue Jul 21, 2020 11:31 am

Ramie wrote: ↑

Mon Jul 20, 2020 9:40 pm

Is it possible that your fitbit thinks that you are asleep at night when you are reading and watching TV? Does it calculate RHR using only waking values?

??? You seem to have reversed the issue I reported.

Let me explain what I mean (in case you're still wondering about this)... I have an apple watch and I use a sleep tracking app. I am often awake late at night, sitting quietly at my desk. Very sedentary, but wide awake. However, it is common for my sleep app to record that I have been asleep during that time, probably because I am more still and my heartrate is often lower than other times during the day. Because it misinterprets my activity as sleeping rather than awake but not active, my average sleeping heartrate is incorrect, and when I go into the apps and adjust the sleeping times (the apps allow me to edit and tell them my actual bedtime), the average heart rate and other metrics all change. I can picture your exact problem happening to me, because my heartrate seems to be at its lowest late at night. If RHR is just a measure of heartrate when awake, and if those lower, late night values aren't included because my device thinks I'm asleep, then it will only consider the other, higher heartrates measured throughout the day, when figuring out the RHR. Anyway, I missed your reply when you first gave it, so hopefully you've got the problem figured out or resolved now.