We're looking at around 2 weeks or so before we put out the official release.

Excellent news, thank you!

@benp thanks a lot, will check it out!

@caeduk Please post a new topic with specific steps to reproduce the issue you're having so we can investigate it on our end.

Undiscover will disconnect, but will not explicitly unbond.

Thank you for your replies. It is interesting that you got different results than me. On my undersanding, turning off the Bluetooth adapter definitely terminates the connection and thus the device can be used again for further scanning/connection. I've been trying out a bunch of different things. Sometimes, when the device is stuck on this state, I am able to retrieve the device from the regular getDevice(String macAddress) method. And then I can establish a connection, verify the BONDED state, read the standard Device Information Service, and even enable some BleNotify. However, I am not able to negotiate the MTU as the operation fails with a REMOTE_GATT_FAILURE due to “no resources”. I'll activate autoNegotiateMtuOnReconnect and try again tomorrow, maybe you have some magic in there or I'm doing something wrong. Other than that, I think I'll use the getDevices_bonded() function, filter for the device, and unbond it. Then connect again. That seems to work on the Toolbox V3 app and does not retrigger a bonding notification for some reason.

Excellent, please let me know if you still see the problem.

Yes, those trigger. We added those when we noticed that the times we set in taskTimeoutRequestFilter or DefaultTaskTimeoutRequestFilter weren't triggering.

Hi, I'm jumping back into this thread with more information and a couple of questions: The Nordic's nRF Connect app can detect when I connect the BLE peripheral on my own app and directly interact with it. Which is pretty cool. Also, when you open up their application and you click 'connect' on a bonded device that is already connected (using my own app), their app connects the services and is able to interact with the peripheral device. Q1: How could I achieve the behavior described by point #2? Either manually (user interaction required) or automatically? i.e. when I open up my app, it should detect bonded devices that are connected and enable them to be used right away by the user.

Well, it's mostly the connecting itself which is the issue... The scanning/finding is pretty consistent now...

Gotcha, sounds great!

@ryanbis Awesome! We look forward to the release. Cheers, Gunnar

Glad to hear! Looking forward to the next release.