Spinning Cardio Load Always Shows Zero

[ggatel]

Others like walking and rowing are fine.. Please Fix

[gwapogreg]

I have a similar issue. Low to Zero cardio load registered for spinning or when riding, whilst it registers fine when I walk my dogs. Definitely broken. 

Fitbit Sense. 

[RiekoC]

Hello @ggatel & @gwapogreg 

I saw a Moderator post from yesterday (07 Jan 2025) stating that an update to the Fitbit app will start rolling out soon (this week?) and includes general issue fixes for the Cardio Load and Target Cardio Load. The updates tend to rollout in waves. Keep checking your app store for the update and install it when it's available to you.

Hopefully, the update will fix the Cardio Load inconsistencies.

[ronsans]

same, when are they going to fix this?!

[RiekoC]

Hello @ronsans , @ggatel , @gwapogreg 

Based on the user reports I'm seeing, version 4.34.1 hasn't fixed the issue with spinning/biking and Cardio Load.

Please submit your issues using the Feedback option in the Fitbit app:

• Tap on your picture in the upper right of the Today page in the Fitbit app
• Tap on Feedback in the menu that opens
• Complete the prompts & submit

Although it's likely that you won't receive a reply, the team receives & reviews the feedback reports.

[RiekoC]

Hello @Cmatznermason 

Were you not able to use the Feedback option in the Fitbit app? What error/message did you get?

Several users have reported that they had to uninstall then re-install the Fitbit app to get their Cardio Load working. Have you had a chance to try this?

[Jozolarozo]

It’s still not working and deleting and reloading the app didn’t help. I sent feedback. Very frustrating. It’s hard to use this feature for targets if it is not picking up the exercise with heart rate in the target zone just because my arms are still. 

[bde1]

Cardio load for spinning not working - received cardio load of 6 for 50 minute spin with 49 minute in vigorous and peak zones. Fitbit app version is 4.35 Android 15 on Pixel 9, using Pixel Watch 3 for heart rate. 

I am not sure how this got through product testing - spinning being one of the most popular cardio exercises! The issue has been raised since release of pixel watch 3 in 2024 and no fix yet?

Can you please dedicate some resources to fix this - it will make alot of your customers both present and future happy! Thanks

[hovdeo]

i hear you - got same issues. cannot use cardio load for anything reasonable the way it is working today. nice gimmick and barely that, at best.

did 2 hrs on the indoor bike trainer this morning, 5x10' threshold intervals which is a fairly hard session. 188 active zone minutes fitbit says but just 80 on cardio load. avg HR 130 (charge 5) vs 138bpm with garmin strap. max HR 161 (charge 5) vs 165 with garmin strap. TSS 157 on trainingpeaks

when i compare to an older session, running - 1 hr, avg HR garmin strap 137, max 168bpm, charge avg 157bpm (?????) peak 175bpm (not a chance), 122 active zone mins, and 225 cardio load, similar readiness as today

gym sessions, 75 min, avg HR 115 - 120bpm with peak of 140 - 145bpm - cardio load 80 - 120 go figure

is the cardio load an attempt to create a fitbig-pixel version Training Stress Score (TSS) at TrainingPeaks with a slight adjustment for readiness score? is hand wrist based HR readers too inaccurate to do what they try to achieve with cardio load?

now it seems to be an interesting idea but hardware and algorithms do not seem to be able to deliver.

[bde1]

Can someone from google support please respond to this issue. You also need to update your help as it should state that cardio load does not work for spinning activity. A notice similar to the one you publish for swimming would be honest and upfront - especially for future customers to make an informed decision based on functionality that actually works. Thanks.

[GrannyAdams]

Still mot able to get spinning to register more than a very low cardiac load. Also now not able to manually log workouts. Not happy! I've tried uninstall ingredients and reinstalling the app, restarting the Sense 2, re-pairing the watch to my phone....nothing has worked.

[ccstarr]

Even months later this still doesn't work

Fitbit app on my Pixel Watch 3 tracks the workout perfectly (heart rate, calories etc, except for Cardio Load - The centrepoint of Fitbit's methodology

How can it still not have been fixed even months later 

Other workouts track cardio load

Spinning isy main exercise, so this is a real downer on Google Fitbit & Pixel Watch fitness tracking via Fitbit

[Petterhebbe]

Is demotivating getting higher cardio load from walking to the gym than one hour hard work on the spin bike. Next watch will not no pixel unless this'll is fixed. I love statistics so this is important for me.

[Mg1977]

Same issue here.  Versa 3.  Pretty frustrating when you do hours of spinning and the feedback is that you are in danger of undertraining...

[alexthecat]

@Mg1977 I've been using the Cardio Load feature since September 2024 on my Pixel Watch 3. I haven't encountered this problem with Cardio Load and I spin regularly. I wear my Watch on my ankle when spinning though. I wonder if that might work for you too. I have no idea. It's just a suggestion.

[bde1]

That is a great idea as I have read in forums that the low cardio load while spinning is due to lack of movement detected by watch on wrist. Any issues with heart rate readings on ankle? I will give this a try next spin. Cheers.

[ChrisMos]

Same here in March, every Run gets me 0 Cardio Load

[GrannyAdams]

Since the update I am also unable to manually log workouts, or edit any auto-detected exercise.  Anyone else having that issue?

[alexthecat]

@bde1 I've been spinning with Fitbits on my ankle for years and not had any problems with it. That includes the original Sense, which is essentially the same as your Versa 3, with a third-party band that I got on Amazon.

I try to position the sensor in the part of my ankle that would correspond to where I would check my pulse in my wrist. I do sometimes get weird HR data for the first few minutes, but that happens with the device on my wrist too.

[hovdeo]

@alextried ankle for the first time today, per your suggestion. did 1h45min on the turbo trainer with 3x 12' LT1 - light-medium session. got some Cardio load but zone mins was a bit low - HR reading came at 101bpm avg vs. 119bpm avg on garmin chest strap. bit much of a difference. see if i find a better placement to close the gap but similar to difference when using wrist area.

whilst cardio load was up, it was still a funky ratio between zone minutes (92) and cardio load (78) when compared to the ratio between the two when just doing an easy walk or even light yard work. and it is an even funkier ratio when doing HIIT/vo2 or threshold intervals - cardio is then relatively lower compared to the registered zone minutes. in my simple mind, i would have expected higher zone minutes, more intense sessions, to result in a relatively higher cardio load given the effort/"cost" associated with such sessions.