Ive been running ble mesh example for few minutes as for now and i have question. From menuconfig options i understand that esp32 should store all necessary data exchanged during provisioning like app key, IV etc, but now it seems not work. My question is: is it implemented now, will it be implemented or do we need to implement it in our app? No complaining, just asking.

- Up to how many nodes you have tried with this MESH Networking using BLE?
- What will be the average current consumption if you have connected multiple nodes?
- How network has been formed means like parent and child or like hope mechanism?
- Is there any critical issue to use BLE MESH current release so that we can plan accordingly?
- which ESP32 IDF version will be supported for that?

I will try to check it into next week and will ask few more questions based on our analysis.

Ive been running ble mesh example for few minutes as for now and i have question. From menuconfig options i understand that esp32 should store all necessary data exchanged during provisioning like app key, IV etc, but now it seems not work. My question is: is it implemented now, will it be implemented or do we need to implement it in our app? No complaining, just asking.

Currently, it doesn't store the data in NVS. So if you don't reboot the device, it should work finely. If it doesn't work on your side, could you tell us how to reproduce your issue?

BTW, for the "power-down memory" feature:
* We have finished the "NVS storage" of Mesh nodes and it will be released soon
* For the "NVS storage" of Provisioner device, it is on the development plan and will be released in the near future

- Up to how many nodes you have tried with this MESH Networking using BLE?
- What will be the average current consumption if you have connected multiple nodes?
- How network has been formed means like parent and child or like hope mechanism?
- Is there any critical issue to use BLE MESH current release so that we can plan accordingly?
- which ESP32 IDF version will be supported for that?

I will try to check it into next week and will ask few more questions based on our analysis.

What follows is my response to your questions, hope it helps you:

Up to how many nodes you have tried with this MESH Networking using BLE?
* We have tried with 100 BLE devices;
* Maybe this demo will help you make a first impression about how is "ESP32 BLE Mesh" going: Espressif Fast Provisioning using ESP BLE Mesh App .

What will be the average current consumption if you have connected multiple nodes?
* BLE Mesh nodes need to stay on the scanning state all the time, so they are normally main powered (e.g., 220V power supply).
* There is a special role "Low Power Node" in BLE Mesh which is designed for the ultra-low power sensors;
* But some features are disabled for those LPN nodes, such as relay feature, proxy feature, friend feature, etc.
* I think ESP32 is not suitable for the "ultra-low power" case compared to some other BLE-Only chips.

How network has been formed means like parent and child or like hope mechanism?
* BLE Mesh is a "Flooding Mesh" and it requires neither "routing table" nor "parent-child". That means, all the devices are broadcasting data and also listening to the broadcasting from the nearby devices.
* I think the following article will help you have a basic knowledge about "BLE Mesh Networking": An Intro to Bluetooth Mesh

Is there any critical issue to use BLE MESH current release so that we can plan accordingly?
* We have fixed most of the critical issues that we have encountered during our test;
* I think the main "critical issue" is that we need more test about our BLE Mesh. And we hope that our customers can help test our "beta version" and provide more suggestions about it. So that we can make it stable more quickly.
* We have been developing on BLE Mesh to improve our performance, like "Wi-Fi & BLE Mesh Coexistence Performance", "Fast OTA Performance", etc.
* And we will release a version soon which has a much improved "Wi-Fi & BLE Mesh Coexistence Performance".

which ESP32 IDF version will be supported for that?
* If all goes well, I think IDF 4.0 or IDF 4.1 will be supported for "BLE Mesh SDK".

Currently, it doesn't store the data in NVS. So if you don't reboot the device, it should work finely. If it doesn't work on your side, could you tell us how to reproduce your issue?

BTW, for the "power-down memory" feature:
* We have finished the "NVS storage" of Mesh nodes and it will be released soon
* For the "NVS storage" of Provisioner device, it is on the development plan and will be released in the near future

Yes, it works perfect now. All necessary data are stored in ram. What I asked is "power-down memory" feature, but answer is satisfying my question, thanks for support.
About esp32 using as provisioner it is too early to me, as for now silab and nRF provisioners are working good.

Who is online

About Us

Espressif Systems is a fabless semiconductor company providing cutting-edge low power WiFi SoCs and wireless solutions for wireless communications and Internet of Things applications. ESP8266EX and ESP32 are some of our products.