Re: ESP BLE Mesh v0.5 Beta has been released
Posted: 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.
Thank you.
Is the any mechanism to store provision data into flash then restore the provision data when the board is restarted?
Thank you.
That is a great news, thank you.ESP_Island wrote: ↑Mon Dec 24, 2018 3:17 amHi, @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!
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]#
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
Will AT commands support BLE/WIFI mesh in future?
Saw this posted to Espressif YouTube last Friday: https://www.youtube.com/watch?v=xLUy1-O7UJE
Is there an ETA on the ESP-BLE-Mesh update release (with provisioning restoration etc)?
Any chance you can commit the most recent updates so that we can help with testing? This seems to be one of the most popular threads on the forum, so BLE Mesh on ESP32 is hot!ESP_Island wrote: ↑Tue Feb 05, 2019 5:07 amSaw this posted to Espressif YouTube last Friday: https://www.youtube.com/watch?v=xLUy1-O7UJE
Is there an ETA on the ESP-BLE-Mesh update release (with provisioning restoration etc)?
The update release is under test. It will be published soon, please wait for it with patience
Thanks
1. The get_onoff_set_handler contains 4 parameters:
Code: Select all
static esp_ble_mesh_model_pub_t onoff_pub = {
.msg = NET_BUF_SIMPLE(2 + 1),
.update = NULL,
.dev_role = ROLE_NODE,
};