The Pixel Watch’s integration with Fitbit has some teething problems, with some users reporting that the watch vastly overestimates the number of calories they burn, some by as much as three times what they were used to. A post from Fitbit community moderator Rodrigo M. says the problem affects “many” users, but there is an easy way to fix it.
One of the main selling points of the Pixel Watch is its integration with Fitbit’s health and fitness ecosystem, which collects data such as calories burned, heart rate, VO2 max, sleep tracking, and so on, and presents it in an accessible way.
It means the Pixel Watch has to be as good as the best Fitbitand similar to many of the best running watches when it comes to his fitness credentials. That Fitbit integration is often the first thing shown on promotional material for the Pixel Watch, but the fact that many people have early issues with it shows that the Google team may not have fixed all the kinks.
A Fitbit Community Member (opens in new tab) said: “The Pixel Watch vastly overestimates my calorie burn. I switched from a charge 4 to the pixel watch and my Kj burned from exercise has tripled for the same number of steps. A 5km run at ~30mins pace with the charge 4 was about 400kj and with the pixel watch is over 900. Yesterday the watch said I burned 5900 cal despite walking only 7000 steps and no workout did.
Another user on the same thread said “My first full day with the Pixel Watch and I’m comfortably 1500 calories left too”. These are the messages that prompted Fitbit’s response stating that this is not an uncommon issue and that a fix is underway.
Luckily, if you’ve just bought a Pixel Watch, it’s good to know there’s a quick fix. Fitbit says you can restart your Pixel Watch using the instructions on Google’s WearOS support pagewhich should solve the problem.
Analysis: More Fitbit issues abound
It seems that all Fitbit devices are known for experiencing some sort of software or hardware failure over their lifetime.
Whether it’s the high-profile Fitbit Ionics story being recalled after users were physically burned from overheating their tires, the Problems with Bluetooth disconnection and battery consumption of Charge 5, or Versa models being blocked for the latest updates, there seems to be a recurring pattern. It’s not all the devices in the range, but enough to make headlines.
The Pixel Watch is the first example of Fitbit tech being used on a WearOS watch, so it’s understandable that there could be some teething problems here. Honestly, if it’s something a quick reboot can fix rather than waiting for the Fitbit developers to roll out an update or recall the device, Pixel Watch users have gotten away with it easily.