Hello, I am working on a project using Mesh with nrf52 boards. I have 3 boards for now, two of them are in a mesh network (boards A and B) (I will have more later to hava a real mesh network), and the

#bluetoothmesh

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, The Zephyr mesh health server leaves fault registration up to the application, however you do need to register a bt_mesh_health_srv_cb struct which includes callbacks for retrieving the faults, cl

#bluetoothmesh #zephyrbluetoothmesh

Hi All, I am looking at the BT Mesh Health Server, and Client, so that i can report faults between nodes and ultimately to the central control application. Unfortunately, i have run into a problem; Ho

#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

Interesting, I was using this CONFIG_BT_SETTINGS because I got it on other project. I did what you said and the errors were gone, thank you, apparently is working. One more thing, this messages "<wrn>

#bluetoothmesh #zephyrbluetoothmesh

Hi Lucas, It looks like you’ve enabled CONFIG_BT_SETTINGS, but are not calling settings_load() in your app. It might explain the behaviour you’re seeing, since you’re effectively leaving the stack par

#bluetoothmesh #zephyrbluetoothmesh

Hello, I need help to understand what is the correct way to make a self provision. I have two boards(nrf52_pca10040) and them will be provisioned on the same network to make some tests. So far I was u

#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, I'm new to this and struggling with BLE Mesh provisioning and need help, I am using Micro-bit (nrf51) which struggle to provision via BlueZ meshctl as they have such little memory hence i am attem

#bluetoothmesh #zephyrbluetoothmesh

Hi, After merging https://github.com/zephyrproject-rtos/zephyr/pull/13135#issuecomment-462891136 this PR in local repo, we can do DFU OTA using Android #nRFConnect. But I've observe following things:

#bluetoothmesh

Hi, Since this is a BlueZ question it’d be better asked on the BlueZ mailing lists. I’ve added it to CC. E.g. Brian or Inga (who know the BlueZ mesh implementation very well) might be able to answer y

#bluetoothmesh #nrf52832

Hey, I am trying to establish a bluetooth mesh using the Raspberry Pi 3 (bluez meshctl) as the provisioner and the nrf52 boards as the nodes. The nodes have to periodically send sensor data (LPN) to t

#bluetoothmesh #nrf52832

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

I noticed that in these examples, there's only one main.c file, and only one image file would be built, it can support different hardware, but seems not different roles? Bluetooth Mesh is supposed to

#bluetoothmesh

Hi Robert, Can you please open a GitHub issue and assign it to @jhedberg ? Thanks, Carles

#ble #bluetoothmesh

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 There is a platform_whitelist in the sample.yaml file. In your case: "platform_whitelist: frdm_k64f " So you need this nxp board or have to port the sample to another board. Greetings Serafin

#bluetoothmesh #nrf52480 #nrf52832 #zephyrbluetoothmesh

Hi All, I have been working on ipv6 over ble on zephyr RTOS to form mesh network.I have been successfully integrated "rpl_node"(which is in zephyr/samples/net/rpl_node) with ble(nrf52832), and it has

#bluetoothmesh #nrf52480 #nrf52832 #zephyrbluetoothmesh

Hi, When could we expect that blemesh code will be usable in c++. Most header files in zephyr are compatible with c++ but not ble mesh headers. No #ifdef __cplusplus in headers. Regards, Robert

#ble #bluetoothmesh