lly 8fd34d4741 ble_mesh: example: Update example license 4 lat temu
..
main 8fd34d4741 ble_mesh: example: Update example license 4 lat temu
tutorial aa2a98899b ble_mesh: example: Fix example README & tutorial link error 5 lat temu
CMakeLists.txt 55c5d2953d ble_mesh: Add nvs operations for examples 5 lat temu
README.md 5b2fa1a5ad build_app: make multi target support readable 5 lat temu
sdkconfig.ci.bluedroid 7c1c669799 component/bt: add BLE v5.0 feature for bluedroid host 5 lat temu
sdkconfig.ci.bluedroid_deinit 7c1c669799 component/bt: add BLE v5.0 feature for bluedroid host 5 lat temu
sdkconfig.ci.model 7c1c669799 component/bt: add BLE v5.0 feature for bluedroid host 5 lat temu
sdkconfig.ci.nimble 7c1c669799 component/bt: add BLE v5.0 feature for bluedroid host 5 lat temu
sdkconfig.ci.nimble_deinit 7c1c669799 component/bt: add BLE v5.0 feature for bluedroid host 5 lat temu
sdkconfig.ci.proxy00 7c1c669799 component/bt: add BLE v5.0 feature for bluedroid host 5 lat temu
sdkconfig.ci.proxy01 7c1c669799 component/bt: add BLE v5.0 feature for bluedroid host 5 lat temu
sdkconfig.ci.proxy02 7c1c669799 component/bt: add BLE v5.0 feature for bluedroid host 5 lat temu
sdkconfig.ci.proxy03 7c1c669799 component/bt: add BLE v5.0 feature for bluedroid host 5 lat temu
sdkconfig.ci.proxy04 7c1c669799 component/bt: add BLE v5.0 feature for bluedroid host 5 lat temu
sdkconfig.ci.proxy05 7c1c669799 component/bt: add BLE v5.0 feature for bluedroid host 5 lat temu
sdkconfig.defaults 7c1c669799 component/bt: add BLE v5.0 feature for bluedroid host 5 lat temu
sdkconfig.defaults.esp32c3 6fc4bf7145 components/bt: Fix link error of Kconfig 4 lat temu
sdkconfig.defaults.esp32s3 6fc4bf7145 components/bt: Fix link error of Kconfig 4 lat temu

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.