WHOOP 5.0 raw HCI capture — where to submit? (docs reference #174, which doesn't exist)

[digitalerdude]

docs/WHOOP5_DEEP_DATA.md points to this issue as the tracking issue for the WHOOP 5/MG
deep-data (R22) unlock:

Tracking: #174

That issue number doesn't currently resolve (404) — the repo's highest issue/PR number
right now is #102. The doc also says:

Even better: a Bluetooth HCI capture of the official app syncing a night's history
shows the deep packets actually flowing and their layout. See the capture guide in
the wiki.

The wiki link (github.com/ryanbr/noop/wiki) redirects straight back to the repo home,
so there doesn't seem to be a public capture guide there either.

I have a WHOOP 5.0 strap and would like to help by providing a raw HCI/BTSnoop capture
of the official app doing a full history sync, so the type-0x2F deep records can get
decoded. Before I do that, could someone confirm:

1. What the correct tracking issue number is (or should this issue become the new one?)
2. The expected capture format/tooling (I was planning an iOS Bluetooth diagnostic
   profile capture → .pklg/btsnoop_hci.log, opened in Wireshark)
3. Where to upload the capture file (attach here, or is there a preferred drop point?)

Happy to also fix the stale #174 reference and wiki link in
docs/WHOOP5_DEEP_DATA.md once the right number/link is confirmed.

[ryanbr]

Great catch, and thanks for offering to help — this is exactly the artifact the deep-data work needs.

On the stale references: you're right. #174 was an issue number inherited from the original upstream repo (now deleted), so it 404s here, and there's no public wiki. I've just fixed docs/WHOOP5_DEEP_DATA.md on main — the #174 links now point to this issue (#103), which is the tracking issue for HCI captures + new deep-record layouts, and the "capture guide in the wiki" is replaced with the actual method. So no PR needed on your side for that, though further capture-guide additions are welcome.

Your three questions:

1. Tracking issue: WHOOP 5.0 raw HCI capture — where to submit? (docs reference #174, which doesn't exist) #103 — this one. It's now referenced from the doc.
2. Tooling: your plan is exactly right — iOS PacketLogger via the Bluetooth diagnostic profile → .pklg (or Android Developer Options → Bluetooth HCI snoop log → btsnoop_hci.log), opened in Wireshark. That's the same iOS-HCI approach the judes.club write-up used.
3. Upload: attach it here (NOOP is offline-only, so there's no private drop). One privacy note: an HCI log carries your strap's BLE MAC + the full sync traffic — no account credentials (BLE is device-local), but device identifiers are present, so it's worth filtering the capture to just the WHOOP peripheral in Wireshark before posting.

What's most useful: capture the official app doing a full night's history sync (not just live HR). NOOP already decodes the R22 enable sequence and the known channels; the gap now is the un-decoded record layouts — the type-0x2F deep records and any 5/MG history record types NOOP still skips. A full-sync capture is where those show up. Thanks again!