New Versa 4 Hourly Activity Not Tracking

[Trexie]

Day 2 of using my new Versa 4 and it has stopped tracking my Hourly Activity on the app. I’m getting reminders to move, and completing the 250 steps, but the app shows that I have remained stationary for 5 hours!  Very frustrating. I tried restarting my device, turning Bluetooth on and off, and logging out and back in to the FitBit app. Nothing has worked. 

[Guy_]

Hi @Trexie - for move hours to show in the app the watch must sync properly and it seems it's not. See Why won't my Fitbit device sync?

It does take a while to appear though.

If you want to follow your hourly steps more precisely you can install the SimpleClockPro clock face from the Gallery tile of the Fitbit App.

This will show directly on the watch face, your active Hours count, steps done (or to do) for the hour and full hourly steps history for every hour of the day, with multiple reminders to move to be sure to succeed.

The installation requires the watch syncs so is a good test to see if that is working as well.

[Trexie]

@Guy_ Thanks for the info on the clock face, but I’m more interested in getting the all my data to accurately sync with the app than in precise step counting at this point. My Versa 4 continues to have trouble syncing (ie I have to try multiple times, restarting via a long hold of the side button, turning phone and Bluetooth on and off). Also, some data syncs right away while other data does not. After multiple tries today, for example most of the data finally synced, but the “Longest Stationary Period” in Hourly Activity is completely inaccurate, (showing me as Stationary for over 7 hours). What can I do to have this fixed?

[Guy_]

@Trexie - some data has to be calculated before it will show in the Fitbit App, depending on how well it syncs and how busy the servers are it can take some time.

The new V4 Fitbit App isn't as robust as the previous release and versions of it can have different issues and that generally can't be fixed by you.

Sometimes the Fitbit App loses connection with the watch and sometimes the move hours  summary isn't in sync with the underlying data but this generally resolves itself over time.