Issues with Pixel Watch 3 – Step Count and Hourly Movement Reminder

[Maunin]

Step Count Issue:
Step count increases on the device but syncs to a random number in the app, then decreases by few steps.

Hourly Reminder:
No reminder at 50th minute and completed steps vanish after a few minutes.

Has anyone faced this? Found a fix?

[Maunin]

In Detail:

I purchased the Pixel Watch 3 about a month ago, and since then, I’ve been experiencing the following issues:

1. Step Count Issue:

   • After movement, the step count increases on the device (e.g., from 1000 to 1500). However, when syncing, the sync is successful, but the Fitbit app shows a random number (e.g., 1460) instead of 1500. After a few moments, both the app and the device show a decrease in the step count, often dropping by few hundread steps (e.g., down to 1370).

2. Hourly Movement Reminder:

   • Unlike my previous Fitbit device, I no longer receive the hourly reminder at the 50th minute of the hour. Additionally, even when I complete the required 250 steps, the device acknowledges this with a success message, and it’s reflected in the app initially. However, after a few minutes, the steps disappear, and the hour block shows almost no movement completed.

I’ve raised these issues with support three times but have not received any satisfactory resolution. The support team has mentioned waiting for an update (for which there’s no timeline), and they claim the issue lies with the app, not the device itself.

Has anyone else experienced similar issues, and if so, have you found any resolution?

[gdio53]

@Maunin 

For the Hourly Movement reminder, can you verify that reminders to move is turned on, and the time and days are set correctly?
Tap the battery icon at the top left of the Today screen, then select Google Pixel Watch 3.  Select Reminders to move and verify that Get reminders is toggled on..  Check the Start and End time, and days are set to what you want.

[Maunin]

@gdio53 thanks for response but let me make my issue clear regarding the hourly reminder.

1. The hourly reminders are turned on, and I do get them, but not exactly at 50 minutes (like 09:50, 10:50, 11:50). Instead, I get them a few minutes late, like 09:53, 10:51, or 11:59.
2. Sometimes, after completing the 250 steps, they disappear when the hour changes, and the previous hour shows as missed, as if I didn’t hit the movement target.

[gdio53]

@Maunin 

Have you trued restarting your phone & watch?

[Maunin]

Well yes, 

I have tried watch restarting, app restarting, log out from App, clear cache and then delete app followed by reinstalling it with previous version 

Also as per the support team, I waited for update of the app but even after yesterday's update issue persists.

I have highlighted this issue to support team and they have identified the issue but they neither have workaround nor they have visibility that when it can be fixed. 

[RiekoC]

Hello @Maunin 

After one of the recent Pixel Watch updates, we noticed a delay in app notifications. Like you, I've experienced a delay in getting my hourly notifications. I've even got a notification to move after the hour.

The app notification delay issue has been escalated to the team and they are working on fixing the problem. So far, we haven't seen a timeline for the fix.

The team is also aware of the issue that results in step count discrepancy between the device & the Fitbit app. Again, like you, I've experienced where my Pixel Watch 3 shows that I met the 250 step hourly goal for a specific hour. Then, after syncing with the app, both the watch & app show that I didn't meet the hourly goal. This also happened with my Pixel Watch 2. I've gotten into the habit of doing extra steps & syncing with the app to confirm that I met the goal. It's annoying and I still miss some of the hours.

The step count discrepancy issue seems to be a rather complex problem. This issue affects multiple Fitbit devices; it's not consistent; it's not easily reproducible. I don't envy the team who is investigating this problem and figuring out the eventual fix.

At this point, there's no troubleshooting that we can recommend or workaround as the issues are on the Fitbit side.