Problem with integration of light switch server with the beacon project from the nRF5 SDK.

[Matteo Orlandini]

Hi,

I'm trying to integrate the light switch server example in nRF5 SDK for Mesh v4 with ble app beacon from the nRF5 SDK v16. I added the advertising_init and the advertising_start functions from the beacon example to the light switch server example. The firmware is correct and Segger can build successfully the project.

I saw that if the macro MESH_FEATURE_GATT_ENABLED is set, the RTT Viewer gave "app_error_weak.c,  119, Mesh error 4 at 0x000268F1" because there is a problem with sd_ble_gap_adv_set_configure.

#if MESH_FEATURE_GATT_ENABLED
    gap_params_init();
    conn_params_init();
#endif

If the macro MESH_FEATURE_GATT_ENABLED is zero, the firmware works well without any errors but the nRF Mesh mobile app can't find the board. I evaluate the firmware with two other boards, in one of them is flashed the light switch provisioner example and in the other one is flashed the client example. The three board work well and they successfully rum mesh and the server can also send beacon.

How can I make this work with nRF Mesh mobile app? I think there is a proxy problem but I don't know how to fix it.

Thanks.

[Hung Bui]

Hi Matteo, 

The softdevice can only do one advertising at a time (you can switch between but you have to reinitialize the advertising packet). So if you want the device to advertise as a GATT proxy device and a beacon (and mesh) at the same time, you should use mesh API to do advertising, instead of calling advertising_init () and advertising_start () . 

I would suggest you to have a look at the beaconing example. Have a look at adv_init() and adv_start() function. These functions use Mesh advertiser module to do beacon advertising. 

[Matteo Orlandini]

Thank you Hung.