Pixel Watch 4 March 2026 Update: Why Your SpO2 and Skin Temp Sensors Stopped

If your Pixel Watch 4 stopped recording overnight Blood Oxygen (SpO2) and Skin Temperature right after installing the March 2026 update, your watch’s hardware sensors usually aren’t broken. Major Wear OS security and firmware updates frequently reset background Body Sensor permissions, pause Fitbit overnight tracking toggles, or leave Fitbit Health Services out of sync with the new OS build. Re-granting permissions and updating watch apps restores both metrics on your next sleep cycle.

Quick Answer

Missing SpO2 and Skin Temperature readings on a Pixel Watch 4 after the March 2026 update are usually caused by reset Body Sensor permissions, outdated watch-side Fitbit apps, or Battery Saver shutting off overnight LEDs. Re-enable Fitbit sensor permissions on both watch and phone, update all apps in the watch Play Store, and reboot before bed.

What Is Actually Happening?

Unlike heart rate—which your Pixel Watch 4 measures continuously all day—SpO2 (Blood Oxygen) and Skin Temperature variation are collected specifically during sleep:

  • SpO2 relies on red and infrared LEDs pulsing into your skin while you lie still asleep.
  • Skin Temperature tracks subtle overnight surface temperature changes against your multi-night personal baseline.

When the March 2026 firmware update installs, Android/Wear OS tightens privacy gates around background health sensors. If Body Sensors or Fitbit background permissions reset during the OS upgrade—or if the Fitbit watch app needs a matching Play Store update to talk to the new firmware—your watch keeps tracking steps and daytime heart rate normally while overnight SpO2 and Skin Temperature stay completely blank.

How to Tell Software Permission Lockout From Sensor Failure

Do this 15-second check before worrying about hardware failure:

  1. Take the watch off your wrist for a second and start a manual Heart Rate check or look underneath the watch while putting it back on.
  2. If the green optical LEDs still light up and your live heart rate appears normally in the Fitbit Today tile, your rear optical sensor array is alive. The missing SpO2 and Skin Temperature data is a permission, app-sync, or sleep-condition issue.
  3. If no rear LEDs light up at all and heart rate refuses to read even after a force reboot, you may be looking at a deeper sensor hub crash or hardware fault.

What to Do: Restoring SpO2 and Skin Temperature

Work through these steps during the day so your sensors are ready to record tonight.

Step 1: Re-Grant Body Sensor Permissions on the Watch and Phone

  1. On your Pixel Watch 4, open Settings > Apps & notifications > App permissions > Sensors (or Body sensors).
  2. Find Fitbit, Fitbit Today, and Google Health Services (if listed) and make sure each is set to Allow (or Allow all the time).
  3. Open the Fitbit app on your watch and scroll through the Health Metrics / SpO2 / Skin Temperature prompts—accept any newly reset consent cards. For specific permission prompts that refuse to stick, follow Pixel Watch 4: Bypassing the “Blood Oxygen Permission” Reset After March Update.
  4. On your paired phone, open Settings > Apps > Fitbit > Permissions and confirm Physical activity, Body sensors (if present), Location, and Nearby devices are allowed. Also check How to Reset the “Health Connect” Permission Hub on Android 16 if phone-side metrics stopped updating together.

Step 2: Update Watch Apps via the Watch Play Store

The March 2026 system update expects updated versions of Fitbit and Health Services on the watch:

  1. Open the Google Play Store directly on your Pixel Watch 4 (not your phone).
  2. Scroll down to Manage apps and tap Update all.
  3. Wait until all updates finish installing.

Step 3: Force-Restart the Watch to Reload the Sensor Hub

  1. Press and hold both the Crown and the Side button together for about 15 to 20 seconds until the white Google G logo appears, then release.
  2. Wait for the watch to finish booting so the low-power sensor coprocessor initializes cleanly.

Step 4: Check Battery Saver and Overnight Wear Conditions

Even with permissions fixed, Pixel Watch 4 will skip overnight SpO2 and Skin Temperature if certain bedtime conditions fail:

  • Turn off Battery Saver before bed: Battery Saver disables overnight SpO2 LEDs to preserve power. Charge your watch past 30%–40% before sleeping so it does not drop into automatic Battery Saver at 3:00 AM.
  • Sleep continuously for at least 3 hours: Short naps or badly fragmented sleep do not give Fitbit enough stillness to compute SpO2 and skin temperature averages.
  • Tighten the band: Wear the watch snug one finger width above the wrist bone so ambient room light does not leak into the optical sensor—see Troubleshooting Blood Oxygen (SpO2) “Measurement Unsuccessful” Errors for fit and cold-hand tips.

What to Check If Data Still Doesn’t Appear After One Night

Wait one full night of sleep (3+ continuous hours) after completing Steps 1–4, then open the Fitbit app on your phone in the morning and pull down to force a manual sync.

  • If overnight Sleep stages recorded, yet SpO2 / Skin Temp tiles remain blank: Check Troubleshooting Auto-Sync Failures on the Google Pixel Watch 4 and verify inside the phone Fitbit app (You > Health Metrics) that the SpO2 clock face or tile is enabled and didn’t lose regional/account sync.
  • If Skin Temperature starts showing up with odd spikes or dips: Keep in mind that room temperature, heavy blankets, and illness all move skin readings; review Understanding “Skin Temperature” Deviations: Fever vs. Environmental Heat to interpret your fresh baseline.
  • When to escalate: If your watch tracks sleep and heart rate cleanly for three consecutive nights after re-granting permissions, updating Play Store apps, and wearing the band snugly with Battery Saver off—yet SpO2 and Skin Temp still log zero readings—contact Google Pixel Watch Support so they can check sensor diagnostics or evaluate a warranty replacement.

Bottom Line

When SpO2 and Skin Temperature disappear right after the Pixel Watch 4 March 2026 update, the physical sensors are rarely broken. Re-allow Fitbit’s Body Sensor permissions on both watch and phone, run Update all inside the watch’s Play Store, force-restart the watch, and sleep a full night with Battery Saver turned off to bring both metrics back.