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

Nutrition app doesn't put me in a calorie deficit

I am testing out the Nutrition App in Connect+ for the first time. 

I have told it that I have a weight loss goal, but it is currently telling me I can eat 2932 calories today. That is nearly 200 calories above what Garmin predicts I will have burned by the end of the day, so not at all conducive to weight loss. 

I usually use Cronometer, which gives me a calorie deficit and adjusts based on my calories burned in a day.

From what I can gather, Garmin Nutrition is taking my Daily Calories Goal and adding my Activity Level with my average daily active calories, but if my actual active calories on any given day are below my average then it has me eating in a surplus, despite the fact I've told it I want to be in a deficit. 

Am I missing something here? I have also selected the option to Auto Adjust my goal based on activity...

  • Same here. 

    Mine is set to use the Active Calories setting based on my data (1,104cals) and gives me a target of 3,535cals for today (after logged exercise) - and I've got it set to lose .75kg a week.

    My watch says my active calories are 1,313 (20km run) plus 1,278 rest, with a projected total of 3,250 for the day. Not sure how the nutrition tracking will have me losing weight when it's offering me more calories than I've burned, let alone allowing for a deficit? 

    Surely something isn't right with the daily calorie goal calculation?

  • I seem to have fixed this by setting my activity level to 'Sedentary' and switching on 'Auto Adjust Calorie Goal'. It now puts me in a ~500 calorie deficit based on what I'm set to burn that day.

  • Having real problems with the nutrition app - the total consumed is greater than all the meals I have loaded!?  Seems to be a poor version or mfp - which rope course you can’t use with Garmin once you’ve signed up for Connect+.  Just rubbish.

  • This did work for me also, nice find as a workaround until fixed.  Thanks for sharing.