Water logged on device doesn't show in Fitbit app (RESOLVED)

[AlessFitbit]

Fitbit Update: 12/18/19

Hi everyone,

When this thread started earlier this year, the issue was that waterlogging on the watch was not syncing over to the Fitbit app. No matter what you would log, it just wouldn't show up in the Fitbit app and didn't sync the information over.

Now, we're seeing reports that waterlogging is syncing over, but it is the wrong amount of water that was logged onto the watch. To keep threads organized and on-topic, I'm now going to close this thread and move the conversation here: Water Logging syncs incorrect amount to app.I've already merged some posts from this thread into that one. 

If you're experiencing this new issue after updating to Fitbit OS 4.1, follow that thread for updates. 

---

Fitbit Update: 2/7/19

Hi everyone!

Thanks so much for your patience while our team continues to investigate these reports with water logging issues. If you haven't yet tried some troubleshooting steps, I'd recommend the following: 

• Sync your Versa with your mobile device
• Force quit and then restart the Fitbit app 
• Restart Today app on Versa and wait at least a minute 

I'll keep you updated, so please stay tuned! 

---

Fitbit Update: 1/24/19

Hey Versa Fam! 

Our team is still investigating these reports for water logs not syncing over to the Fitbit app after logging them on your watch. We appreciate your reports and feedback. 

If I receive any new information, I will update this thread so please stay subscribed. Thank you! 

[AlessFitbit · Accepted solution]

Fitbit Update: 12/17

Hi Versa Smartwatches family,

In the last firmware update Fitbit OS 4.1 (70.7.14), we implemented some fixes to improve waterlogging on the device. If you haven't already, please make sure you update to this new firmware which is packed with many new features and fixes. 

In addition, inside of the Fitbit app make sure that you check the TODAY app and that there aren't any pending updates for it. 

Lastly, make sure you have the latest version of the Fitbit app installed on your phone. It's important to always keep the app up to date to ensure the best Fitbit experience. 

We appreciate your patience while we rectified this issue. Please do let us know how it goes after updating to OS 4.1! 

[Fitlark]

Despite the notice of a new update, mine is still not working, in fact,
worse

[velw]

I checked this morning that I had the latest versions, and tried logging 10ml from the watch. It didn't seem to register on the chart immediately but it now shows up both there and on the app. Success (here, at least)! Thanks, Fitbit team. 

(The chart shows my average logged is 1ml rather than 10ml, but I'm guessing it's averaging it across all the days/weeks it didn't work!! XD)

[Ash30524]

I have had my watch 3 days. It's updated and still not working correctly. Super sucks since I spent alot of money on this device. 

[SkylineSi]

Following the update yesterday, Firmware and today app updated and it appears to be syncing straight away now. 

Please note, Fitbit tech support chat agents were not aware of this problem nor the update

[Lmsu18]

As It seems this issue will continue till Fitbit make a update,

meanwhile what I did for a solution was downloading an app called Ionic Water By Brian Ouellette, for me works great! 

you can edit shortcuts logs for the amount of water you want in FL Oz or ML, and automatically it synced with the app,

hope this could help you guys. 

[AlessFitbit]

Hi everyone,

When this thread started earlier this year, the issue was that waterlogging on the watch was not syncing over to the Fitbit app. No matter what you would log, it just wouldn't show up in the Fitbit app and didn't sync the information over.

Now, we're seeing reports that waterlogging is syncing over, but it is the wrong amount of water that was logged onto the watch. To keep threads organized and on-topic, I'm now going to close this thread and move the conversation here: Water Logging syncs incorrect amount to app.I've already merged some posts from this thread into that one. 

If you're experiencing this new issue after updating to Fitbit OS 4.1, follow that thread for updates.