-
Notifications
You must be signed in to change notification settings - Fork 354
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
bug in retrieveConnected #559
Comments
I am having a similar issue on Android. I bought a smart watch to interface with the heart rate monitor. The watch is connected to the phone but when I call retrieveConnected() I only get devices that my specific app has connected to. It doesn't retrieve the watch. Edit: I found my issue. getBondedDevices() is returning my watch, but the plugin is filtering out on: if (device.getType() != BluetoothDevice.DEVICE_TYPE_LE) { My watch is returning as BluetoothDevice.DEVICE_TYPE_DUAL |
@asoap Thanks for taking a closer look. This should be fairly simple to fix, so I'll try to raise a PR in the next week or so. But PRs are always welcome :) |
I can make a pull request and do the change. I'm just not sure if it should be changed? Like I don't know enough about BLE to know if DEVICE_TYPE_DUAL should be talking also? Or if there is some limit that is added because of it? |
I don't think there's any issue updating it to DEVICE_TYPE_DUAL. https://stackoverflow.com/questions/54922664/android-bluetoothdevice-type-dual |
bluetoothle.retrieveConnected doesn't return any paired devices on iOS 14 (iPhone X) |
bluetoothle.retrieveConnected is returning a blank array to me for the success callback. |
I confirm obtaining an empty array in the |
When i print data from retrieve connected i am getting only 2 devices, but i know i have 3 devices bonded (confirmed with nRF connect), also
isBonded
returns true with my TV address, which is not included inretrieveConnected
:ionic + angular on Samsung S9+, android 9.
Thanks for great plugin, even with few bugs/glitches is really awesome.
The text was updated successfully, but these errors were encountered: