On Tue, 2019-05-14 at 14:50 +0530, Shaik Mahaboob Nazeer wrote: > hi, > > -> We tried Zephyr Mesh onoff example on nrf52 eval kit to test the > Mesh Functionality.For provisioning of the node > we are using meshctl, built from the latest current master of the > bluez source.So during the provisioning of the node when we > start the "meshctl" and run the "discover-unprovisioned on" we are > able to get the Device UUID for the provisioning. > > Later when we try to provision the node using the "provision > <UUID>" command it initiate the provision and does not wait > for the user to enter OOB .You can find the log as below. > /*******************************************/ > --- snip --- > /**************************************/ > > Could you elaborate a little on the status of the current master of > bluez in regards to BLE mesh, is it usable or should we look to older > versions? > > Do you know if there is a common issue while provisioning of the node > with the current master and > is there anything that need to be configured before provisioning? > I get the same results. I check out 48a2c3db1ccff28a615fac56066ca7d721f98d0a That was the last time I used meshctl. It requests an oob string and completes provisioning. Steve
