nvl1109 wrote:That is a great news, thank you.
Is there anyone tried with linux bluez 5.50?
I have tried with bluez, but it's failed to provision. the local_node.json and prov_db.json are taken from bluez code."Provisioning failed" message are shown.
Code: Select all
[meshctl]# discover-unprovisioned on SetDiscoveryFilter success Discovery started Adapter property changed [CHG] Controller AA:AA:AA:AA:AA:AA Discovering: yes Mesh Provisioning Service (00001827-0000-1000-8000-00805f9b34fb) Device UUID: dddd240ac402fd8e0000000000000000 OOB: 0000 [meshctl]# provision dddd240ac402fd8e0000000000000000 Trying to connect Device 24:0A:C4:02:FD:8E ESP-BLE-MESH Adapter property changed [CHG] Controller AA:AA:AA:AA:AA:AA Discovering: no Connection successful Services resolved yes Found matching char: path /org/bluez/hci0/dev_24_0A_C4_02_FD_8E/service002e/char002f, uuid 00002adb-0000-1000-8000-00805f9b34fb Found matching char: path /org/bluez/hci0/dev_24_0A_C4_02_FD_8E/service002e/char0031, uuid 00002adc-0000-1000-8000-00805f9b34fb Start notification on /org/bluez/hci0/dev_24_0A_C4_02_FD_8E/service002e/char0031 Characteristic property changed /org/bluez/hci0/dev_24_0A_C4_02_FD_8E/service002e/char0031 AcquireNotify success: fd 7 MTU 517 Notify for Mesh Provisioning Out Data started Open-Node: 0x559c78 Open-Prov: 0x556540 Open-Prov: proxy 0x55af78 Initiated provisioning Characteristic property changed /org/bluez/hci0/dev_24_0A_C4_02_FD_8E/service002e/char002f AcquireWrite success: fd 8 MTU 517 GATT-TX: 03 00 10 GATT-RX: 03 01 01 00 01 00 00 00 00 00 00 00 00 Got provisioning data (12 bytes) 01 01 00 01 00 00 00 00 00 00 00 00 Provisioning failed Attempting to disconnect from 24:0A:C4:02:FD:8E Characteristic property changed /org/bluez/hci0/dev_24_0A_C4_02_FD_8E/service002e/char0031 Write closed Services resolved no Characteristic property changed /org/bluez/hci0/dev_24_0A_C4_02_FD_8E/service002e/char002f [meshctl]#
In ESP32 console
Code: Select all
I (763) ble_mesh_node: BLE Mesh Node initialized I (40113) ble_mesh_node: esp_ble_mesh_prov_cb, event = ESP_BLE_MESH_NODE_PROV_LINK_OPEN_EVT I (40113) ble_mesh_node: ESP_BLE_MESH_NODE_PROV_LINK_OPEN_EVT, bearer PB-GATT W (40303) BLE_MESH: Client wrote 0x0000 instead enabling notify
I am having this exact same issue when trying to use the meshctl tool from bluez 5.50. I am trying to use an RPi as a provisioner to provision multiple ESP32 BLE nodes.
I followed the guide from Bluetooth.com ( https://www.bluetooth.com/~/media/files ... shx?la=en ), but the only difference is that they are using nRF52 boards as the BLE mesh nodes.