08-27-2020
19:53
- last edited on
09-03-2020
14:47
by
LizzyFitbit
08-27-2020
19:53
- last edited on
09-03-2020
14:47
by
LizzyFitbit
After the most recent update my zone minutes are not added up correctly. Although the graph and Average heart rate show that I reached cardio and fat burn levels of heart activity (shown in orange and yellow), all minutes are shows as below zones. I have an iPhone 11 and a versa 2. All devices are updated. I’m not concerned with with small gaps in data but the minutes do not add up correctly in reference to the graph. This happens even when there is no gap in data.
Moderator Edit: Clarified subject
09-05-2020
11:06
- last edited on
05-26-2021
06:15
by
JuanJoFitbit
09-05-2020
11:06
- last edited on
05-26-2021
06:15
by
JuanJoFitbit
Exact same issue, but when I log in to Fitbit.com on a web browser, the exercise zone information is accurate. Not sure how that is possible since the watch syncs with the phone which syncs with Fitbit's cloud, but it is 100% true. Yesterday, my phone logged just over 2 hours in exercise zone, but online, it shows almost 10 hours. Thanks for reporting this issue.
Same here, but when I logged in to Fitbit online (web browser), the exercise zone information is accurate, unlike the app info. Not sure how that is possible, but thought you'd like to know that somehow the watch syncs with the app which syncs with Fitbit and miraculously, the online version reports properly. Not sure how that is possible, but thought you'd like to know.
Moderator edit: merged reply
09-05-2020 11:18
09-05-2020 11:18
@Rachelbrunt29 wrote:Today’s been better started to record zone minutes but says I have hit 143 zone minutes but on breakdown still says 36 cardio zone and 72 fat burn which doesn’t add up it’s so confusing
Was that 36 minutes in Cardio and 72 minutes in Fat Burn?
If so, with Cardio counting double that would be 72 Active Zone Minutes for both Cardio and Fat Burn adding up to 144 Active Zone minutes. I could see it being 142 if during one particular "clock minute" you were more in Fat Burn than Cardio.
If it was 36 AZM in Cardio and 72 AZM in Fat Burn, then something is indeed fishy.
09-05-2020 19:46
09-05-2020 19:46
09-05-2020 23:15
09-05-2020 23:15
09-07-2020 17:32
09-07-2020 17:32
Hello everyone.
Thanks for you the information and screenshots provided. I'm sorry for the experience you're having as I understand how important this information is for you. Our team is currently investigating this situation and while I don't have further updates, I've forwarded your comments so the're informed of the impact this has caused you. I appreciate your patience and please know that your feedback hasn't gone unnoticed.
Let me know if you have another question.
09-07-2020 18:05
09-07-2020 18:05
09-07-2020 18:18
09-07-2020 18:18
Excellent news there! Did it just start working OK by itself or did you need to do a reboot of the tracker, your phone or both? I have a gym session later today so I'll go prepared if necessary!
09-07-2020 21:23
09-07-2020 21:23
The exact same thing happened to me..VERY frustrating! After my run last Sat. it showed I had 1 hr 5 mins PEAK & 3 hrs CARDIO. I then did the firmware update on my Versa 2 & it immed. changed ALL my zone readings to blue/below. And, since doing this update, every min of everyday since has shown blue/below regardless of the fact my heart rate readings get as high as 168 bpm & all the heart rate readings appear to be correct. As a result of all this, it shows I’ve had 0 active mins for the past 4 days.. CRAZY!
There’s nothing worse than programmers ‘fixing’ things that aren’t broke. PLEASE FIX THIS BUG ASAP FITBIT?! Or tell me how I can revert to the prior version where everything was working perfectly 🙄
09-08-2020 04:14
09-08-2020 04:14
09-08-2020 05:25
09-08-2020 05:25
Fitbit asked me to turn heart rate monitoring off and then sync, and then turn it back on and sync again. I did this and got all my proper readings on this morning's workout. Again I've no idea if it's coincidental but it might help someone.
09-08-2020 19:46
09-08-2020 19:46
I just updated my versa. I worked out today and at the top of the workout it is blue and says all minutes were below heart rate zones, but when you look below at the graph it clearly shows that my heart rate was in cardio and peak during my work out.
09-09-2020 17:41
09-09-2020 17:41
Thx! I did that & it now shows data under zone mins view but it’s not correct. The # of fat burn, cardio & peak mins don’t correlate to the heart rate graph readings. They aren’t displayed correctly under the heart rate view either. The heart rate graphs appear to be the same regardless of where you view them from but the fat burn, cardio & peak mins info (extrapolated from that graph) are still not correct anywhere as far as I can tell...
09-09-2020 23:52
09-09-2020 23:52
I opened this topic also in the German community w/o any feedback or resolution yet. So I am going to follow this one and just cross fingers....
09-15-2020 17:45
09-15-2020 17:45
Hi everyone. It's good to see you around the forums.
@cardiokristen and @yvonne2907, thanks for the update and sharing the steps that worked for you. I'm glad that your heart rate details are correct in the Fitbit app and I'm sure others will find your posts very helpful. If you need anything else, don't hesitate to let me know.
@NancyB and @MikeGoll, thanks for joining this thread and for every step tried prior to posting. I'm sorry that the heart rate zones aren't displayed correctly. Our team is aware of this situation and while I don't have further details, be sure that our team is working to bring a resolution to all our affected users.
I'll be around if you have another question.
09-15-2020 19:33
09-15-2020 19:33
Yep I am having the same exact problem. I have a two-day old NEW Versa 2 that only started showing these issues after I updated the app and Fitbit firmware. It's disappointing to see Fitbit code updates that "add" new features but break other ones in the process. If there is any way to revert back to the previous firmware version until everything is functional again let me know.
See here: https://imgur.com/a/zzBsXRN
The photo with the zones is from the day before I updated it (9/14). The second photo is from working out after updating my Fitbit firmware. No zones are showing even though my heart rate was higher in the second workout.
09-23-2020 15:34
09-23-2020 15:34
I have done 6 days of exercise only showing my minimum of 3. Each exercise is showing below zone which a lot of people have commented on the same problem but with no resolution. Seems to be after the firmware update. Yes I have uninstalled etc
09-24-2020
07:36
- last edited on
05-26-2021
07:05
by
JuanJoFitbit
09-24-2020
07:36
- last edited on
05-26-2021
07:05
by
JuanJoFitbit
And...Versa is not recording all my steps nor all the exercise minutes (even in below zone). Played 27 holes of golf & it only recorded 2hrs 45 mins of activity out of the 7.5 hrs I played. It captured 25,300 steps that day but I know that wasn’t correct either because I watched the APP record steps during activity & it missed many of them. Adding insult to injury, my battery life appears to be worse after this last update. I find my Fitbit to be pretty useless at this point 😡 Pls pass this along to programmers & advise on when these probs will be fixed?
Also...I’m unable to set a custom max heart rate. When I turn on ‘custom’ & enter a #, it’s immediately overridden & changed to ‘0’ (regardless of the # I enter).
Moderator edit: merged reply
09-24-2020 11:18
09-24-2020 11:18
@NancyB -
While that is a known issue with the iOS app, at least, there is a workaround.
You can change it in the Settings page in the Web Dashboard, save the change and sync your device. Of about a dozen people that have tried that when I recommended it on another thread, only one individual could not get it to take. Once person had to log out of the app and back in for it to take.
And you need to stay on top of it. The FitBit servers routinely reset the Custom Max HR override back to the "default" value of 220 - age. It has happened to me three times in the past 2 weeks.
Good luck.
09-24-2020 13:02
09-24-2020 13:02
10-03-2020 09:12
10-03-2020 09:12
I have this exact problem on my Ionic!