Chapter 3. application solution
3.5.1 What is the maximum data transmission load for Bluetooth® LE (BLE) mesh?
• Up to 384 bytes for the single packet in application layer, up to 11 bytes in the bottom layer with no sub-
packages.
3.5.2 Could you provide an example of networking through ESP32 BLE-Mesh? What
APP can be used for BLE-Mesh networking?
• Please use example ono_server,and use nRF Mesh APP for mobile phones.
• For the network conguration process, please refer to Getting Started with ESP-BLE-MESH.
3.5.3 For unprovisioned device in BLE-MESH, the default name is ESP-BLE-MESH,
how to modify this name?
• You can use API esp_ble_mesh_set_unprovisioned_device_name(), it is suggested to call it after
esp_ble_mesh_init(), otherwise the device name is still ESP-BLE-MESH.
3.5.4 How many node devices can ESP32’s BLE-MESH application connect to?
• Theoretically, the ESP32 BLE-MESH application supports 32767 node devices. The number of connections
supported in actual application depends on the memory usage.
3.5.5 How can I manually reset a BLE mesh device without the mobile provisioning app
or provisioning device?
• You can call the esp_ble_mesh_node_local_reset interface to reset the BLE Mesh Node, erase all the provi-
sioning information, and wait until the reset event arrives to conrm a successful reset. After the call, the
device needs to be provisioned again.
3.5.6 After running the BLE MESH program for a long time on ESP32, it found that a
segmentation fault occurs when the client sends a message to the server and printed
NO multi-segment messsage contexts available. How to handle the
fault?
• User can go to Component config -> ESP BLE Mesh Support -> Maximum number
of simultaneous outgoing segmented messages and expand the space by conguring
BLE_MESH_TX_SEG_MSG_COUNT.
3.5.7 Can I turn o network keys and IV updates when using the ESP32 BLE Mesh
application?
• No, please don’t. Network keys and IV updates are required for using the application.
Espressif Systems 28
Submit Document Feedback
Release master