alex/esp-idf
alex/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2024-10-05 20:47:46 -04:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
d48c89b56a
esp-idf/examples/bluetooth/esp_ble_mesh/ble_mesh_client_model
History
Hrishikesh Dhayagude cba69dd088 Bluetooth examples restructuring 
The existing Bluetooth examples are split as:

1. examples/bluetooth/bluedroid - Bluedroid Host (BT + BLE) examples
   a. examples/bluetooth/bluedroid/classic_bt - Classic BT examples
   b. examples/bluetooth/bluedroid/ble - BLE examples
   c. examples/bluetooth/bluedroid/coex - Classic BT and BLE coex examples
   d. examples/bluetooth/bluedroid/hci - VHCI and HCI UART examples
      i. Rename ble_adv to controller_vhci_ble_adv and move it in hci folder
2. examples/bluetooth/nimble - NimBLE BLE Host + NimBLE Mesh examples
3. examples/bluetooth/esp_ble_mesh - ESP BLE Mesh examples
4. Update documentation references
2019-07-01 19:21:57 +08:00
..
main Bluetooth examples restructuring 2019-07-01 19:21:57 +08:00
tutorial Bluetooth examples restructuring 2019-07-01 19:21:57 +08:00
CMakeLists.txt Bluetooth examples restructuring 2019-07-01 19:21:57 +08:00
Makefile Bluetooth examples restructuring 2019-07-01 19:21:57 +08:00
README.md Bluetooth examples restructuring 2019-07-01 19:21:57 +08:00
sdkconfig.defaults Bluetooth examples restructuring 2019-07-01 19:21:57 +08:00

README.md

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.