Skip to content

Define functional requirements for BLE.scan() to process duplicated Peripherals. #508

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
SidLeung opened this issue Mar 28, 2017 · 4 comments

Comments

@SidLeung
Copy link
Contributor

The BLE.scan API is (in v 2.0.2) capable of filtering out duplicated detected Peripherals. The fact that Advertisement data of a Peripheral may be presented in one or multiple packets (Adv Data and Scan Response Data). Thus, this ticket is to clarify the requirements of the scan() API on how to process the Adv info from different kinds of Peripheral.

@SidLeung SidLeung self-assigned this Mar 28, 2017
@SidLeung SidLeung added this to the Elnath milestone Mar 28, 2017
@SidLeung
Copy link
Contributor Author

Capturing a discussion on this issue here,

#500 (comment)

@SidLeung
Copy link
Contributor Author

@sandeepmistry @sgbihu , please present your suggestions/requests for change here.

@sgbihu
Copy link
Contributor

sgbihu commented Mar 29, 2017

The scan request will send out after the central see the advertising. So the scan response will be got in an expected time. The implementation can add a delay to return new device. I have implement a solution here #502

@novashah
Copy link

Fixed and Merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants