03-28-2023
08:08
- last edited on
03-28-2023
09:57
by
MarreFitbit
03-28-2023
08:08
- last edited on
03-28-2023
09:57
by
MarreFitbit
A rant. It's now 16:03 (4:03pm) and my Fitbit is stuck showing the time as 13:56. I've looked at it several times and the display goes off when not in use but then the incorrect time is still showing when I raise my wrist. Could a watch possibly have a worse fault? I think not.
I have seen this happen before when I went abroad and the time zone changed but my Sense was showing the correct time after the clocks updated in the UK two days ago.
I assume the watch has lost synchronisation with the app on my phone since the phone is two floors away in my house. However, this should never happen and showing the correct time should not depend on synching with another device.
Any ideas?
Moderator Edit: Clarified subject
03-28-2023 08:40 - edited 03-28-2023 08:41
03-28-2023 08:40 - edited 03-28-2023 08:41
Have you looked at your timezone settings in the app? It's under your profile, App Settings, then Time Zone. Check your Location as well.
03-28-2023 09:45 - edited 03-28-2023 09:46
03-28-2023 09:45 - edited 03-28-2023 09:46
Thanks, yes I have and it was set to "Automatic time zone" (from network) as expected. My point was that, after a correctly set time change because of a change of time zone or daylight time status, the time should stay correct while I'm in that time zone (I haven't been anywhere since the clock change). My Sense has refreshed and now shows the correct time, but this problem could cause users to miss appointments, flights etc.
03-28-2023 19:58
03-28-2023 19:58
Hi @TyneBridges - some watches are faulty and lose time if not constantly synced.
If your watch lost 7 minutes in 2 days it is clearly faulty and needs replacing, if under warranty, or accept to have a good syncing all the time by being next to the phone all the time and making sure it can sync.
Author | ch, passion for improvement.
04-01-2023 01:11 - edited 04-01-2023 01:12
04-01-2023 01:11 - edited 04-01-2023 01:12
Thanks. It looks to me as if the problem wasn't with syncing but that the display hadn't refreshed, even after several "on-offs" of the screen. Once I switched to a different screen and then went back to the time display it did refresh but, for the Fitbit to call itself a watch at all, this really has to be automatic - that is, not to need any user intervention.