Skip to content

Sleep not recorded — backfill times out, strap reports mismatched time #700

Open

Description

@ekadranata-ai

NOOP version

9.0.2

Platform

iOS

OS version

27.0

WHOOP strap model

WHOOP 4.0

Where the data is coming from

Live Bluetooth (strap connected)

Test Centre profile

Not a test-mode bug

What happens

Every once in a while, no sleep is recorded. The live log shows backfill timing out. In the app, Charge shows "–" and sleep sessions are either missing or wrong:

Last "recorded" real sleep was 14 July, yet the graphs show sleep data for 15 and 16 July.
On 17 July the app briefly showed Charge 20% with ~2h of sleep. After editing the sleep time, the charge data disappeared again.
The persistent warning "Your strap isn't accepting the alarm — the strap keeps reporting a different time than NOOP sends" appears, disappears after a full recharge + re-pair, then returns after the next night.
A nap on 20 July was recorded correctly, with correct timing.
The strap buzz alarm fires at the correct time, even while the app claims the strap's time doesn't match.

Update 21 July: the nap on 20 July was recorded correctly, but the following night again produced no sleep and no Charge — so a correct nap does not indicate the issue is resolved.

What you expected instead

Overnight sleep sessions are recorded and backfilled normally, without repeated non-working recharge/re-pair cycles.

Steps to reproduce

  1. Charge strap to 100%, disconnect, re-pair — the strap-time warning disappears.
  2. Wear strap overnight.
  3. Open app in the morning: no sleep recorded (or partial/incorrect), backfill times out in the live log, and the strap-time warning has returned.

noop-strap-log-260717-0716.txt
noop-strap-log-260721-0937.txt

Image Image Image Image Image Image Image

Strap log


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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions