Bluetooth Low Energy Mesh Protocol Specification

This topic describes how to configure standard fields for Bluetooth Low Energy (LE) mesh networking to implement Bluetooth LE mesh device discovering and provisioning. After you complete the configuration, a provisioner, typically the app or gateway, can then provision a Bluetooth LE mesh device.

Configure UUID

Bluetooth mesh specification specifies:

• An unprovisioned device must support PB-ADV and may support PB-GATT.
• A provisioner must support both PB-ADV and PB-GATT or at least one of them.

Tuya Bluetooth LE mesh protocol specifies that a Bluetooth LE mesh device must support PB-ADV and PB-GATT, a mobile phone can provision a device through PB-GATT, and a gateway can provision a device through PB-ADV or PB-GATT.

Unprovisioned device beacon

• The unprovisioned device beacon is used by devices that are unprovisioned to allow them to be discovered by a provisioner. A provisioner can scan for nearby devices that are advertising and then get their product ID (PID). The format of this beacon is defined in the following figure.

  

• For the provisioner that does not support PB-ADV, such as the mobile phone, it provisions a device through PB-GATT. The format of advertising data is defined in the following figure.

  

Device UUID

The device UUID is composed of the device’s MAC address, mesh category, and PID.

UUID fields:

For example, if a device’s MAC address is 0x112233445566, mesh category is 0x1011, and PID is abcdefgh, this device’s UUID in hexadecimal notation is 11 22 33 44 55 66 10 11 61 62 63 64 65 66 67 68.

Mesh category

Product category description:

Device information

Fields of Composition Data Page 0 in Bluetooth mesh specification can be used to store device information.

Firmware version

Use VID (VERSION_ID) in Composition Data Page 0 to represent the firmware version that is displayed in ASCII format. For example, if VERSION_ID is 0x3533, it represents version 3.5.

Product information

Use PID (PRODUCT_ID) in Composition Data Page 0 to represent product ID.

• PRODUCT_ID Octet 0:

  Octet 0	RFU
  Bit width	8 bits
  Description	Reserved by Tuya

• PRODUCT_ID Octet 1:

  Octet 1	RFU	Key sharing	Device types
  Bit width	6 bits	1 bit	1 bit
  Description	Reserved by Tuya	Whether to support app_key sharing and sub sharing between models.	Device registration method

  Two device registration methods are available. 0 indicates registration through PID and 1 indicates registration through the product key. Only the Smart Life app support registration through the product key. For the logic of sharing model key and subscription address between models, you need to implement it in the firmware.