08-29-2023 21:20
08-29-2023 21:20
I recently (yesterday) had to have a procedure on my heart due to heart flutter.
I put on my charge 5 after getting home and found the readings were high again, 120+. I thought would wait until the morning to phone my doctor, even the overnight rates did not go below 75.
I have a garmin with heart strap and a finder heart rate/oxygen monitor. It tried those and my rates were as expected mid 60s to early 70s.
I took the charge 5 back to the shop and they replaced it, got it home and paired it up, initially things seemed ok, I did the firmware update and now I have the same issue.
Sometimes the rate would drop to 70 but if I stand up it jumps to 130+ immediately, the other devices go up a few beats but the charge 5 can be up to 60 beats out. It now just sits at 120+ even though my other devices put my heart rate in the 60s.
08-29-2023 21:34 - edited 08-29-2023 21:35
08-29-2023 21:34 - edited 08-29-2023 21:35
Just for curiosity, try taking your pulse manually by feeling you pulse rate at your wrist with your finger, watching a clock and see how that correlates to Fitbit and the chest strap. I say that because the heart strap and Fitbit are actually measuring 2 different things. Usually they are essentially the same, but with heart rhythm abnormalities, they can differ. The chest strap is measuring the heart's electrical signal, and Fitbit is hopefully measuring the blood flow at your wrist. With everything working in sync, they should be the same, but with some heart rhythm issues, they can differ. That said, I expect the Fitbit reading is off, but it is still worth trying.
I hope your procedure, perhaps catheter ablation (?), fixed your problem.
08-29-2023 21:42
08-29-2023 21:42
I just had a cardioversion to put it back into rhythm.
I tried what you suggested, on my wrist I counted 37 (for 30sec) so approx. 75.
The fitbit (which I took off to just prior to testing manually) was at 142.
08-30-2023 10:41
08-30-2023 10:41
So that check seems to verify that the Fitbit reading indeed was in error.