feat(gfps_service): Add Google Fast Pair Service #161
Merged
Conversation
This file contains 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
* Add google/nearby submodule under external folder * Add gfps_service component implementing the device specific google/nearby support as well as a wrapper service for GFPS * Add gfps_service example * Update and rebuild docs (and clean up some extraneous files) * Update CI
finger563
added
enhancement
|
✅Static analysis result - no issues found! ✅ |
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.
Description
Motivation and Context
Now that we have a BLE server (#157), being able to pair quickly and with a nice interface (supporting app matching) would be great. On Android, this can be provided by using the google:nearby/embedded framework and supporting the Google Fast Pair Service (GFPS). This PR adds support for that. GFPS doesn't preclude standard settings-menu-based pairing, but offers an alternative and is based on proximity of the android device to the bluetooth peripheral. It also still supports standard pairing on iOS as well.
NOTE: you will have to register your own device on the google nearby devices dashboard.
NOTE: this uses NimBLE as the BLE stack of choice. If you want to see a bluedroid implementation, see finger563/esp-gfps-example
How has this been tested?
Building and running the new example on a QtPy ESP32s3.
Screenshots (if appropriate, e.g. schematic, board, console logs, lab pictures):
Types of changes
Checklist:
Software
.github/workflows/build.ymlfile to add my new test to the automated cloud build github action.