Access native peripheral implementation

[eygraber]

Is it possible to access the native implementation of a peripheral? I want to "hand off" my Kable connection to https://github.com/NordicSemiconductor/Android-nRF-Connect-Device-Manager, but I need the underlying BluetoothDevice.

[twyatt]

I'm reluctant to expose the underlying peripheral object (e.g. BluetoothDevice and/or BluetoothGatt on Android) as Kable's inner workings rely heavily on the state of those objects and that commands/callbacks are invoked in specific orders.

Exposing the underlying object provides a huge footgun to the library consumer.

Although it could potentially be exposed with massive warnings re: its direct usage. 🤷

I think it'd be better (if not too huge of a lift) to support Kable in libraries such as Android-nRF-Connect-Device-Manager. That library appears to have a transport layer, I wonder how difficult it would be to add a Kable-based BLE transport?

I'm curious if you've tried forking Kable to expose the underlying object and pass it along, and saw things work? I imagine when doing so would completely break the Kable side of things for that object?

[eygraber]

I haven't tried exposing it myself through a fork, but my current plan is to use BluetoothManager to find the existing BluetoothDevice and test it that way.

I thought about making a Kable transport for nRF, but I'm on a constrained schedule, so not sure if it's the most feasible.

[aetrocks]

I also have the need for the peripheral objects and or the Managers themselves, mainly because I need them for firmware updates.
Spiked using Kable and it works great for normal BLE interactions but in the end I need to use NRF-DFU-Libraries in iOS and Android and they want at least the peripheral I think.