Interactive PyACI won't find my unprovisioned device

RE: Interactive PyACI won't find my unprovisioned device

Renato Freitas — Thu, 29 Oct 2020 19:25:07 GMT

Sorry for not mentioning the LPN part. Enabling MESH_FEATURE_PB_ADV_ENABLED seems to solve the problem, now I'm able to use PyACI successfully.

Thank you very much!

RE: Interactive PyACI won't find my unprovisioned device

Hung Bui — Thu, 29 Oct 2020 09:52:49 GMT

You could have mentioned about "Mesh LPN" in your question. The Mesh LPN firmware by default doesn't support PBADV provisioning. You can find that in the documentation here at Provisioning and configuration section.

To enable PBADV you need to set MESH_FEATURE_PB_ADV_ENABLED to 1 in nrf_mesh_config_app.h . I haven't tried myself if it works though.

RE: Interactive PyACI won't find my unprovisioned device

Renato Freitas — Wed, 28 Oct 2020 20:52:33 GMT

Hi Hung, thanks for the fast reply.

I liked your idea of flashing my firmware on a dev board, but considering that my device has a lot of peripherals configurations, it would be time consuming removing those routines just to test the Mesh part. So what I did was the opposite: flashed my device with a nRF5x Mesh LPN Switch example (which my code is based of), and it still doesn't show only on the PyACI terminal, but I can see it using both the nRF Mesh and nRFConnect phone apps.

I followed your advice of using the NRFConnect app to sniff BLE packets and noticed that the only difference between packets from the dev board with the nRF5x Mesh Light example and my device is the adv interval:

https://ibb.co/Yf0Fbw9

https://ibb.co/CsNcYP0

Maybe the PyACI doesn't recognize the first one because of the large time interval?

RE: Interactive PyACI won't find my unprovisioned device

Hung Bui — Wed, 28 Oct 2020 13:21:55 GMT

Hi Renato,

It's hard to tell what could be wrong.
But if you try your same firmware (with Generic Level Client) on the other dev board, can you find it with PyACI ?

Another thing you can try is to turn off MESH_FEATURE_PB_GATT_ENABLED in nrf_mesh_config_app.h this will disable PBGATT provisioning via GATT and only allow PB ADV provisioning. Then you can use the NRFConnect app on the phone to try scanning if you can catch the advertising packet with Beacon type 0x00 Like what shown here::