09-10-2015 11:40
09-10-2015 11:40
FitBit is apparently using the number of water log entries as the number of glasses of water, rather than calculating the actual number of glasses of water from the day total.
At first I thought this was an issue with the sync from MFP, but looking back at my history from before I started logging with MFP, I have found that each and every one of my water logs was counted wrong.
Below is a screen shot from the Achievemint export for August 23 to September 9 with two columns added at the end. The second-to-last column is the correct data.
Answered! Go to the Best Answer.
09-14-2015 13:32
09-14-2015 13:32
Thanks for the explanation @nconantj, this seems to be something that needs to be worked out with the developers. Let me see what i can do. 🙂
09-13-2015 09:51
09-13-2015 09:51
Hi @nconantj i would recommend (If you have not attempted it already) revoking access from mfp to your fitbit account and the relinking both accounts again.
To manage your linked Apps, please follow these instructions:
1. Log in to fitbit.com
2. Click on the gear icon on upper right corner of your screen.
3. Go to settings
4. Choose "Applications"
5. Click on "Revoke access"
After doing this, relink both accounts.
09-14-2015 11:44
09-14-2015 11:44
I'm sorry, but that is just not going to solve the problem.
MFP sends a summary (a single record) that says how many glasses of water I recorded with them. Fitbit recognizes this in all their graphs.
The problem is in Fitbit's programming of the sync with Achievemint. Fitbit is saying to Achievemint "I have 'X' records for this user, so this user has had 'X' glasses of water." What Fitbit should be saying to Achievement is "I have 'X' fluid ounces for this user, so this user has 'Y' glasses of water," where Y=X/8.
To work around the problem, I've gone to recording all my water intake on a per-glass basis. If I drink 80 fluid ounces of water, I make 10 records of eight fluid ounce glasses. Since Fitbit sees this as 10 records, the sync to Achievemint is 10 glasses.
09-14-2015 13:32
09-14-2015 13:32
Thanks for the explanation @nconantj, this seems to be something that needs to be worked out with the developers. Let me see what i can do. 🙂