How to use Bluetooth Mesh GATT provisioning with regular BLE stack?

[gsegment]

I am running an example from Mesh SDK (v2.1.1) named "ble_app_uart_coesixt". I see device in Bluetooth list, everything is ok. But I need to provision this device using my smartphone without other devices. My goal is to provision device and than communicate with regular BLE uart profile. I can't understand how to combine "light_switch proxy_client" with coexist example. As I see it is just GATT service, and I don't need a "proxy" feature itself, only need to provision device with BLE. How can I do it?

[Bjørn Kvaale]

1) Do you want to be Bluetooth Mesh compliant? If so, I believe these provisioning you want to do might break the Bluetooth Mesh specs, thereby making it very difficult to become certified. You can naturally make your own proprietary mesh solution if that is easier & you do not need Bluetooth Mesh compliance. I would just make sure to focus on the security aspect, as a subnetwork key will give access to the network layer of the sub network.

2) By node IDs, are you referring to the unicast addresses that are provided to the nodes in the nRF Mesh app for example?

I would strongly recommend to take a look at Section 3.10.2 & 3.10.4 from the Mesh Profile Spec. These two sub-chapters explain temporary guest access & the key refresh procedure when a guest node is e.g. removed from the network. That way, the keys that are no longer used by the guest device are essentially thrown away.

gsegment said:

So when guest has been provisioned and later leaves, how we can handle >16 bit IDs acquiring?

 I believe this will be similar to when a node leaves the mesh network. Are you referring to the unicast address again with the >16 bit IDs? Are you wondering what happens to the unicast addresses that were given to the guest networks?