OVMS3-idf/examples/bluetooth/esp_ble_mesh/ble_mesh_node/onoff_client
lly b19671e0d4 ble_mesh: Add ESP BLE Mesh implementation
1. BLE Mesh Core

    * Provisioning: Node Role
        * PB-ADV and PB-GATT
        * Authentication OOB

    * Provisioning: Provisioner Role
        * PB-ADV and PB-GATT
        * Authentication OOB

    * Networking
        * Relay
        * Segmentation and Reassembly
        * Key Refresh
        * IV Update

    * Proxy Support

    * Multiple Client Models Run Simultaneously
        * Support multiple client models send packets to different nodes simultaneously
        * No blocking between client model and server

    * NVS Storage
        * Store BLE Mesh node related information in flash
        * Store BLE Mesh Provisioner related information in flash

2. BLE Mesh Models

    * Foundation Models
        * Configuration Server Model
        * Configuration Client Model
        * Health Server Model
        * Health Client Model

    * Generic
        * Generic OnOff Server
        * Generic OnOff Client
        * Generic Level Server
        * Generic Level Client
        * Generic Default Transition Time Server
        * Generic Default Transition Time Client
        * Generic Power OnOff Server
        * Generic Power OnOff Setup Server
        * Generic Power OnOff Client
        * Generic Power Level Server
        * Generic Power Level Setup Server
        * Generic Power Level Client
        * Generic Battery Server
        * Generic Battery Client
        * Generic Location Server
        * Generic Location Setup Server
        * Generic Location Client
        * Generic Admin Property Server
        * Generic Manufacturer Property Server
        * Generic User Property Server
        * Generic Client Property Server
        * Generic Property Client

    * Sensor Server Model
        * Sensor Server
        * Sensor Setup Server
        * Sensor Client

    * Time and Scenes
        * Time Server
        * Time Setup Server
        * Time Client
        * Scene Server
        * Scene Setup Server
        * Scene Client
        * Scheduler Server
        * Scheduler Setup Server
        * Scheduler Client

    * Lighting
        * Light Lightness Server
        * Light Lightness Setup Server
        * Light Lightness Client
        * Light CTL Server
        * Light CTL Setup Server
        * Light CTL Client
        * Light CTL Temperature Server
        * Light HSL Server
        * Light HSL Setup Server
        * Light HSL Client
        * Light HSL Hue Server
        * Light HSL Saturation Server
        * Light xyL Server
        * Light xyL Setup Server
        * Light xyL Client
        * Light LC Server
        * Light LC Setup Server
        * Light LC Client

3. BLE Mesh Applications

    * BLE Mesh Node
        * OnOff Client Example
        * OnOff Server Example

    * BLE Mesh Provisioner
        * Example

    * Fast Provisioning
        * Vendor Fast Prov Server Model
        * Vendor Fast Prov Client Model
        * Examples

    * Wi-Fi & BLE Mesh Coexistence
        * Example

    * BLE Mesh Console Commands
        * Examples
2020-02-03 12:03:36 +08:00
..
components/button ble_mesh: Add ESP BLE Mesh implementation 2020-02-03 12:03:36 +08:00
main ble_mesh: Add ESP BLE Mesh implementation 2020-02-03 12:03:36 +08:00
tutorial ble_mesh: Add ESP BLE Mesh implementation 2020-02-03 12:03:36 +08:00
CMakeLists.txt ble_mesh: Add ESP BLE Mesh implementation 2020-02-03 12:03:36 +08:00
Makefile ble_mesh: Add ESP BLE Mesh implementation 2020-02-03 12:03:36 +08:00
README.md ble_mesh: Add ESP BLE Mesh implementation 2020-02-03 12:03:36 +08:00
sdkconfig.defaults ble_mesh: Add ESP BLE Mesh implementation 2020-02-03 12:03:36 +08:00

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.