Spinning shows 0 minutes for all heart rate zones

[r1gging]

When I look at a workout I just completed in the app, my heartrate seems to have been tracked accurately but the zones say 0 all the way through. Has anyone run into this/have a fix? I contacted support and they said it's because autotrack conflicts with manual tracking and clobbers the data, but I then disabled autotrack and this still happens when I manually track a workout.

I'm using the Pixel Watch if that's relevant here.

Moderator edit: Subject for clarity.

[RodrigoMFitbit · Accepted solution]

@r1gging Welcome to the forums. Thanks for your post about the heart rate information on the Fitbit app.

Thanks for the explanation and the screenshot. That has happened to me before but it was only a one time issue and it was with tennis, if I remember correctly. I will have to check again. However, it has been working with my last workouts. Pleas make sure that your Fitbit app is up to date. 

Open the Google Play Store and look for the Fitbit app. If there is an update available, please proceed with it. 

If the issue persists, I recommend you stay in touch with customer support. They will help you out. Have a nice day!

[Glade82]

Pixel Watch, Andorid App. Both up to date and restarted.

Run exercise triggered from the watch when away from home without the phone and without cellular connection.

Heart rate seems to have recorded correctly, but for the last two days the HR zone has not been recognised correctly.

Normally I exercise in the gym with phone(data connection available) and the zones are recognised. Not sure if that is relevant?

Any Ideas? Thanks!

[Glade82]

I still have this problem even after speaking to Fitbit support.

I think it happens when the watch does not have a data connection. 

Maybe tomorrow I will take my phone with me when I run outside and see if it helps.

 

[Carbashian]

I don't think having the phone with you matters. All my workouts are tracking as 100% below zones when that is clearly not the case. 

[walk_on_by]

This same thing just started happening to me -- and it's been consistently wrong for about the last week.  Before that, zone minutes worked; now, it seems to think I'm in only in the fat burn zone very briefly and never rise above that despite the Heart Rate Zones (these are the defaults -- I haven't changed them) clearly showing I should be in one of Fat Burn, Cardio, or Peak most of the time.  I have the latest FitBit app (last updated about a month ago) and a Pixel Watch and phone (both also fully up-to-date).

I did try Fitbit Chat to get help -- they were of no use.  They say there's a new release of the app due next Tuesday (March 9), but they couldn't say if this was a known problem that was being fixed.  Any ideas?

[walk_on_by]

I found a fix for this problem -- I did a force stop on the Fitbit app and cleared all storage (cache and data), then restarted the app (at which point, it had to download a whole bunch of historical data).  On my next walk, Heart Rate Zones were correctly computed again.  At least I'll know what to do if this happens again.

I think I know what got the app into this state, too -- I was on a walk where my watch was very low on battery and it went into extreme battery saving mode (and stopped recording heart rate).  I put it on the charger as soon as I got home (it was at 2%) and didn't stop the walk until hours later.  That was the last walk with valid Heart Rate Zone minutes (up to the point where it stopped tracking Heart Rate).