You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The deep timeline sections shows the temperature however it is most likely scalled wrongly -> there is a slight difference sometimes of the captured metrics but it usually is only within 7 to 9 degrees
What you expected instead
It should properly scale it
Steps to reproduce
Connect your whoop
Let it collect some data
See in deep timeline 7.6C
Strap log
I dont think its needed - i will attach one later if required
Before you submit
I attached my exported NOOP .zip (not a screenshot of the Live screen). If my bug is a clearly reproducible UI issue I described exactly how to see it instead.
I attached or pasted a strap log above — or my bug is a clearly reproducible UI issue that doesn't need one (e.g. a typo, a button that does nothing) and I've described exactly how to see it.
I checked the Troubleshooting guide — especially "history syncs but no data" (most often the strap isn't banking history to flash; charge it to 100% and reconnect).
I checked the FAQ and — if I'm on a WHOOP 5.0 / MG — the 5.0/MG status page, and this isn't an already-known limit (e.g. SpO₂, or recovery/sleep on the 5/MG).
I've left out anything personal (strap serial, account email, raw export).
Root cause found — this is not a °C/°F conversion bug.
The Add-Device wizard stores the strap's registry model label as bare "4.0" (AddDeviceWizard.kt:268), but all four skin-temp family resolvers compare the label against the full picker spelling "WHOOP 4.0" (FullDayChartScreen.kt ~360, RegistryDayOwnerSource.kt ~55, Repository.swift ~1452, IntelligenceEngine.swift ~1386). For a wizard-paired 4.0 the match always fails, so its samples get decoded with the WHOOP 5/MG raw/100 rule.
The arithmetic confirms it: a worn 4.0's raw skin-temp band is 760–865, and /100 gives exactly the reported 7.6–8.65 °C — 34 °C real → 8.46.
Other surfaces hide the bug because analytics gates absolute temps to the plausible 28–42 °C range; the Deep Timeline plots ungated, which is why it shows up only there.
This is the same registry-vs-hardcoded-label bug class as #172/#175 and #178/#179. Fix in PR #180, which centralizes label→family resolution into one documented resolver per platform instead of patching the four comparison sites.
I'm on 8.6.2 and it still shows 8-10c in deep timeline. It doesn't show anything on today->skin temperature. There it says import your history first. I'm confused - I never used whoop app, do I have to for this feature to work? Why does it show numbers on deep timeline then? Is it still bugged?
Activity
pagarsky commentedon Jul 10, 2026
Root cause found — this is not a °C/°F conversion bug.
The Add-Device wizard stores the strap's registry model label as bare
"4.0"(AddDeviceWizard.kt:268), but all four skin-temp family resolvers compare the label against the full picker spelling"WHOOP 4.0"(FullDayChartScreen.kt~360,RegistryDayOwnerSource.kt~55,Repository.swift~1452,IntelligenceEngine.swift~1386). For a wizard-paired 4.0 the match always fails, so its samples get decoded with the WHOOP 5/MG raw/100 rule.The arithmetic confirms it: a worn 4.0's raw skin-temp band is 760–865, and /100 gives exactly the reported 7.6–8.65 °C — 34 °C real → 8.46.
Other surfaces hide the bug because analytics gates absolute temps to the plausible 28–42 °C range; the Deep Timeline plots ungated, which is why it shows up only there.
This is the same registry-vs-hardcoded-label bug class as #172/#175 and #178/#179. Fix in PR #180, which centralizes label→family resolution into one documented resolver per platform instead of patching the four comparison sites.
Fix wizard-paired WHOOP 4.0 skin temps decoding on the 5/MG scale (ry…
Fix wizard-paired WHOOP 4.0 skin temps decoding on the 5/MG scale (ry…
WHOOP 4.0: learn per-device skin-temp anchor instead of assuming raw 826
Fix wizard-paired WHOOP 4.0 skin temps decoding on the 5/MG scale (#171…
Fix wizard-paired WHOOP 4.0 skin temps decoding on the 5/MG scale (#171…
WHOOP 4.0: learn per-device skin-temp anchor instead of assuming raw …
WHOOP 4.0: learn per-device skin-temp anchor instead of assuming raw …
igorbaikov commentedon Jul 12, 2026
I'm on 8.6.2 and it still shows 8-10c in deep timeline. It doesn't show anything on today->skin temperature. There it says import your history first. I'm confused - I never used whoop app, do I have to for this feature to work? Why does it show numbers on deep timeline then? Is it still bugged?
Don't name the model in the empty-state copy (#623 re-review)
Fix wizard-paired WHOOP 4.0 skin temps decoding on the 5/MG scale (ry…
WHOOP 4.0: learn per-device skin-temp anchor instead of assuming raw …
Resolve a non-WHOOP device's family from its brand, not a fall-through (
fix(ui): stop a non-WHOOP device inheriting WHOOP-5 empty-state copy (r…
fix(ui): stop a non-WHOOP device inheriting WHOOP-5 empty-state copy (#…
Fix wizard-paired WHOOP 4.0 skin temps decoding on the 5/MG scale (ry…
WHOOP 4.0: learn per-device skin-temp anchor instead of assuming raw …
Resolve a non-WHOOP device's family from its brand, not a fall-through (
fix(ui): stop a non-WHOOP device inheriting WHOOP-5 empty-state copy (r…
Stop Blood Oxygen promising a reading a WHOOP 4.0 cannot produce
ble: pick the battery source from evidence, not from a guess (#1623)