ESP BLE Mesh v0.5 Beta has been released

[nvl1109]

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

[ESP_Island]

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]

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]

Will AT commands support BLE/WIFI mesh in future?

[ESP_Island]

Will AT commands support BLE/WIFI mesh in future?

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

[jmichel]

Hi,

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)?

Thanks.

[ESP_Island]

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)?

The update release is under test. It will be published soon, please wait for it with patience

Thanks

[Christoph]

I use the code ble mesh node. What do I have to do to publish a switching information? The function gen_onoff_set_handler has many parameters. Is there perhaps an example of how to define the structures?

[khigbe]

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)?

The update release is under test. It will be published soon, please wait for it with patience

Thanks

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!

I prefer to use CMake build, which doesn't work on Windows with esp-ble-mesh-v0.5 branch. I've tried a simple merge with v3.2 branch, that didn't work, would require work that is useless work because you've got a newer version that probably is merged with v3.2, or at least some newer branch.

We are patient, but we also need to make progress. I'd prefer to be helping you test and identify problems with new code than trying to work with old code.

[esp_liu]

I use the code ble mesh node. What do I have to do to publish a switching information? The function gen_onoff_set_handler has many parameters. Is there perhaps an example of how to define the structures?

1. The get_onoff_set_handler contains 4 parameters:
* model: which is the message related model, here in this example it's the Generic OnOff Server Model
* ctx: the message related information, e.g. the NetKey Index/AppKey Index used by the message, the source address of the message, the TTL of the message, etc.
* length: length of the Generic OnOff Set message
* data: context of the Generic OnOff Set message
Note: the specific definition of the Generic OnOff Set can be referred in Mesh Model Specification

2. If going to publish a switching information, the following need to be prepared:
* the corresponding model shall support publish functionality
* the model's Model Publication State shall be configured properly (by Configuration Client Model)
* When defining the model, it's publication struct shall be defined properly, for example:

Code: Select all

static esp_ble_mesh_model_pub_t onoff_pub = {
    .msg = NET_BUF_SIMPLE(2 + 1),
    .update = NULL,
    .dev_role = ROLE_NODE,
};

Here the msg is allocated for 3 octets (2 octets opcode + 1 octet on/onff) and the dev_role is set to ROLE_NODE.
After this, you can call esp_ble_mesh_model_publish() to publish the switching information.