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 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, Recently i have started working on Zephyr RTOS to explore IPV6 over BLE.And i am totally new this. I would like to form a mesh network with PCA10059(5 boards) and PCA10040(1 boards) boards, an

#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 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

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 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

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, (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, 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 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, 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 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 Johan, https://www.youtube.com/watch?v=301ynC2IdbY Mr. Martin Woolley has released video which shows time required to discover & provision #BluetoothMesh DEVICE. In this case, he has used "firmware

#zephyrbluetoothmesh #gettingstartedguide

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

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

We have some questions regarding the BLE MESH, So kindly go through below hardware and software setup and please guide us about our queries. Your quick response will be highly appreciated. Hardware se

#ble #bluetoothmesh #hci #zephyrbluetoothmesh #uart