01-29-2021
07:40
- last edited on
01-29-2021
17:08
by
MarreFitbit
01-29-2021
07:40
- last edited on
01-29-2021
17:08
by
MarreFitbit
The weather app has worked well for about a year. Now it won't show any data and claims it needs a sync. No luck. Ideas?
Moderator Edit: Clarified subject
Community Moderators ensure that conversations are friendly, factual, and on-topic. We're here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
Hi there @Oldhiker, welcome to the Community Forums. Thanks for sharing the details about the issue with the Weather app.
As per the description of your post, it seems that your watch hasn't synced to your Fitbit app and that would explain why it has stopped updating the weather on your Versa 2.
To see when was the last time sync of your watch, tap the Today tab > your profile picture > your device image. If you see it hasn't synced yet, sync it.
We've released Android app version 3.37.1 to address syncing issues. Please update your device if you are experiencing issues syncing, please see Why won't my Fitbit device sync?
Also, make sure that the mobile phone you're using is included here Which phones and tablets can I use with my Fitbit watch or tracker?
Please keep in mind that when a device is not supported and does not meet the require OS we cannot guarantee its functionality with the Fitbit app. It might work at a certain time and then it can stop working out of nowhere after an update. This is because the app is not optimized to that device and any change could impact the performance.
Let me know how it goes.
Was my post helpful? Give it a thumbs up to show your appreciation! Of course, if this was the answer you were looking for, don't forget to make it the Best Answer! Als...
I am currently experiencing the exact same problem. The weather app won't display the weather although my watch and phone sync fine (esp. after the latest app update). I am also using a weather clockface that had stopped displaying the weather. Everything worked fine until recently. I suspect the latest firmware version (35.72.1.9) may have something to do with this issue...