Excellent news, thank you!

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

Removing all the calls to unbond() from our side does not mitigate the automatic reconnection.

Gotcha, sounds great!

Try setting the delay between tasks option in the settings menu to something like .5 seconds (the value is in seconds). See if it improves the connection rate at all. I've heard sometimes delaying after service discovery can sometimes help with 133 gatt errors when connecting. This test should at least give us some proof that this is true or not.

Bjoern, How are you setting your reconnect filter?

I'm having the same problems on v3.0.2, where as I connect, turn Bluetooth off and on again, it'll automatically reconnect (at least that's what the sensor says),but a NATIVE_CONNECTION_FAILED is given.

I've updated the logic for enabling/disabling notifications. Now if you pass in a notification listener in a BleNotify instance, it will set that listener as the default only if there are no other NotificationListeners set for the device. This will be in the next version.

The sample projects should be published here: https://forum.sweetblue.io/category/6/sample-apps Hope they upload some soon.

Great suggestion, thanks!