I think Zephyr OS has better support for "Bluetooth Mesh" than Nordic own MESH SDK.
Using this kernel version, I flashed $zephyr/samples/bluetooth/mesh this example into three nRF52840-PDK boards. Now each board is advertising itself as "Zephyr" & using "NRF connect" Android App we can connect to it just like any other BLE peripheral device.
Now all three boards are acting like unprovisioned devices & we have to send some network & application keys via nRF connect app. Right ?
Or are they acting like proxy nodes ?
So after configuration, these devices may be turn as Mesh Node. Right ?? But I don't know what to send.
Nordic Mesh light_switch example is not showing any such properties. I think Nordic Mesh SDK is using Advertising Bearer while Zephyr is using GATT Bearer.
Now what that to do next is question ?
I also found this link, https://www.zephyrproject.org/announc...
As per my understanding, meshctl is BLueZ 5.47 based utility using which we have to develop Bluetooth Mesh Provisioner App. Am I right ?
When I run meshctl utility on my ubuntu desktop, it gives me following error -
Local config directory not provided. Failed to parse local node configuration file local_node.json
Does any body have this local_node.json for testing which is compatible for nRF52840-PDK board?