B
bebop_dev
Guest
I'm using the bluetoothleapis.h, and wrote some code that only works when my BLE device is in "Connected" state on Windows, but the problem is the device mostly stays in the "Paired" state. On initial pairing the device will say "Connected" and quickly change to "Paired". Sometimes after doing this several times, it will finally stay "Connected", but I'm not sure what triggers this.
Anyway if the device is in the "Paired" state, BluetoothGATTSetDescriptorValue and BluetoothGATTSetCharacteristicValue both return E_ABORT or -2147467260, thus I can't setup the notification changes and writing messages to the device.
The Device is running a custom GATT service is I'm not sure if this a device problem or not, or why Windows briefly puts the device in the "Connected" state, which my app can work and continue to get info from the device, but if I don't start my app quick enough the device will go to "Paired", and I'll have to reconnect the device again.
Is there perhaps a programmatic solution to put the device into the "Connected" state? Has anyone seen this behavior before?
Continue reading...
Anyway if the device is in the "Paired" state, BluetoothGATTSetDescriptorValue and BluetoothGATTSetCharacteristicValue both return E_ABORT or -2147467260, thus I can't setup the notification changes and writing messages to the device.
The Device is running a custom GATT service is I'm not sure if this a device problem or not, or why Windows briefly puts the device in the "Connected" state, which my app can work and continue to get info from the device, but if I don't start my app quick enough the device will go to "Paired", and I'll have to reconnect the device again.
Is there perhaps a programmatic solution to put the device into the "Connected" state? Has anyone seen this behavior before?
Continue reading...