Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Can you point me to a link with some information about this bug? I'm a current Flex owner and would love to learn about this.


I don't know if it's posted anywhere, here's what support told me (after a few back and forth emails and escalations):

> There is a setting on every users profile that allows enabling or disabling of Calorie Estimation. This function gives users an estimation of calories based on their profile history. Its best suited for users that maintain the same relative activity level daily, in case they forget to wear their trackers some of the time. Calorie Estimation used to be enabled by default, but due to some discrepancies such as yours, it is now disabled by default for new users until we can improve the technology.

> I recommend that you turn the Calorie Estimator off on your profile.

So the feature that adjusts your calorie burn based on your activity broke calorie burn estimation. If you turn the feature off.... everything works as expected. Note that I fit perfectly into the "maintain the same relative daily activity level" category.

They knew about it, they turned it off for new users because it caused problems, they left it on for existing users and didn't tell them even if the bug was occurring.


http://help.fitbit.com/articles/en_US/Help_article/How-does-...

"Calorie estimation is used when no activities are logged or data is synced." If that's accurate, then it only "broke" calorie burn estimation on days when you didn't wear your Fitbit.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: