On Wed, 2018-04-18 at 07:06 -0600, Steve Brown wrote:
On Wed, 2018-04-18 at 15:02 +0530, vikrant8051 wrote:
Hi,I looked at this too. Provisioning seems to complete, but the proxy
I am not able to provision my Devices which is executing sample
But able to provision it using Silicon Labs Bluetooth Mesh App.
Is it bug from meshctl (BlueZ) side ?
Thank You !!
service isn't discovered. Meshctl just seems to hang waiting for the
discovery to succeed.
While this is happening, if I use bluetoothctl to scan and then
to the node, the callback in meshctl fires and it starts up and
functions as expected. It appears that something is amiss with the
I believe that the SILABS App uses advertising bearer for
so it's not conclusive that it working and meshctl failing is
definitely a Bluez issue. I checkout an early March version of Bluez
and Zephyr. The problem is still there.
samples/bluetooth/mesh fails in the same way.
I'm not sure where to go from here.
I tracked this down to Zephyr and bisected the problem to commit
Bluetooth: Mesh: Fix Node Identity advertising with PB-ADV