Your observation is correct. This was a design decision on Apple's side and many developers have raised this issue so far. I suggest you check out the list archives, there have been lengthy discussions on the topic. To answer: no, there is no known way of forcefully disconnecting the peripheral other than programming the peripheral to disconnect automatically if needed. But in case of using an Apple device as peripheral even this solution may fail. Cheers, Andras On Oct 3, 2012, at 10:39 AM, Jimmy Adler <d99fish@gmail.com> wrote:
Hi,
I am trying to read out some values from a BLE device and then disconnect from it.
After I'm done reading I call: [centralManager cancelPeripheralConnection:peripheral]; and I get the callback: didDisconnectPeripheral
In the callback I check: [peripheral isConnected] and it comes back as 0.
However, the device appears to still be connected, when looking in the settings app under bluetooth. It takes and additional 30 seconds or so before the device is actually released, and I belive that this is due to the device closing the connection, since it has a timeout of about that long if no transmissions are made, it will go to sleep.
Is there any other way to do the diconnect?
Br,
Jimmy _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/allprog%40gmail.com
This email sent to allprog@gmail.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com