1. BLE Mesh Core * Provisioning: Node Role * PB-ADV and PB-GATT * Authentication OOB * Provisioning: Provisioner Role * PB-ADV and PB-GATT * Authentication OOB * Networking * Relay * Segmentation and Reassembly * Key Refresh * IV Update * Proxy Support * Multiple Client Models Run Simultaneously * Support multiple client models send packets to different nodes simultaneously * No blocking between client model and server * NVS Storage * Store BLE Mesh node related information in flash * Store BLE Mesh Provisioner related information in flash 2. BLE Mesh Models * Foundation Models * Configuration Server Model * Configuration Client Model * Health Server Model * Health Client Model * Generic * Generic OnOff Server * Generic OnOff Client * Generic Level Server * Generic Level Client * Generic Default Transition Time Server * Generic Default Transition Time Client * Generic Power OnOff Server * Generic Power OnOff Setup Server * Generic Power OnOff Client * Generic Power Level Server * Generic Power Level Setup Server * Generic Power Level Client * Generic Battery Server * Generic Battery Client * Generic Location Server * Generic Location Setup Server * Generic Location Client * Generic Admin Property Server * Generic Manufacturer Property Server * Generic User Property Server * Generic Client Property Server * Generic Property Client * Sensor Server Model * Sensor Server * Sensor Setup Server * Sensor Client * Time and Scenes * Time Server * Time Setup Server * Time Client * Scene Server * Scene Setup Server * Scene Client * Scheduler Server * Scheduler Setup Server * Scheduler Client * Lighting * Light Lightness Server * Light Lightness Setup Server * Light Lightness Client * Light CTL Server * Light CTL Setup Server * Light CTL Client * Light CTL Temperature Server * Light HSL Server * Light HSL Setup Server * Light HSL Client * Light HSL Hue Server * Light HSL Saturation Server * Light xyL Server * Light xyL Setup Server * Light xyL Client * Light LC Server * Light LC Setup Server * Light LC Client 3. BLE Mesh Applications * BLE Mesh Node * OnOff Client Example * OnOff Server Example * BLE Mesh Provisioner * Example * Fast Provisioning * Vendor Fast Prov Server Model * Vendor Fast Prov Client Model * Examples * Wi-Fi & BLE Mesh Coexistence * Example * BLE Mesh Console Commands * Examples
93 lines
5 KiB
Markdown
93 lines
5 KiB
Markdown
# Demo Function
|
||
|
||
This demo demonstrates the fast provisioning of ESP BLE Mesh network and how to use the EspBleMesh app to control an individual provisioned node or all the provisioned nodes.
|
||
|
||
A video of this demo can be seen
|
||
[here](http://download.espressif.com/BLE_MESH/BLE_Mesh_Demo/V0.4_Demo_Fast_Provision/ESP32_BLE_Mesh_Fast_Provision.mp4)
|
||
|
||
# What You Need
|
||
|
||
* [EspBleMesh App for Android](http://download.espressif.com/BLE_MESH/BLE_Mesh_Tools/BLE_Mesh_App/EspBleMesh-0.9.4.apk)
|
||
* [ESP BLE Mesh SDK v0.6(Beta Version)](https://glab.espressif.cn/ble_mesh/esp-ble-mesh-v0.6)
|
||
* ESP32 Development Boards
|
||
|
||
> Note:
|
||
>
|
||
> 1. Please flash the [`ble_mesh_fast_prov_server`](https://glab.espressif.cn/ble_mesh/esp-ble-mesh-v0.6/tree/ble_mesh_release/esp-ble-mesh-v0.6/examples/bluetooth/esp_ble_mesh/ble_mesh_fast_provision/ble_mesh_fast_prov_server) to your boards first;
|
||
> 2. To have a better understanding of the performance of the BLE Mesh network, we recommend that at least 3 devices should be added in your network.
|
||
> 3. We recommend that you solder LED indicators if your development board does not come with lights.
|
||
> 4. Please check the type of board and LED pin definition enabled in `Example BLE Mesh Config` by running `idf.py menuconfig`
|
||
|
||
![Board](images/device.png)
|
||
|
||
|
||
# Flash and Monitor
|
||
|
||
1. Enter the directory:
|
||
examples/bluetooth/esp_ble_mesh/ble_mesh_fast_provision/ble_mesh_fast_prov_server
|
||
2. Make sure that the `IDF_PATH` environment variable was set in accordance with your current IDF path
|
||
3. Check the version of your toolchain. Version 4.1 or newer should be used.
|
||
|
||
![Checkenvironment](images/picture1.png)
|
||
|
||
4. Run `idf.py -p PORT flash` to compile codes and flash the codes to the device.
|
||
|
||
![compiledcode](images/picture2.png)
|
||
|
||
> Note:
|
||
>
|
||
> Please click on the Exit button if you see the following windows.
|
||
|
||
|
||
5. Please establish a connection between your device and PC, using the correct serial number, if you want to monitor the operation of this device on PC.
|
||
|
||
# How to Use the App
|
||
|
||
Please launch the `EspBleMesh` app, and follow the steps described below to establish a BLE Mesh network and control any individual node or all the nodes.
|
||
|
||
![App steps](images/app_ble.png)
|
||
1. Click on the upper left corner to see more options;
|
||
2. Click on **Provisioning** to scan nearby unprovisioned devices;
|
||
3. Choose any unprovisioned devices in the scanned list;
|
||
4. Enter the number of devices you want to add in your mesh network;
|
||
> Note:
|
||
>
|
||
> If you only want to use the normal provisioning feature,You don't check the option for fast provisioning.
|
||
5. Wait until all the devices are provisioned;
|
||
6. Click on the upper left corner to see more options;
|
||
7. Click on **Fast Provisioned** to see all the provisioned devices;
|
||
8. Control your devices.
|
||
|
||
> Note:
|
||
>
|
||
> Please disable your Bluetooth function on your phone, enable it and try again, if you have encountered any connection issues.
|
||
|
||
|
||
# Procedure
|
||
|
||
## Role
|
||
|
||
* Phone - Top Provisioner
|
||
* The device that has been provisioned by Phone - Primary Provisioner
|
||
* Devices that have been provisioned and changed to the role of a provisioner - Temporary Provisioner
|
||
* Devices that have been provisioned but not changed to the role of a provisioner - Node
|
||
|
||
## Interaction
|
||
|
||
![Interaction](images/time.png)
|
||
1. The Top Provisioner configures the first device to access the network with the GATT bearer.
|
||
2. The Top Provisioner sends the `send_config_appkey_add` message to allocate the Appkey to this device.
|
||
3. The Top Provisioner sends the `send_fast_prov_info_set` message to provide the necessary information so the device can be changed to a Primary Provisioner.
|
||
4. The device calls the `esp_ble_mesh_set_fast_prov_action` API to change itself into the role of a Primary Provisioner and disconnects with the Top Provisioner.
|
||
5. The Primary Provisioner sends the `send_config_appkey_add` message to allocate the Appkey to an other device.
|
||
6. The Primary Provisioner sends the `send_fast_prov_info_set` message to provide the necessary information so the device can be changed to a Temporary Provisioner.
|
||
7. The device calls the `esp_ble_mesh_set_fast_prov_action` API to change itself into the role of a Temporary Provisioner and starts its address timer.
|
||
8. The Temporary Provisioner collects the addresses of nodes that it has provisioned and sends these addresses to the Primary Provisioner, when its address timer times out, which indicates the Temporary Provisioner hasn't provisioned any devices for 10s.
|
||
9. The Primary Provisioner reconnects to the Top Provisioner when its address timer times out, which indicates the Primary Provisioner hasn't received any messages from the Temporary Provisioners for 10s.
|
||
10. The Top Provisioner sends the `node_adress_Get` message automatically after reconnecting with the Primary Provisioner.
|
||
11. At this point, the Top Provisioner is able to control any nodes in the BLE Mesh Network.
|
||
|
||
> Note:
|
||
>
|
||
> The nodes in the BLE Mesh Network only disable its provisioner functionality after it has been controlled by the Top Provisioner for at least one time.
|
||
|