Sense 2 not tracking calories or hourly activity properly

[jengall]

My Sense 2 isn't properly tracking calories or hourly activity.  Re: calories, I usually average about 2,600 calories burned a day, and by 10am I'm usually up around 1,800, having gone for a 5 mile walk in the morning.  I walked as usual this morning but Fitbit thinks I have burned only 577 calories.

For hourly activity, it's showing as 0 hours with 250+ steps (should show 7am and 8am at least).

I've restarted my Fitbit, manually closed the app, restarted my phone - no change.  Yesterday, it all worked normally.  What else should I try to get it back to normal?

[JohnnyRow]

Check your weight is approximately correct.

Check you are getting heart rate readings.

[jengall]

Thanks Johnny.  Weight is correct and I am getting heart rate readings.

[jengall]

Hi, so I didn't get an answer to this and would love to hear from others.

The other day when this happened, it took most of the day but then the missing calories/hourly activity eventually showed up.  Today, the same thing happened - the device and app were missing calories and hourly activity for hours after I went for my morning walk.  They did eventually show up, but it's annoying because I cannot then use that information during the course of the day to make decisions about food and exercise, as I am used to doing.

So I'd love if someone has a way to prevent this from happening!  The Sense 2 is only about a year old, so it can't be that it is worn out already.

[JohnnyRow]

That is valuable more information to know that the data is showing up later in the day, and changes the whole situation.

Are you talking about readings from the Sense 2  or from the phone app?

[jengall]

On both the Sense 2 and on the phone app, the data is not showing up until later in the day.

[JohnnyRow]

On the watch, do the calories show right on the clockface or do you have to scroll to another screen to see them?  Is it a clockface by Fitbit? Name?  Do calories eventually get added all at once or just gradually extra increases?

[jengall]

It is a Fitbit clockface - "SpO2 Waveform."  I have to swipe once to get to the "Today's Activity" screen that has the calories. 

The calories seem to get added all at once.  It's not like there are 0 calories and then suddenly a lot - it's like the Fitbit is recording the minimum calories per hour with a steady low amount recorded per hour, until hours later when suddenly all the calories are in their proper place on the graph of the day (higher calories for the hours when I was exercising and lower for the times I was sedentary).  This happened on 3/6 and today, 3/9, but on 3/7 and 3/8 it recorded as usual.

Thank you so much for all of your help!

[JohnnyRow]

I was trying to figure out if you were getting this info directly from the watch itself or from the phone app, because sometimes the phone display doesn't update.  I know in particular that often happens for the hours with 250+ steps. For that, the data is recorded correctly but the phone redisplay just doesn't always update fully.  I have found that can often be corrected by doing left arrow back to yesterday, then back to today's display, and it redraws the hours correctly.  Not ideal but often fixes the graphic.  Don't know if same  happens on calories.  That's why I was trying to figure out where you were reading calories.  It looks like SPO2 WaveForm does not show calories on main page but a nearly similar clockface, just "Waveform" without the SPO2" shows calories on the main face if you wanted to try that even for just a few days, just to watch the calorie growth more easily to see if calories are increasing correctly on watch but just not on phone app, which would make more sense to me.  If they are actually not increasing as expected on watch itself, then I am totally stymied.

Hope that all made sense.

[jengall]

Thanks.  I will try switching the clock face to watch the calories more closely, but for sure yesterday and the other day, the calories on the Sense 2 itself were wrong, not just on the Fitbit app - they were wrong on both.

Thanks for all of your help.  Do let me know if you can think of anything else that might fix it!