Crash_Override/OVMS3-idf
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
OVMS3-idf/examples/bluetooth/esp_ble_mesh/ble_mesh_node/onoff_client
History
lly 0e4faac0ee ble_mesh: Rename ble mesh example main & init files 
- Rename ble_mesh_demo_main.c to main.c
- Rename ble_mesh_demo_init.* to ble_mesh_example_init.*
2020-05-22 14:09:21 +08:00
..
main ble_mesh: Rename ble mesh example main & init files 2020-05-22 14:09:21 +08:00
tutorial ble_mesh: Add ESP BLE Mesh implementation 2020-02-03 12:03:36 +08:00
CMakeLists.txt ble_mesh: Move the example init to the components 2020-05-22 14:08:53 +08:00
Makefile ble_mesh: Move the example init to the components 2020-05-22 14:08:53 +08:00
README.md ble_mesh: Add ESP BLE Mesh implementation 2020-02-03 12:03:36 +08:00
sdkconfig.ci.bluedroid ble_mesh: Add bluedroid and nimble example configurations 2020-04-30 08:42:43 +00:00
sdkconfig.ci.nimble ble_mesh: Add bluedroid and nimble example configurations 2020-04-30 08:42:43 +00:00
sdkconfig.defaults ble_mesh: Add ESP BLE Mesh implementation 2020-02-03 12:03:36 +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.