Sleep times on Pixel Watch 2 completely wrong

[Arctic_Lyn]

I have used Fitbit trackers for years and have never had this trouble but ever since I switched over to a Google Pixel 2 smartwatch, my sleep start and end times are a constant 17 hours behind. I go to bed at 11 pm, it says start time of 6am. I get up at 6 am and it says end time of 1 pm. This has happened since day 1 of connecting my watch, it never did get the time right.

I haven't changed time zones and I've got my Fitbit app, phone and watch all set to automatic time zones which for me is MST (Canada) with no daylight savings time. I have tried all the other suggestions on the forum about playing with time zones, resetting the watch, uninstalling and reinstalling the app....nothing works.

I'm really frustrated at this point as nothing seems to work. Can somebody offer some new advice on how to fix this?

Thanks.
Lyn

[Gr4ndp4]

Hi, @Arctic_Lyn, welcome to the community, can you please provide a screenshot of the error? I'm running a PW2 on a Pixel8 Pro and do not replicate your problem. Before you do this check your Fitbit app on your phone and the PW are up to date. I'm running Version 4.08 (110025801) and Android 13 with a security update on 5th January 2024.

Have you tried factory resetting your PW2 & then going through the set-up procedure again? Try reloading the Fitbit app again be sure to clear the cache on your phone, delete the app & restart your phone before loading the app again.

Let us know the make, model & OS of your cellphone.

Cheers

[Arctic_Lyn]

Thanks for the reply.

I believe I tried all those steps before but I'll try them in the order that you've suggested and try again. I am not thrilled about resetting my PW2 to factory as I'd have to go through and set up all my apps from scratch. Almost as much of a pain in the butt as resetting the phone. I will try that if these steps don't work.

 

My phone is a Motorola Edge 2022, Android version 13. My phone is up to date on system updates as well.

[Gr4ndp4]

Hi, @Arctic_Lyn, the dark blue on the horizontal graphic line equates to "Deep Sleep". If you go to the top of the screen > months>time in sleep stages mine looks like this - 

and this -

For some reason where your sleep score is absent, the graph notes "Deep Sleep". On one hand, the times are completely wrong and on the days you get no score the data is up the chute as well. I think your best way forward if a complete reset fails, is to talk to "Customer Support" . Use the chat facility or phone for a prompt response. I've not seen these symptoms before and I suspect they will be new to CS, it would be a good move if you could prepare a note of what you have tried and the results so you can brief the agent.

I hope this is helpful.

Cheers

[Arctic_Lyn]

Thanks for the help. I had taken that screen shot just of sleep times to show the screwed up times. The 2 dark ones at the top, yesterday and today, the watch didn't register cycles. That happens quite a bit with the PW2, I guess it may not sit properly on my wrist at night. I do get sleep cycle tracking (well, at least for the nights it can get an accurate reading)  just the times are whacked.

I'll leave it be for tonight and see if the time corrects itself. If not, I'll take your advice on the other steps.

Thanks much!

[RiekoC]

Hello @Arctic_Lyn 

If & when you do a factory reset on your Pixel watch, make sure that you have a recent backup to use. The backup makes the factory reset process less painful, speaking from experience. Most of your apps & settings will be restored through the backup. If you have a cards in your Google Wallet app, I know you'll have to setup those again.

I believe Backup should be on by default. To check:

• Open the Pixel Watch app on your phone
• Tap on System
• Tap on Backup and restore. If the backup was enabled, you should see the date & time of the last backup.

[Arctic_Lyn]

Thanks Cross-country Runner. I'll have to make sure I've got a recent backup.

[Arctic_Lyn]

Well, I thought I would give it a few days to see if the problem rectified itself but nope, still screwed up on the time. I'll get in tough with CS I suppose as I've tried all the tricks that you folks have mentioned.

Thanks again for the help.