Hi Billy, That depends on your application and the source of the faults. All the stack requires is for you to keep track of the fault history. You could do that e.g. with a simple u8_t array like the

#bluetoothmesh #zephyrbluetoothmesh

Hi Lucas, (added zephyr-devel back to CC since this info may benefit others as well) No, that’s normal. It means you used the configuration client API without requesting it to wait for the response me

#bluetoothmesh #zephyrbluetoothmesh

Hi Billy, If I were to guess, you’re calling the configuration client APIs without waiting for the responses (passing NULL for the response parameters, like the status) and some previous call has cons

#bluetoothmesh #zephyrbluetoothmesh

Hi All, I am looking at implementing a sensor network via BLE Mesh and am looking for any information on the implementation of the SENSOR MESH MODEL. Can anyone point me in the right direction? Many t

#bluetoothmesh #zephyrbluetoothmesh

Hi All, I have been working on RPL node example(which is in zephyr/samples/net/rpl_node), to work it as both central and peripheral concurrently. I have successfully integrated peripheral code with RP

#nrf52832 #zephyrbluetoothmesh

Hi Akash, Look the at the hardware information and setup procedure in "samples/net/rpl_border_router/README.rst". - Ravi

#bluetoothmesh #nrf52480 #nrf52832 #zephyrbluetoothmesh

Hi Akash, Maybe have also a look at this example: https://docs.zephyrproject.org/1.13.0/samples/boards/nrf52/mesh/onoff-app/README.html Best regards, Frank

#nrf52832 #zephyrbluetoothmesh

Hi Vikrant, It's impossible to say for sure without some more information. It's possible that different advertising parameters are used. If you have PB-ADV enabled that will also take time away from P

#zephyrbluetoothmesh #gettingstartedguide