08-21-2019
02:21
- last edited on
11-17-2020
10:40
by
MatthewFitbit
08-21-2019
02:21
- last edited on
11-17-2020
10:40
by
MatthewFitbit
In early July I went for a run and my heart rate peaked at 153. A few days later, and every time since, my heart rate has peaked - for a sustained period - at 200 or more. I'm 59. I'm either dead or Charge 3 is giving me rubbish data. I dug out my old Polaris and - no surprise - on the Polaris my heart rate peaked at 152.
I have read the thread regarding this problem. I have reset my watch, switch off and on the heart rate (oddly when it was switch off the laser was still flashing) and the problem persists. I wear my watch on my non-dominant wrist, facing out, a finger space back from the bone as recommended.
I did update the Charge 3 software recently but didn't log the date to know if that was the problem. As far as I can see the issue reported in the above thread was not resolved and those customers were walking away from Fitbit. How can this be fixed please?
Moderator edit: subject for clarity
Answered! Go to the Best Answer.
08-29-2019 06:28
08-29-2019 06:28
After quite a few exchanges with technical support as they got the data they needed to understand the problem, Fitbit were quick to conclude that the Charge 3 I have is faulty and are sending a replacement. Have to compliement the support team on thier work and customer care.
08-22-2019 04:50
08-22-2019 04:50
08-22-2019 06:57
08-22-2019 06:57
Thanks for your response. Unfortunately this is not the solution.
I have seen this post previously and tried moving the watch further up the arm, it made no difference to the result. And it does not explain the sudden 55bpm jump in recorded HR; the watch, arm and placement was unchanged through this period.
I would note that when running it is difficult to keep the watch secured in this postion if it is not clamped in place, which this links rightly states one should avoid.
08-23-2019 07:05
08-23-2019 07:05
I appreciate the update @VIBlack.
Since the instructions provided didn't work, I've gone ahead and escalated your case to our support team, for them to take a deeper look at this. Please keep an eye on your inbox for further instructions.
In the meantime, let me know if you need anything else.
08-29-2019 06:28
08-29-2019 06:28
After quite a few exchanges with technical support as they got the data they needed to understand the problem, Fitbit were quick to conclude that the Charge 3 I have is faulty and are sending a replacement. Have to compliement the support team on thier work and customer care.
08-30-2019 06:04
08-30-2019 06:04
Those are great news, @VIBlack.
I am glad to hear that you will be receiving a replacement. At the moment of receiving it, you can follow the instructions provided in the article: How do I set up my Fitbit device? to set it up.
Happy stepping! 🙂
05-16-2020 10:49
05-16-2020 10:49
Hello Alejandra and VIBlack. I am a 66 year old jogger and have had exactly the same problem with my Fitbit Charge 3 for approximately one year now. My jogging heart rate is nowhere near accurate and often shows sustained rates near 200 bpm. Based on previously accurate readings from my Charge 2 HR and treadmill heart rate sensors, I would say the Charge 3 often reads 50-60 bpm high. I have tried rebooting, updating and ensuring the tracker is worn properly but the problem still persists. Heart rate tracking is the primary reason I have worn a Fitbit for the past five years but I am seriously considering a move to a different brand if Fitbit cannot correct this problem.
05-17-2020 02:21
05-17-2020 02:21
Fitbit replaced my watch, but the replacement was still way over the top. I have got into the habit of running with a polaris chest strap monitor and fitbit 3 to compare and the polaris also has me reaching impossible HRs, so I've also got into the habit of ignoring it and taking the extra calorie count as icing on the cake. Fitbit have recently had to replace the replacement when the screen developed the smudge of death. Great service from the company, shame their products are so poorly built.
08-09-2020 07:15
08-09-2020 07:15
This is my problem as well. My Fitbit is completely inaccurate when I run, showing me running at 175 when an ePatch monitor shows that number is wildly inaccurate.
08-25-2020 10:51
08-25-2020 10:51
I started having a similar issue today. I was sitting in bed and it showed in the cardio zone. I checked my other monitor and I was in my resting zone. It is also giving me a massive calorie bonus on my Lose It app. Just trying to figure out what is happening.
Thanks,
beth ziegler