About the Bluetooth mesh light samples question on NRF5340

RE: About the Bluetooth mesh light samples question on NRF5340

Hieu — Thu, 29 Dec 2022 16:08:20 GMT

Hi Hugh,

Thank you for the kind words, we are just slowly getting better.

Glad to know that you got everything working as you wished. I will close this Q&A then.

Hieu

RE: About the Bluetooth mesh light samples question on NRF5340

Hugh Wu — Thu, 29 Dec 2022 01:30:37 GMT

Hi Hieu,

I’m sorry to hear about that. Hope you and your family are going well.

I think I resolved this problem, I tried to enable the automatic connection on the mesh app of proxy icon, and then I can provision devices by using no OOB as well. Just following the video, I added group, subscribed it, set publish, and whatnot. Finally, I pressed the button from light switch device, and then I saw the led1 was turned on/off on the light device.
Everything turn out great.

Hugh

RE: About the Bluetooth mesh light samples question on NRF5340

Hieu — Wed, 28 Dec 2022 21:09:44 GMT

Hi Hugh,

Sorry for the late follow-up. We are facing a holiday understaffed situation, and my family is just recovering from some surprisingly long lasted health issues.

I personally encountered the same symptom where the provisioned timeout at "Requesting Composition Data..." If I recall correctly, the fix for me was to disable debug options in the build.

Could you please try both of these and let me know if one or both works?

- Disable debug options

- Use NCS v2.0.2, but still build with debug options

RE: About the Bluetooth mesh light samples question on NRF5340

Hugh Wu — Tue, 27 Dec 2022 16:36:27 GMT

Hi there,

I followed this video https://www.youtube.com/watch?v=Jt2ui22fBjM&t=872s for trying to build up my mesh network.

But I don't have the Thingy:53 device for a mesh light node, so I replace it with NRF5340 DK,

And I also get the provisioned timeout that "Requesting Composition Data..." after clicking the "no OOB" type to provision the device

The UART log as below:

*** Booting Zephyr OS build v3.2.99-ncs1 ***
Initializing...
[00:00:00.448,547] <inf> fs_nvs: 8 Sectors of 4096 bytes
[00:00:00.448,547] <inf> fs_nvsBluetooth initialized
: alloc Mesh initialized
wra: 0, fe8
[00:00:00.448,547] <inf> fs_nvs: data wra: 0, 0
[00:00:00.466,400] <inf> bt_hci_core: No ID address. App must call settings_load()
[00:00:42.885,589] <wrn> bt_l2cap: Ignoring data for unknown channel ID 0x003a
[00:00:47.937,774] <inf> bt_mesh_main: Primary Element: 0x0007

Sorry, I don't know how to reproduce the first version log I sent, does anyone assist me with how to set up the Bluetooth mesh network?

RE: About the Bluetooth mesh light samples question on NRF5340

Hugh Wu — Mon, 26 Dec 2022 03:25:44 GMT

Hi Hieu,

Thanks for your reply,

No, The 14-second logs happened after clicking the network device from the Nrf mesh App.

RE: About the Bluetooth mesh light samples question on NRF5340

Hieu — Fri, 23 Dec 2022 21:16:28 GMT

Hello Hugh,

In your log, I see a 14-second difference from boot until the error happened. Were there some manual trigger/external events before the error happened?

Hieu