Repository navigation
[hrv] HRV & Autonomie - activated nights only doesn't track naps during the day #92
Description
NOOP version
8.4.0-staging
Platform
Android
OS version
16
WHOOP strap model
WHOOP 4.0
Where the data is coming from
Live Bluetooth (strap connected)
Test Centre profile
HRV & Autonomic
What happens
I activated hrv readings continuously, but nights only. I didn't get any tracking of naps during the day the last two days.
This night there was a nap tracked. So I decided to deactivate nights only and my nap after noon was tracked spot on.
What you expected instead
Just to let you know, maybe it's related to the settings.
Steps to reproduce
Strap log
<details><summary>Strap log (last 40 lines, redacted)</summary>
14:51:50 [display] frameSummary frames=60 mean=12.0ms p95=11.2ms hitches=1 worst=66.3ms threshold=33.0ms
14:51:51 [display] frameSummary frames=60 mean=12.0ms p95=11.1ms hitches=1 worst=66.3ms threshold=33.0ms
14:51:51 [display] frameSummary frames=60 mean=12.0ms p95=11.1ms hitches=1 worst=66.3ms threshold=33.0ms
14:51:52 [display] frameSummary frames=60 mean=12.2ms p95=11.2ms hitches=1 worst=77.5ms threshold=33.0ms
14:51:53 [display] frameSummary frames=60 mean=12.0ms p95=11.1ms hitches=1 worst=66.3ms threshold=33.0ms
14:51:54 [display] frameSummary frames=60 mean=11.6ms p95=11.1ms hitches=1 worst=44.2ms threshold=33.0ms
14:51:54 → TOGGLE_REALTIME_HR payload=01
14:51:54 [display] frameSummary frames=60 mean=11.8ms p95=11.1ms hitches=1 worst=55.3ms threshold=33.0ms
14:51:54 [connection] frameTiming type=COMMAND_RESPONSE t=1783515114s
14:51:54 [connection] frameTiming type=EVENT t=1783515114s
14:51:54 [connection] frameTiming type=REALTIME_DATA t=1783515114s
14:51:55 [display] frameSummary frames=60 mean=12.0ms p95=11.1ms hitches=1 worst=66.3ms threshold=33.0ms
14:51:56 [display] frameSummary frames=60 mean=11.8ms p95=11.1ms hitches=1 worst=55.3ms threshold=33.0ms
14:51:57 [display] frameSummary frames=60 mean=13.1ms p95=11.1ms hitches=1 worst=132.8ms threshold=33.0ms
14:51:58 [display] frameSummary frames=60 mean=16.0ms p95=16.8ms hitches=1 worst=111.0ms threshold=33.0ms
14:51:59 [display] frameSummary frames=60 mean=18.2ms p95=16.7ms hitches=1 worst=116.6ms threshold=33.0ms
14:52:00 [display] frameSummary frames=60 mean=18.5ms p95=16.7ms hitches=1 worst=132.9ms threshold=33.0ms
14:52:01 [display] frameSummary frames=60 mean=16.6ms p95=17.4ms hitches=1 worst=99.8ms threshold=33.0ms
14:52:01 [display] frameSummary frames=60 mean=12.0ms p95=11.1ms hitches=1 worst=66.4ms threshold=33.0ms
14:52:02 [display] frameSummary frames=60 mean=14.2ms p95=44.2ms hitches=3 worst=88.5ms threshold=33.0ms
14:52:03 [display] frameSummary frames=60 mean=11.4ms p95=11.1ms hitches=1 worst=33.2ms threshold=33.0ms
14:52:04 [display] frameSummary frames=60 mean=11.7ms p95=11.1ms hitches=1 worst=33.3ms threshold=33.0ms
14:52:05 [display] frameSummary frames=60 mean=17.9ms p95=17.8ms hitches=2 worst=155.6ms threshold=33.0ms
14:52:06 [display] frameSummary frames=60 mean=13.6ms p95=22.1ms hitches=2 worst=88.5ms threshold=33.0ms
14:52:06 [display] frameSummary frames=60 mean=11.8ms p95=11.2ms hitches=1 worst=44.2ms threshold=33.0ms
14:52:07 [display] frameSummary frames=60 mean=14.7ms p95=27.7ms hitches=2 worst=99.7ms threshold=33.0ms
14:52:08 [display] frameSummary frames=60 mean=17.2ms p95=16.6ms hitches=1 worst=49.8ms threshold=33.0ms
=== Capture check ===
universal: present (dayOwner day=)
sleep: present (gate run=)
connection: MISSING (clockDrift )
workouts: MISSING (session event=)
display: present (dataVolume dbRows=)
import: MISSING (import parser=)
steps: MISSING (stepsEst )
battery: present (battery series=)
recovery: MISSING (charge score=)
hrv: MISSING (hrv rmssd=)
INCOMPLETE: missing connection, workouts, import, steps, recovery, hrv
bundle ok files=2 report=present meta=present screenshot=present crash=present leaks=0
</details>
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).
Activity
royabby365 commentedon Jul 8, 2026
@pilleuspulcher-blip this is working as intended but it could have used clarification. I've submitted a bug fix to change the verbiage but the behavior will remain the same. There's potential for this to be an additional feature in the future but for now, I think the priority is existing feature improvement and bug fixes while we are still trying to pick up where the original developer left off.
fix(issue #92): clarify overnight-only HRV setting and manual HRV rea…
Merge pull request #95 from royabby365/fix/issue-92-hrv-naps-overnigh…
Merge pull request #120 from ryanbr/ios-hrv-overnight-copy-92
iOS/macOS: clarify overnight-only HRV setting copy (ryanbr#92)
Release v8.5.0: changelog + version bump
Oura: bound history-drain with full-pull fast-exit (fix ryanbr#92 in…
[Oura Ring] - one-packet framing refactor + sleep-phase fix + honest …
Merge pull request ryanbr#95 from royabby365/fix/issue-92-hrv-naps-ov…
iOS/macOS: clarify overnight-only HRV setting copy (ryanbr#92)
Merge pull request ryanbr#120 from ryanbr/ios-hrv-overnight-copy-92
Release v8.5.0: changelog + version bump
[Oura Ring] - one-packet framing refactor + sleep-phase fix + honest …
[Oura Ring] - one-packet framing refactor + sleep-phase fix + honest …