11-06-2020
23:06
- last edited on
11-07-2020
04:05
by
JuanJoFitbit
11-06-2020
23:06
- last edited on
11-07-2020
04:05
by
JuanJoFitbit
Hi,
I have been working on training in different heart rate zones and tonight I was excited because towards the end of my run I actually got my heart rate up to 174 for 90 seconds. At least that's what my Charge 3 said but then after syncing it said my highest heart rate was 155. I was really disappointed. How do I fix this? Also yes my settings are set to track my heart rate all that is on.
Moderator edit: updated subject for clarity
11-07-2020 04:05
11-07-2020 04:05
Hi @Shannon19881, welcome to our Fitbit Community. I'm sorry to hear that your Charge 3 is not tracking your heart rate accurately. I totally understand how you feel about this.
Please restart your Charge 3 as described in this help article. After this, check out this help page, which explains how your Fitbit device tracks your heart rate.
Finally, monitor your tracker during the next 24 hours and see if the issue gets fixed.
Keep me posted on the outcome.
11-08-2020 19:50
11-08-2020 19:50
Thank you, I will try this..
11-09-2020 02:54 - edited 11-09-2020 13:33
11-09-2020 02:54 - edited 11-09-2020 13:33
This is an age-old problem and there are several posts spanning a year or two with an identical and yet unresolved issue. Phones and watches should not need to be rebooted etc and it should just work a claimed. I have never had to do this EVER, but do have the same problem.
Essentially the problem lies with the watch/phone s/w in that one or the other or both override if power is low. The pic above shows my watch and iPhone 6 running fine when power on both is high and the only phone app running is the FITBIT app. It will continue and run even until low levels of charge on both but the problem arises once stopped and when either several apps are running or both have low charge levels, where no matter what, they will not synch. Even when both or either is fully recharged it will not synch but then out of the blue, they will suddenly synch. Also, there is no way to control this and therein lies the root of the problem.
I find that it works best when the FITBIT App is the only phone app operational in which case, as shown above, "real-time" phone app updates occur but which are not possible to stop unless the phone is taken out of communication range. I have to kill all apps and then start the FITBIT App on the phone and I get real-time updates.
The user needs to be provided with an option to override this (like the manual synch) but it appears FB have rather chosen to preserve battery life.
The problem is when real-time updates start there is no means to control this and this what is lacking. A "real-time update or synch" option is required but then live with the consequences. It will start and stop at will, out of the blue, whether required or not.
FITBIT are renowned for providing very polite but rather useless feedback, on this issue, and seemingly have no intention of resolving what for me is a somewhat trivial issue.
It begs one to ask whether any moderator has actually used or tried this out?