06-18-2020 17:13 - last edited on 09-16-2020 10:17 by MatthewFitbit
06-18-2020 17:13 - last edited on 09-16-2020 10:17 by MatthewFitbit
The thread is basically what it says on the tin. I prefer to set my custom max heart rate (CMHR) to 220 because I get more accurate calorie burn information when the tracker isn't telling me I'm in "fat burn" while I'm sitting in front of my computer.
I've had my CMHR set like this for a few months, but when I was showing it to a friend yesterday it reset it and now refuses to save my CMHR. I've tried setting it lower as well, but it still resets.
When I first got my Charge 3 I was being told I had burned 3000 calories during a day of minimal activity. I was spending significant portions of my day in "fat burn" zone according to it. That was clearly wrong and if I'd eaten at "maintenance", I would have ballooned. After changing the CMHR it settled down and gave me much more reasonable data. So far today its been giving me seemingly accurate data, but I'm still eager to gain some certainty that it will work as desired.
06-19-2020 11:11
06-19-2020 11:11
I have the same problem on Charge 4. The Custom Max Heart Rate doesn't save and always changes to 0. Very frustating.
06-19-2020 23:55
06-19-2020 23:55
Exactly! That's what happens to me as well. I wonder if it's a bug with the current version of the app. Next time it updates we should see if we can set it.
06-21-2020 03:22 - edited 07-21-2020 23:01
06-21-2020 03:22 - edited 07-21-2020 23:01
It’s definitely a bug since it used to save before.
If you make the change on the web dashboard instead of on the app it saves for a couple of days, but eventually reverts to the default (220 minus age) again.
As an update on Fitbit iOS app 3.25.1 (977) this bug appears to be back as I had to enter Custom Max Heart Rate on the web dashboard since the app wouldn’t save the change.
it shouldn’t be that difficult for the developers to fix, one would think!
Greetings,
08-04-2020 08:56
08-04-2020 08:56
I have same problem with charge 4 and iphone X. I can fool it for few hours by changing on android device and sync from iphone but it changes back to 220-age after few hours.
10-10-2020 07:36
10-10-2020 07:36
I have had the same issue with my Versa Lite since May 2020. I used to be able to fix it using the web browser dashboard and it would stick sometimes for months, but now it is not working at all with the new firmware update. I deleted a couple of apps that deal with HR Zones thinking they may interfere with this feature but that didn’t help. I am using the fitbit to pace at low heart rates for health reasons and really depend on being able to customize the max HR (and thus the zones). I am much more able to make decisions about my activity based on how much time I’ve spent in each zone. I think it’s time they fix this issue!!!
10-14-2020 20:41
10-14-2020 20:41
Hi Staceyllc,
I can best describe the option to change the heart rate values as “moody”. Sometimes it stays for a week or so after editing it from the Dashboard, other times the change is removed straightaway.
In my case I need the Max Heart to read 200 instead of the age-adjusted default of about 160.
It seems that any editing performed for the Heart Rate is negated after an update to the Fitbit
iOS app. BTW, my Ionic has the latest firmware.
Let’s hope for a fix soon!
12-15-2020 03:59
03-01-2021 12:14
03-01-2021 12:14
I know this is a temporary work around but I just changed the year I was born so that 220 minus the plugged age would equal the maximum heart rate I want.