help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Water Log History Shows Zero Daily Values

Replies are disabled for this topic. Start a new one or visit our Help Center.

‎03-20-2023 10:27 - edited ‎03-20-2023 10:29

‎03-20-2023 10:27 - edited ‎03-20-2023 10:29

When you click on the water log tile and go to the page that shows the daily history for each week, all values for each day is zero until you click on a day.  Once you click on a day and come back, that day then shows the value in the high level page.  You have to do this for every day in order to get all the values to show correctly.

Best Answer
0 Votes
1 REPLY 1

‎03-20-2023 11:30 - edited ‎03-24-2023 04:08

‎03-20-2023 11:30 - edited ‎03-24-2023 04:08

On further investigation I believe this may be tied to correctly updating in history log the values from the integration to Hidratespark.  At least for Today row in the history log, I manually entered water in the Fitbit app and it shows up where the Hidratespark values do not.   The interesting thing is the high level water tile includes Hidratespark value.   If you click the water log tile and then click on today and come back, it will update to include Hidratespark values. 

 

So it looks like the integration the hidratespark data is being pulled in but the date is being ignored and it is not being correctly included in the lower level pages by the fitbit app.

Best Answer
0 Votes