-
Notifications
You must be signed in to change notification settings - Fork 688
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
Add connectable property to BLE Scan result #812
Comments
I have seen Advertisement Flag 0x1A being connectable an also nonconnectable in nRF android app. |
You can have a connectable device without any included advertised Flags. |
@Luxin812 PTAL |
@mrx23dot , thank you for your good idea. We will consider adding it to our future feature development plans. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem?
Asking for near by BLE devices don't tell me if they are connectable or not:
based on discussion in comments here:
https://stackoverflow.com/questions/28467590/detecting-whether-a-ble-device-is-connectable-on-android
"connectable" status doesn't come from Advertisement Flags but from environment (ESP AT).
Describe the solution you'd like.
is connectable
+BLESCAN:"52:83:e4:05:9f:d9",-98,0303f3fe,,1,yes
+BLESCAN:"52:83:e4:05:9f:d9",-98,0303f3fe,,1,no
or in number
Describe alternatives you've considered.
only other way to test is trying to connect but that's VERY slow.
Additional context.
version
The text was updated successfully, but these errors were encountered: