History

lly 8b2291a718 ble_mesh: Continue node info restore even if failure happens During BLE Mesh Provisioner initialization, the stack will restore the nodes information if settings storage is enabled. Previously when a failure happens (e.g. found the same uuid) during the restore procedure, the information of the following nodes will not be restored and error will be directly returned. But this will introduce some problem with user experience, because some newly provisioned nodes information will not be restored and Provisioner will not be able to control those nodes. So we change the operation here, when a failure happens during the restore procedure, Provisioner will only ignore the information of the current node and continue restoring other nodes information.		2020-04-30 11:50:15 +00:00
..
api	ble_mesh: Support BLE advertising simultaneously	2020-04-10 17:34:06 +08:00
btc	ble_mesh: Remove some redundant functions	2020-04-30 11:50:15 +00:00
mesh_common	ble_mesh: Use lock for mesh timer operations	2020-03-13 19:24:12 +08:00
mesh_core	ble_mesh: Continue node info restore even if failure happens	2020-04-30 11:50:15 +00:00
mesh_models	ble_mesh: Start the timer when starting to send the client message	2020-03-02 02:08:13 +00:00
Kconfig.in	ble_mesh: Remove BLE_MESH_MAX_STORED_NODES option	2020-04-30 11:50:15 +00:00
README.md	Provide BLE Mesh documentation	2019-10-30 17:01:18 +08:00

ESP-BLE-MESH Component

This is Espressif Bluetooth Low Energy Mesh component folder.

This component is a part of Espressif IoT Development Framework (ESP-IDF). For the latest documentation please refer to ESP-IDF Programming Guide.

The ESP-BLE-MESH networking enables many-to-many (m:m) device communications and is optimized for creating large-scale device networks.

Refer to ESP-BLE-MESH Examples of Getting Started for the tutorials of ESP BLE Mesh examples.