Repository navigation
docs: a paired phone as a presence key over BLE HID - #367
Merged
Merged
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.
The Bluetooth LE guide's HID section gains a short paragraph and snippet: a board serving
bledev.hidwithencrypted=Trueknows when a bonded phone comes into range, because the phone reconnects by itself, with no app.Run on an ESP32-P4 (MicroPython 1.30 preview) with a Galaxy S21 on Android 14: the snippet as written saw the phone arrive on pairing, leave and come back across a Bluetooth off and on, and leave on unpair. A separate probe timed
conn.encryptedacross four arrivals: False whenserve()returns, True 291 to 424 ms later on bonded reconnects.