24H HR Data

[NoahMcE]

Hey @NoopApp, where can hourly heart rate data be viewed within the android app?

[NoopApp]

Hey @NoahMcE — it's on the Today tab (Control Center): a 24-hour heart-rate trend that plots your continuous HR across today in 5-minute averages, with the day's low / average / high underneath. It's read from the strap's own history, so it covers the hours the app was closed too — it shows up once you've worn and synced the strap today. If you don't see it yet, there's just no wear-data for today.

[NoopApp]

The 24-hour HR trend is real and ships on both platforms — it's built from your strap's own ~1 Hz HR history, not just live readings.

What it is: the Today screen shows a continuous day curve (5-minute average buckets since midnight) with Min/Avg/Max — built from the strap's stored samples, so it reads continuously even for hours the app was closed.

How it populates: via the automatic history offload — on connect + every 15 min, NOOP pulls the strap's banked HR records and commits them. Wear it all day with the app closed, open NOOP, let it sync, and the day backfills in.

The key gotcha (esp. 5/MG): the clock prerequisite. For the strap to bank HR history while you're away, it has to be clocked. NOOP sets the strap's clock on every connect — but an un-clocked WHOOP 5 doesn't write sensor data to flash at all, so an offload "succeeds" but returns zero records and the trend stays empty. So if your 24h HR looks sparse, the usual cause isn't a missing feature — it's that the strap spent that stretch un-clocked (e.g. right after the recent firmware update that reset 5/MG bonds — see the in-app reconnect guide). The fix is the same loop: reconnect so NOOP re-clocks it, then let a sync or two run and the day fills in. If you still see gaps after a clean reconnect + sync, grab a strap log — our diagnostics dump a hex sample of any frames that decode to zero rows, which is exactly what we'd need.

[NoopApp]

Quick recap in case it's useful, @NoahMcE — the hourly view you're after is the 24-hour heart-rate trend on the Today tab (Control Center). It plots your continuous HR across today in 5-minute average buckets with the day's Min / Avg / Max underneath, and because it's read from the strap's own banked history it covers the hours the app was closed too. It appears once you've worn and synced the strap today (no wear-data yet = nothing shown, rather than an empty axis).

One gotcha worth flagging if it ever looks sparse — especially on WHOOP 5/MG: the strap only banks HR history while it's clocked. NOOP re-sets the clock on every connect, but an un-clocked 5 doesn't write sensor data to flash at all, so a sync can "succeed" and still return zero records. If that happens (e.g. after the recent firmware update that reset 5/MG bonds), just reconnect via the in-app guide so we re-clock it, then let a sync or two run and the day fills in.

Did that get you to the data? If so, mind marking it as the answer so others can find it — and if you still see gaps after a clean reconnect + sync, grab a strap log and we'll dig in (our diagnostics dump a hex sample of any frames that decode to zero rows, which is exactly what we'd need).

[NoahMcE]

@NoopApp

4.0 Strap

Just for context before the overnight test, I had another look after your explanation and I believe the 24-hour HR trend is meant to appear somewhere on the Today tab, but I'm still not seeing it at the moment.

The app is currently showing "History synced just now" and the strap is bonded, however I still don't appear to have a 24-hour HR trend card or graph visible anywhere. I've attached screenshots of what I'm currently seeing on v1.72 in case that helps confirm whether the trend section is hidden until enough historical data exists, or whether it should already be visible.

What's encouraging is that the most recent logs look significantly healthier than the earlier ones. The trim cursor is continuing to advance across syncs, history offloads are occurring regularly, and the large numbers of decoded-to-0-rows warnings seen previously have almost entirely disappeared. There are still a few status=8 disconnects and reconnects during longer runs, but NOOP appears to recover from those automatically and continue syncing afterwards.

Given the trim is now steadily advancing and history is clearly being handed over more consistently than before, I'm interested that the 24-hour HR trend still isn't appearing yet despite "History synced" being reported. My guess is either there still isn't enough historical data accumulated for the trend to render, or there may be an additional requirement before that view becomes visible.

I'll leave everything connected overnight and report back tomorrow morning with the results, screenshots and a fresh strap log. If it's useful, I've happy to attached the latest pre-overnight log for comparison against tomorrow's run.

noop-strap-log (10).txt

Edit – the screenshot showing "-" for Live HR updated shortly afterwards and began displaying a value again.