Issue with calories burned when performing intensive exercise

[RyMiller]

Has anyone experienced an issue with the Sense retrospectively changing and capping the calories burned per hour during high intensity exercise?

If we take Sunday as an example, I went on a 65 mile cycle, with varying heart rate throughout.  When I initially check calories burned, it looks how I would expect - periods of more cals burned during higher heart rate periods and likewise dips when the heart rate goes down.  

However, after 30 mins or so post exercise, the calorie tracker updates and shows a flat number which is much lower than it should be (much like how it shows sleep or periods of BMR when you don’t have the watch on) and erases the previous numbers.

I didn’t have this issue with my Fitbit Versa 1 that I just upgraded, it seems to be only happening since I moved to the Sense.  

Any ideas?

Thanks,

Ryan 

[JohnnyRow]

Did you manually log the bike ride?

[RyMiller]

I did not, I let it track it on its own.  I track mileage on Strava directly, so just want to link miles travelled to calories burned is all.  

I did attempt to use the exercise function on the watch linked to Strava originally but I find that the button is too sensitive.  It auto-pauses and starts randomly throughout the cycle, I’m assuming if part of my wrist touches the underside of the button.  

[JohnnyRow]

That's the right way.  I was just checking because manually logging it disregards you recorded heart rate and makes it same value throughout.

[RyMiller]

Understood, thanks for clarifying.  

Could it be that Strava is assuming calories burned and pushing that back to the Fitbit app, causing it to update and stripe the divided assumed figure across?

Strava doesn’t show that it assumes calories, but currently I can’t think what else it would be.

[JohnnyRow]

No idea, don't use Strava.  You could ask on Third Party Integrations board as many Strava users there.

---