11-11-2020
14:13
- last edited on
05-18-2021
12:30
by
DavideFitbit
11-11-2020
14:13
- last edited on
05-18-2021
12:30
by
DavideFitbit
I am in fact tracking my Bicycle Ride together with Fitbit App and Strava on my iPhone after selecting Bike ride on the Versa 2 screen starting my activity. But the calorie count for a 1.5 hour 16 mile ride that should normally be in my case (6'4" 220lbs) around 1100 calories burned, my Versa 2 gets everything right except for the calories, it reports 447 calories.
When I use my Powerwatch2 with GPS it gets it right with 1148 calories. Why is that ?
Moderator edit: format
11-13-2020 01:02
11-13-2020 01:02
It happens with me too. When I select weights or work out mode in my fit bit, it gives very low calories burned metrics. I have compared it with Apple watch and there is always a difference of 100 to 150 calories burnt. Some time back both watches used to show same metrics. but now my versa 2 shows a very low calories after my workout.
11-13-2020 01:30
11-13-2020 01:30
Yep, same for me. Did a 6km walk this afternoon and 200 less calories than it should record. Sort out your updates Fitbit!
11-13-2020 07:26
11-13-2020 07:26
Well, sofar I resisted the urge to search for a competing watch, but since Google took over I think this is
now becoming a no-brainer. I thought their AI would help things, but either they do not give a hoot
or their stuff sucks.
11-13-2020 10:01
11-13-2020 10:01
well if it would be 200 cal less we could talk, but in my case I have now tracked my rides every day. This morning I rode 13 miles and the official bike calculator with my weight and my height and my stats tells me that I burned 912 calories for the time it took me and the distance. Now the Fitbit should know this even better as it has in addition to all that the heart rate etc.
Well instead of 912 calories it reported 377 calories, this is 41% of what it should have reported. This is a joke.