Charge 6 reached a heart rate of 200+

[JamoC]

Just before bed last night, while doing nothing but sitting, my Charge 6 reached 213BPM and stayed in the 200's for about 5min. I did not feel anything, and grabbed my chest strap to try and compare, but did not get to it in time before the pulse returned to normal range. 

Is there anything known at this point about high BPM or issues with Charge 6? 

I run 3-5k a day (not an Olympic pace, but still 5:30 a km). My heart stays between 150bpm 160bpm. 

Before I run off to the doctor, is there anything anyone may know or have experienced, since getting onto the charge 6? 

Cheers

Moderator Edit: Clarified subject

[JamoC]

Since everyone seems to hit 213 on the dot I would assume so. I run 3-5k a day (m-f) and my HR never goes above 170. I feel like I would notice it.

I also have been sitting around often and watch the Fitbit heart rate go up and down on its own. Sometimes 140, sometimes 150 for no reason. I have used a pulse oximeter to confirm the error with the Fitbit.

I would recommend not stressing over Fitbit data. I have seen a cardiologist a few times because of these silly things and he said not to trust them, and if they worked he would bought them instead of the hundreds of thousands of dollars worth of equipment.

[ChrisV55]

Yes, I think you are absolutely right. The same thing has happened several times without me having any problems. 
I now ignore these high values ​​and I feel fine.

[lizmbehan]

Thank you, it was very concerning at the time

[Gabbee]

I've been having a similar problem with my Charge 5, and come here to see if the C6 has fixed it. Apparently not.

In my case I'm getting high (120 to 170) HR readings in some exercise modes - Workout, Yoga, etc. but not Walk mode. I know they're incorrect because I've checked with pulse oximeter and Polar strap. This occurs in minor-medium exercise and afterwards for 20min or so.

I suspect that these incorrect readings stem from an unfortunate sampling rate, combined with my somewhat irregular HR which is presumably worse during exercise. Whatever it is, it doesn't occur for the pulse oximeter or Polar strap.

[ExSeaDog]

My current solution was to turn off the afib warnings in the app. Since doing that I have not received any wacky notifications of higher than 123 bpm. Hardly a solution but certainly less stress. I have been having trouble with my various Fitbits  for some time now. I can no longer access my Versa 3, it just refuses to update. My long term solution is that when this Charge dies, I am switching to something (anything)  that isn't a Fitbit. I have already lot all my "Friends" all my "Stats" and all my "Badges".

Not good enough Google

[Linz16]

I'm glad I checked in here.

I've only had the Charge 6 for 3 weeks, purchased to replace my old Charge 2.

Yesterday, I also experienced the magic number of 213 heart rate while sitting down at rest. I happened to look down at the device to see the time, and HR was 145 then crazily jumping up through the 200s. It then jumped down to 50 for a few mins, before stabilising a few mins later at what i assume was my genuine heart rate.  Obviously I had a huge panic thinking I was having some kind of cardio episode. When I checked the app it had recorded around 15 minutes of heart rate at 213.

I felt unwell for the rest of the day (either due to the stress, or because I really have had an event) and made a Drs appointment as soon as I could.  My Dr of course has to take my information at face value and referred me for ecg and blood tests etc. I must admit I am scared. 

Now I come on here and find out this might be a glitch?! Can anyone at Fitbit/Google confirm whether this has been investigated because if it is a glitch it's a serious problem. There must be a significance of the 213 reading that several people have reported? If we'd all had a cardiac event that number would vary surely? 

I really wish I'd been wearing my old C2 at the same time to compare. I'm going to put it on now, in case this happens again (ironically there was absolutely nothing wrong with my C2 but I had to replace it because it wouldn't work with the app anymore and Google told me it was an unsupported legacy device!) 

[Linz16]

@LizzyFitbit hi!

Are you able to advise on this issue please? There are lots of reports on this thread and others, of heart rate showing 213 for a period of time whilst at rest. Is this a bug, what is the significance of 213 as so many people report the same thing, could this be looked into please as it's frightening people. Thank you ! 

[Muvver]

Hi
I wouldn’t worry about it too much. I haven’t had this issue again.

If you have heart problems or have other symptoms then consult a
professional. I honestly think it’s a glitch.
Just like, I can’t change the hours of daily 250 steps each hour. When I do
change it on app, it goes right back to the other hours 🤷🏼‍:female_sign:

[Muvver]

Hi

Have you tried tight or loosening the strap. I found the plastic strap was my problem. It also gave me sweat rashes. I now have an elastic strap

[lizmbehan]

Thanks for the advice, I will try loosening the strap

[Rjm22]

Mine was 212 I've had a 155 and 165 readings   as well as far as I can remember I was sitting in my chair. I had a heart attack in July 2021 so I'm somewhat concerned. After seening this I might not have to worry.  I got the Fitbit 5 a few months after the heart attack because I wasn't sure about what I was feeling. Then I got a Fitbit 6, this one is almost 2 years old I think. I got it not long after it came out.

[lizmbehan]

Sorry to hear that, I hope you are doing ok now - as others have said on
here it seems like a glitch. Wish you good health

[Shiloh223]

Do you know if they have looked into this     it's very unnerving  it's completely weird that two thirteen is some magic number

[Muvver]

Hi
I’m not sure it’s been looked into. I have issues with my charge 6.
Not that reliable for me.

[Linz16]

When I posted my comment above,  I tried to tag one of the Fitbit moderators but either it did not work or they chose not to respond. 

I agree it's really worrying. 

[Gabbee]

---

@Shiloh223 wrote:  it's very unnerving  it's completely weird that two thirteen is some magic number

---

Interesting but it may not be significant. I've had some experience processing analog data in software and these sorts of 'magic numbers' often seem to crop up. Most of the fitbit's displayed numbers are the result of a whole lot of guestimates and often reasonable assumptions, making it seem as if we're getting more information than should be possible. (I'm fascinated by the estimates of SPO2 for example.)

Even HR is potentially tricky to measure, given that the signal may include a lot of noise, and detecting each beat gets trickier if the pulse is irregular (as in my case). Looking at a fitbit ECG shows the irregularity, the noise and variation in the peaks (and even ectopic (?) beats). The processing of this data is a brute, starting with the analog/digital conversion followed by a number of mathematical functions any of which may tend to *quantise* the data, ie restrict it to a relative small number of values. If our fitbit were to include the error margin, we might find HR was 213 +/-5 for example. If this quantisation is the full explanation, I'd expect not to see (say) 211, 212, 214 or 215. But even if I saw these, I'd then like to see a graph of how often they appear.

BTW, despite these comments I'm super-impressed at how well these devices work, providing amazing value for money IMNSHO. I can live with a bit of wierdo behaviour as a very slight downside.

[Linz16]

@Gabbee interesting thank you.

Im having another theory now. I've never seen anyone post a HIGHER number than 213. What if 213 is the absolute highest the device can get to, so if someone really is having an episode of extreme high heart rate of potentially even higher than 213 due to a medical condition, that is what it will show. Or, if its a technical glitch, if the device freaks out for whatever reason, it goes to it's default 'highest' display? I'm speculating of course in my desperation for an answer!

For me, prior to me getting the Charge 6, I'd have totally agreed with your comment that the huge benefits of having a Fitbit vastly outweigh any occasional 'weirdo behaviour'. I used to see my Fitbit as a reassuring device but since having the 6 it's a massive source of anxiety for me because I cannot tell whether this is 'weirdo behaviour' or whether it's real and I have a sudden heart condition. I am awaiting tests. 

It would be great if someone at Fitbit could just let us know if this is a known fault. 

[Gabbee]

213 may be the max (@Linz16) but I wouldn't bet on it. I reckon it would give some sort of indication when the HR gets too high for the software's comfort.

Given that the popularity of these smartwatches depends on the magical way they derive figures attractive to (many) users such as 'sleep score' and 'wellness', it's against the maker's interest to advertise their (even common) flaws, or explain how they derive these figures. I guess the moral of the story is to use more reliable devices to measure what you depend on, and only use the tracker to provide a rough indication of what's going on. I certainly don't regret buying (and replacing) mine: it gives me what I want, more or less, despite its tendency to provided misleading readings under some conditions.

I should also say that as a watch it's more accurate than any other watch I've owned.

[Shiloh223]

I just find it weird that it reaches this two thirteen number and it is not
accompanied by any other symptoms that would usually accompany such a
number

[Gabbee]

Agreed without doubt, @Shiloh223. It's almost certain that your HR at the time was not 213.

In my case (using a C5) I was concerned enough to buy a Polar H10 strap which is generally regarded as accurate, and it proved to me that my genuine pulse was significantly lower than that shown by the C5 - eg 110 not 150. I was also concerned that AF (atrial fibrillation) might be the cause of the high readings but was assured in a cardiac forum that my ECG did not show signs of AF.

I suspect that both our high readings are due to problems in the processing of the HR data (possibly aggravated by irregular HR in my case). I would be really interested to see all the readings (including the 213).

I would love to see Fitbit/Google's take on this issue, but so far the silence has been disappointing.