esp-idf/examples/bluetooth/esp_ble_mesh/ble_mesh_node/onoff_client
lly 73d22d8ed9 ble_mesh: example: Update sdkconfig test files for disabling Health Server model 2020-10-23 02:04:21 +00:00
..
main
tutorial
CMakeLists.txt
Makefile
README.md
sdkconfig.ci.bluedroid ble_mesh: ci: Enable settings in sdkconfig.ci.xxx 2020-09-14 08:40:12 +00:00
sdkconfig.ci.bluedroid_deinit ble_mesh: ci: Add disabling mesh deinit sdkconfig test files 2020-10-23 02:04:21 +00:00
sdkconfig.ci.model ble_mesh: example: Update sdkconfig test files for disabling Health Server model 2020-10-23 02:04:21 +00:00
sdkconfig.ci.nimble ble_mesh: ci: Enable settings in sdkconfig.ci.xxx 2020-09-14 08:40:12 +00:00
sdkconfig.ci.nimble_deinit ble_mesh: ci: Add disabling mesh deinit sdkconfig test files 2020-10-23 02:04:21 +00:00
sdkconfig.ci.proxy00
sdkconfig.ci.proxy01
sdkconfig.ci.proxy02
sdkconfig.ci.proxy03
sdkconfig.ci.proxy04
sdkconfig.ci.proxy05
sdkconfig.defaults

README.md

Supported Targets ESP32

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:

  1. Download and run this demo.
  2. Use any app for BLE Mesh to provision this device as well as the device running the Generic OnOff Server demo.
  3. After both onoff client and server devices are provisioned, use UART1 to input the unicast address of the element within the server device.
  4. The Generic OnOff Client will start to get and set Generic OnOff states periodically.

Notes:

  1. The NetKey index and AppKey index are fixed to 0x0000 in this demo.
  2. 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.