Mesh SDK Coexistence apps and provisioning

[rich_l]

My question is basic.  I'm using Mesh SDK 3.2.0 and tried running both of the coexistence apps (ble_app_uart and ble_app_proximity) out of the box on the nRF52832 DK.  Of course I followed the instructions and copied the example project folders from the mesh SDK to the examples/ble_peripheral folder under SDK_15.3.0.

I am able to connect from my Android Smartphone to the kit using nRF Connect, so the BLE peripheral portion of the example is working.

However, I need to provision the devices for my mesh network.  I do not see either example show up in the nRF Mesh App (latest version 2.0.2) so I can't provision or configure.  Any ideas?  Is this expected behavior because the device cant advertise as a Peripheral and as a GATT Proxy at the same time?

I'm using these examples as a learning point for implementing a BLE peripheral into my custom mesh devices and we need to provision our devices, for now, using nRF Mesh app as we set up various demos.

Thanks in advance for the advice and help,

Rich

[rich_l]

Bjorn,

I set MESH_FEATURE_PB_GATT_ENABLED as you suggested and had to add a few missing files to get the project to build.  Now I am getting the runtime error NRF_ERROR_INVALID_STATE in mesh_adv_data_set() line 135 when sd_ble_gap_adv_set_configure() is called so I think there is a conflict with setting up advertising for the BLE peripheral connection and advertising for the mesh proxy.  Any ideas?  Is it even possible for a mesh node to advertise as a standard BLE peripheral and at the same time be recognizable by the nRF Mesh app for provisioning and configuration?

Rich

[Bjørn Kvaale]

Hi Rich,

Sorry about that. I double checked with an engineer & he said it is not possible to do proxy & then normal BLE. Therefore, you cannot provision via the nRF Mesh app.

Kind Regards,

Bjorn