Sleep hours shifted into the future

[The_Belch]

My pixel watch 3 is reporting sleep hours that don't make any sense and are literally impossible. For example, last night it reported I went to bed at 4:30 am and woke up at 1:30pm (it is currently 10:30am and my watch is set to the right time zone). This happened the night before as well. It seems to be tracking my sleep properly I think it's just offset by some number of hours. It seems like this shift is consistently 4 hours into the future. Interestingly, for most of the year I live in a timezone that is 4 hours behind my current timezone. My home timezone in the android clock app is 1 hour behind my current timezone.

[RiekoC]

Hello @The_Belch 

Thank you for posting this in the Fitbit forums as recommended by the Pixel Watch PEs.

If you don't mind, please let us know what troubleshooting steps you've tried so far so that we don't repeat those. Also, how long have you been having this issue with your sleep start & wake times not being correct?

FWIW, I also had trouble with my sleep tracking on 24 Dec 2024. The app didn't have my correct sleep start time. Although I tried to edit my sleep log to fix it, I kept getting an error message that there was already a sleep log for the time. But there wasn't any log in the app for the time frame that I was trying to add. None of the troubleshooting steps that we recommend worked for me in this instance.

[The_Belch]

For troubleshooting, I've tried changing the watches timezone manually instead of automatically, same with the phone time zone, and the home time zone. I've also obviously restarted the watch. I'm not really sure what else to try, my watch is brand new I got it on the 22nd. The first night of sleep tracking was accurate however I only slept 3 hours from around 3am to 6am due to a flight. The flight took me somewhere which is one hour later than my home timezone. I'm thinking this might be related? I slept on the plane and it seems like it wasn't tracked although I'm not entirely sure how that is intended to work. Now since I've been here all my sleeps are shifted forwards exactly 4 hours.

When I manually edit the log it doesn't give me an error but it just hard shifts the time, for example if I actually slept from 11pm to 8am and it reports it as 3am to 12pm and I try to shift it back, I will have no sleep logged from 11 to 3 and the sleep logged from 3 to 8 will be the same as before it was shifted, i.e. the middle of my sleep not the start. I hope that makes sense.

[RiekoC]

Hello @The_Belch 

By any chance, do you use a VPN when you travel? I've seen users report that they had problems with their hours when they used a VPN. One user didn't realize that they still had the VPN enabled and their hours were fixed when they turned it off.

Although I'm not sure that this will work, you could try clearing the cache for the Fitbit app on your phone and force stop the app. When you re-open the app, try changing the timezone & location again to a different one, sync, then set your timezone & location back to automatic, followed by another sync. 

[The_Belch]

Hey! Thanks for the helpful answer. I am using a VPN but I'm connected to a server that has the same timezone as me. I will try disabling it overnight to see if that fixes things. I hope this isn't the issue because I would not like to stop using my VPN. I'll also try clearing cache and following those steps. I will get back to you in the morning with the results.

[The_Belch]

Update - The issue persists.

[RiekoC]

Hello @The_Belch 

Well, that's disappointing that the problem still persists.

I'm at a loss and don't have any other troubleshooting recommendations. I'm going to ask around and see if anyone else has a suggestion.

[The_Belch]

Thanks for trying you help. I'm flying home tomorrow so maybe that will fix it although if travel is the cause that's going to be a problem as I'll be flying back to school soon which is another time change!

[RiekoC]

Hello @The_Belch 

Did your time issue get "fixed" when you returned home?

[The_Belch]

It seems like it has. I just hope it stays fixed when I go back to school next week. If it doesn't I'll update this thread.