Resting heart rate is missing for multiple days

[Lei33]

I have a fitbit sense and am running the fitbit app on Android 12 on Pixel 5, all system/apps software updated to the latest. Fitbit sense is running latest firmware. I wear my Sense every day, but only sporadically to sleep.

I have observed missing resting heart rate (RHR) data that can last for several days in the past. At this time, it's gone missing for a  whole 1.5 weeks. Today is 2022-05-27 and in the app, 2022-05-16 is the last day for which there is a reported resting heart rate. Naturally, the graph also stopped on that day. However, the actual heart rate data (yes, I weat the sense every day) is evidentally all there. ie. when I go into the daily heart rate chart by tapping on 2022-05-16, I can then swipe right to see all the heart rate data for all following days all the way to today. Each day has substantial number of hours logged, so I would not think RHR is missing because too llittle data recorded each day.

I have so far done the following multiple time to try to fix, without any success:

• reboot the sense
• restart the fitbit app
• clear fitbit app cache data and restart
• restart phone

I see a few posts (1, 2) in the forums regarding the same problem, but it's unclear whether any solution/resolution was reached for these threads. I would've imagined that if these were fixed over time, with me being on the latest app versions, and device firmware, this would/should not be a present issue.

Anyone else experiencing this and/or knows a solution?

Thanks.

[JammyB]

I believe the app is at fault. I created three accounts and the RHR froze on the two first accounts after about ten days. On my newest account (this morning), the Fitbit device shows accurate RHR. I logged out, reset my Fitbit on my old account and low and behold there is the frozen RHR at 68, even though the stats page says (erroneously) its 65. Same wrist, same device. There is clearly a problem created by the app and how it syncs to the device. Try setting up a new account in your device and see if you get the same result. Now there is no more developer contact I really don't think there is a way to address this with the app designer/developer.

[Lei33]

Thank you JammyB. I am also of the fairly firm belief that this is an issue with the app. I hope Fitbit is able to address in this manner.

[JammyB]

Good O. I'm not sure what point you're making, the app is what appears to be at fault. We aren't discussing low RHR per se, we're discussing faults in Fitbit products that seem to be reported frequently with little action from Google, the owner of the product.

It would be nice if Google stopped dodging the ball on the heart rate issue. I know this is the last Fitbit I'll buy unless the function is repaired. 

[Lei33]

I second JammyB's sentiment. This has been frustrating. I am now actively looking at other non-fitbit options to move to.

For the record, RHR returned to the chart for 2 days momentarily, without me having done anything different, and has gone missing-in-action again for a few days now.

[JammyB]

I had an early morning today, (03:00) and despite not getting out of bed
until 07:00, and my RHR varying between 57 and 60 for four hours, Fitbit
magically decided it was 67 (AGAIN). So at around 11:30 I returned the
Charge 4 to the original vendor. I also noted this problem has been on
posts since 2016. They've had 6 years to fix it. I guess they just don't
give a **ahem**.
Good bye, Fitbit! It was (almost) fun while it lasted! I (almost) missed
you when I went out for my run. Hello Garmin! Looking forward to taking you
out for a date on Monday!

[vs1dcolor]

Yes. charging $10 a month for faulty application isn't worth it. too bad the app is so flimsy and glitchy. I got the 6 months free and noticed too much inconsistencies and things not working right. so long. Fitbit!