Mesh advertising and BLE advertising coexistence on nRF5340

[Marco Russi]

Hello,

I built my application based on your "ble_peripheral_lbs_coex" example. Board is nRF5340DK.

Mesh and BLE (NUS service) run together but I noticed that the NUS UUID is in scan response. Indeed I see only the Mesh UUID advertised and the way to see the NUS UUID is to connect only. 

Would it be possible to add a custom UUID alongside the Mesh one?

Can I modify the default Mesh UUID to a custom proprietary Mesh UUID?

Thank you.

Marco

[Mttrinh]

Hi,

Mesh and BLE (NUS service) run together but I noticed that the NUS UUID is in scan response. Indeed I see only the Mesh UUID advertised and the way to see the NUS UUID is to connect only. 

The NUS UUID beeing in the scan response is probably du to space restrictions in the advertisement packet. You will have to send a scan request to be able to see the NUS UUID without connecting.

Would it be possible to add a custom UUID alongside the Mesh one?

Do you mean in the scan response? instead of the NUS UUID?

Can I modify the default Mesh UUID to a custom proprietary Mesh UUID?

By Mesh UUID, are you referring to the provisioning service or proxy service?

[Mttrinh]

Hi,

Marco Russi said:

I mean to add a custom UUID together with the Mesh one in the normal advertising space (no scan response). However you said that it is probably not possible due to space restrictions... can you confirm this? 

Yes, its not possible due to space in the advertisement packet.

Marco Russi said:

By changing the Mesh UUID I mean the advertised one so I guess the provisioning service. If possible, should I register this UUID to Bluetooth SIG or go through a sort of paperwork?

It seems like it is possible to customize the device UUID.

You should contact Bluetooth SIG regarding the paperwork.

[Marco Russi]

Thank you very much.