ESP BLE Mesh v0.5 Beta has been released

nvl1109
Posts: 5
Joined: Sat Feb 20, 2016 3:48 pm

Re: ESP BLE Mesh v0.5 Beta has been released

Postby nvl1109 » Sun Dec 23, 2018 11:18 am

Is the any mechanism to store provision data into flash then restore the provision data when the board is restarted?
Thank you.

ESP_Island
Posts: 14
Joined: Thu Jun 29, 2017 7:20 am

Re: ESP BLE Mesh v0.5 Beta has been released

Postby ESP_Island » Mon Dec 24, 2018 3:17 am

Is the any mechanism to store provision data into flash then restore the provision data when the board is restarted?
Thank you.

Hi, @nvl1109
We will release a new BLE Mesh Version soon. It will include many new features, including `restoring the provision data of the node device`, `fast provisioning`, `wifi/ble_mesh coexistence`, etc... Stay tuned!

nvl1109
Posts: 5
Joined: Sat Feb 20, 2016 3:48 pm

Re: ESP BLE Mesh v0.5 Beta has been released

Postby nvl1109 » Sat Dec 29, 2018 4:56 pm

ESP_Island wrote:
Mon Dec 24, 2018 3:17 am
Hi, @nvl1109
We will release a new BLE Mesh Version soon. It will include many new features, including `restoring the provision data of the node device`, `fast provisioning`, `wifi/ble_mesh coexistence`, etc... Stay tuned!
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.

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]#
"Provisioning failed" message are shown.
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

kurta999
Posts: 6
Joined: Sat Jul 21, 2018 4:15 pm

Re: ESP BLE Mesh v0.5 Beta has been released

Postby kurta999 » Fri Jan 11, 2019 12:54 pm

Will AT commands support BLE/WIFI mesh in future?

ESP_Island
Posts: 14
Joined: Thu Jun 29, 2017 7:20 am

Re: ESP BLE Mesh v0.5 Beta has been released

Postby ESP_Island » Tue Jan 15, 2019 2:15 pm

Will AT commands support BLE/WIFI mesh in future?

Through the information from AT team, currently, we have no plans to do it.

Who is online

Users browsing this forum: No registered users and 11 guests