6d87100a70
Specifying all the dependencies (managed and local) in the manifest makes it easier for users to see every component the example depends on. |
||
---|---|---|
.. | ||
main | ||
tutorial | ||
CMakeLists.txt | ||
README.md | ||
sdkconfig.ci.adv | ||
sdkconfig.ci.bluedroid | ||
sdkconfig.ci.bluedroid_deinit | ||
sdkconfig.ci.bluedroid_log | ||
sdkconfig.ci.model | ||
sdkconfig.ci.nimble | ||
sdkconfig.ci.nimble_deinit | ||
sdkconfig.ci.nimble_log | ||
sdkconfig.ci.scan | ||
sdkconfig.defaults | ||
sdkconfig.defaults.esp32c3 | ||
sdkconfig.defaults.esp32c6 | ||
sdkconfig.defaults.esp32h2 | ||
sdkconfig.defaults.esp32s3 |
Supported Targets | ESP32 | ESP32-C3 | ESP32-C6 | ESP32-H2 | ESP32-S3 |
---|
ESP BLE Mesh Node demo
This demo shows how BLE Mesh device can be set up as a node with the following features:
- One element
- Two SIG models
- Configuration Server model: The role of this model is mainly to configure Provisioner device’s AppKey and set up its relay function, TTL size, subscription, etc.
- OnOff Server model: This model implements the most basic function of turning the lights on and off.
The default purpose of this demo is to enable the advertising function with 20-ms non-connectable interval in BLE 5.0. You can disable this function through menuconfig: idf.py menuconfig --> Example Configuration --> This option facilitates sending with 20ms non-connectable interval...
For a better demonstration effect, an RGB LED can be soldered onto the ESP32-DevKitC board, by connecting their corresponding GPIO pins are GPIO_NUM_25, GPIO_NUM_26, GPIO_NUM_27. Then you need to select the following option in menuconfig:
idf.py menuconfig --> Example Configuration --> Board selection for BLE Mesh --> ESP-WROOM-32
Please check the tutorial for more information about this example.