Bug or problem with band? -this chunk carried no sensor records (strap console/diagnostic output) — normal, nothing to persist

[yjp7vv4929-hash]

Hi,

Wore my old 4.0 over a couple of nights now, just to make sure I wasn't being impatient.

In the noop app, my live HR, and live HRV seem to work, but noting populates into the Today, or other tabs.

I've attached three logs, because I've also tried it over a few versions.

Any help appreciated, love the work you're doing.

noop-strap-log.txt
noop-strap2-log.txt
noop-strap3-log.txt
noop-strap4-log.txt

[NoopApp]

Thanks for the kind words — and for attaching four logs across versions, that's exactly what makes this diagnosable. I read all four, and they tell one consistent story.

What's happening: your live HR and HRV work because those stream straight off the strap in real time. But in every one of the four logs, each history sync completes yet hands over only the strap's console/diagnostic output — no sensor records. You can see it in the repeated "this chunk carried no sensor records (strap console/diagnostic output)" line, and the strap's trim cursor barely moves (≈118,447 → 118,499 across a whole session), which means it has essentially nothing stored to give. So HISTORY_COMPLETE fires, but there's nothing to populate Today / Sleep / Recovery with.

Why: this isn't a NOOP decode bug, and it isn't you wearing it wrong — it's the strap not banking history to its own flash. A WHOOP 4.0 only records to flash once its internal clock is set and it has enough charge; if that clock has drifted or lost sync, the strap will still connect and stream live HR, but it won't save the per-night history that any app could later read. (NOOP is even sending SET_CLOCK in your logs — but the strap needs a full charge to re-settle its clock.)

The fix for this state:

1. Put the strap on its charger, take it to 100%, then leave it charging another 30–60 minutes — this lets its clock re-settle.
2. Reconnect to NOOP and wear it for a night.
3. After that night, a good sync will start banking. On v2.0 (just released) the log now shows a persisted N rows (M with motion)… line when it does, so you'll know the moment it's working. You're on 1.94/1.95 — worth updating.

In the meantime, if you want your past history right away, importing your WHOOP export in Data Sources backfills it instantly, independent of the strap's state.

More detail (this is the most common reason recovery/sleep don't appear): the Troubleshooting guide. If a full charge + reconnect still doesn't get it banking, reply with a fresh log and I'll dig deeper. 🙏

[NoopApp]

Quick recap of the fix for anyone landing here: in this state the sync completes but the strap hands over only its console/diagnostic output — no sensor records — which means the strap isn't banking history to its own flash. That's a strap clock/charge condition, not a NOOP decode bug.

The fix:

1. Put the strap on its charger and take it to 100%, then leave it charging another 30–60 min so its internal clock re-settles.
2. Reconnect to NOOP and wear it for a night.
3. After that, a good sync starts banking — on v2.0+ the log shows a persisted N rows (M with motion)… line the moment it does. (Worth updating to v2.2.1 while you're at it.)

If you want past history immediately, importing your WHOOP export in Data Sources backfills it independent of the strap. Closing with the fix — if a full charge + reconnect still doesn't get it banking, reply with a fresh log and we'll reopen and dig deeper. 🙏