Harden WHOOP BLE protocol capture layer - #1
Open
goamorim wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR pushes the current local WHOOP Vault BLE/protocol work from
whoop-vault-ext/whoop-vaultto GitHub.It focuses on making the local BLE backend more robust as the reference layer for the upcoming fully-local iOS app:
Why
The UI/iOS PR is moving the product toward:
WHOOP strap → iPhone CoreBluetooth → local packet parser/rebuilder → SQLite vault → local UI.
For that to be safe, this repo needs the Python BLE/reference implementation to be stronger and better-tested. This PR makes the BLE/protocol layer a better oracle for the Swift/iOS port.
Validation
Ran locally from
whoop-vault-ext/whoop-vault:Result:
Notes
No DBs, logs, exports, virtualenvs, caches, or runtime data are included.