-
Notifications
You must be signed in to change notification settings - Fork 132
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
Regarding Pre-Pairing #20
Comments
Hi! However, you can connect to a device without pairing/bonding. Thanks! |
What I mean by pre-pairing is that, once the device is visible and it has a certain vendor's name, the application should be able to initiate connection without the user having to navigate through menus and do pairing. |
Thanks for the clarification. So in essence, you'd like the ability to add a watcher that is watching to a particular address or device name that's continuously scanning? |
So I would have 100s of devices, which are made by a specific vendor(Say JBL headphones) and I would like to connect to them and receive data as and when I am within the range of those devices and once they have some data to send. |
Got it. The Apis this app is using/demonstrating certainly would allow you to build such an app. You can create an Advertisement watcher with the filtering parameters you need (filtering attribute and RSSI range), then perform the actions you need such as reading/writing or subscribing to a characteristic notification/indication. |
Ok I did manage to filter the devices using the name these devices have. Assuming each of them would have a common substring, but I have not been able to connect automatically without including the click of the glyph() method. |
Perhaps if you share the code of what you've attempted @drache42 can help further. |
Do I load it in my github and share it ? |
If you could load on GitHub that would make life easy. I can then take a look. |
Does this application allow pre-pairing or are there other applications that Microsoft allows pre-pairing and auto connecting of BLE devices
The text was updated successfully, but these errors were encountered: