mirror of
https://github.com/espressif/esp-idf.git
synced 2024-10-05 20:47:46 -04:00
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.bluedroid | ||
sdkconfig.ci.bluedroid_deinit | ||
sdkconfig.ci.model | ||
sdkconfig.ci.nimble | ||
sdkconfig.ci.nimble_deinit | ||
sdkconfig.ci.proxy00 | ||
sdkconfig.ci.proxy01 | ||
sdkconfig.ci.proxy02 | ||
sdkconfig.ci.proxy03 | ||
sdkconfig.ci.proxy04 | ||
sdkconfig.ci.proxy05 | ||
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 Client Model Demo
This demo shows how to use the Generic OnOff Client Model to get/set the generic on/off state. The basic procedures are as follows:
- Download and run this demo.
- Use any app for BLE Mesh to provision this device as well as the device running the Generic OnOff Server demo.
- After both onoff client and server devices are provisioned, use UART1 to input the unicast address of the element within the server device.
- The Generic OnOff Client will start to get and set Generic OnOff states periodically.
Notes:
- The NetKey index and AppKey index are fixed to 0x0000 in this demo.
- If the client device is re-provisioned, but the server device is not, the first few get/set messages from the client will be treated as replay attacks. To avoid this, both devices should be re-provisioned prior to transmitting messages.