This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Vivosmart HR: Daily calorie burn suddenly very low

Former Member
Former Member
I've been wearing the vivosmart HR for 2-3 weeks now, taking it off only to charge. Up until yesterday I was getting 2300-3300 calories burned for the day and it seemed pretty consistent with how active I was that day. Yesterday my calorie burn was a touch over 2000 and today @ 2:30pm I am only at 1100 calories burned. I am 23 female, 232lbs and 5' 8". I have lost about 15 lbs since I started to wear the vivosmart but my weight has been syncing successfully from MyFitnessPal.

The night before last I did the software update on the device and then yesterday Garmin Connect was down all day. Anyone else experiencing this?
  • Former Member
    0 Former Member over 9 years ago
    Hi, I've also had this issue today. I wondered where the Stone option has gone for tracking my weight too?

    Thanks
  • Former Member
    0 Former Member over 9 years ago
    Same thing on fenix3. At least for me it looks like it's only computing my resting calories based on the St jeor bmr formula.....and not multiplying it by 1.2 which it usually does.

    This means I'm showing 350 calories burned less per day the last 2 days. Frustrating because it throws off mfp adjustments!

    Garmin any update or explanation of this?
  • Former Member
    0 Former Member over 9 years ago
    I have been experiencing the same thing. It looks like it started on Friday 4/1. My resting calories is off and is lower than normal. As mentioned previously it is off by a factor of 1.2. Really weird and disappointing.
  • Former Member
    0 Former Member over 9 years ago
    I updated my app Friday and thought maybe my lower resting calorie counts were because of that. I also turned 30 the same day so I thought it did a recalculation due to metabolism. But I'm over 500 resting calories lower than I was on Friday. I'm really hoping this is resolved soon!