-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[ESP32]: Add way to configure scan response.
- Loading branch information
1 parent
367a0c6
commit bdeec26
Showing
4 changed files
with
51 additions
and
0 deletions.
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
# Bluetooth Low Energy (BLE) | ||
|
||
# Nimble: scan response | ||
|
||
The `ConfigureScanResponseData` API is used to configure the | ||
scan response data for advertising in a Bluetooth Low Energy (BLE) application | ||
based on the NimBLE BLE stack. Scan response data is additional data that a BLE | ||
peripheral device can include in its advertising packets to provide more | ||
information about itself. This API allows you to set the scan response data that | ||
will be included in the advertising packets. | ||
|
||
## Usage | ||
``` | ||
uint8_t scanResponse[31]; // 0x05, 0x09, a, b, c, d | ||
{ | ||
scanResponse[0] = 0x05; | ||
scanResponse[1] = 0x09; | ||
scanResponse[2] = 0x61; | ||
scanResponse[3] = 0x62; | ||
scanResponse[4] = 0x63; | ||
scanResponse[5] = 0x64; | ||
chip::ByteSpan data(); | ||
chip::DeviceLayer::Internal::BLEMgrImpl().ConfigureScanResponseData(data); | ||
} | ||
``` | ||
Note: ScanResponse should be configure before device starts advertisement. |
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
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