Bluetooth GATT Descriptor Reference
Value Trigger Setting (0x290A)
The value of the descriptor has two parts. Part one is a condition field and occupies one octet, and part two is the comparison value (trigger point) that the characteristic value is checked against.
Quick Summary
Payload length is profile-defined or variable based on field formats. This page is generated from official GATT XML and presented as implementation-ready guidance.
At a Glance
Key reference details for BLE implementation, interoperability testing, and AI-assisted troubleshooting.
| Property | Value |
|---|---|
| Name | Value Trigger Setting |
| UUID | 0x290A |
| Type | org.bluetooth.descriptor.value_trigger_setting |
| XML Root | Descriptor |
| Source File | org.bluetooth.descriptor.value_trigger_setting.xml |
| Field Count | 4 |
Field Specification
Parsed field definitions from the source XML value structure.
| Field | Requirement | Format | Unit | Exponent | Notes |
|---|---|---|---|---|---|
| Condition | Mandatory | uint8 | - | - | - |
| Value (Analog) | C2 | uint16 | - | - | - |
| Value (Bit Mask) | C3 | N/A | - | - | - |
| Value (Analog Interval) | C4 | uint32 | - | - | Analog One (uint16), Analog Two (uint16) |
Byte Layout and Decode
Payload length is profile-defined or variable based on field formats.
function decodePayload(dataView, offset = 0) {
const condition = dataView.getUint8(offset + 0);
const value_analog = dataView.getUint16(offset + 1, true);
// Parse value_bit_mask (N/A) according to Bluetooth format rules.
const value_analog_interval = dataView.getUint32(offset + 3, true);
return { condition, value_analog, value_bit_mask, value_analog_interval };
}Use Cases and Integration Notes
Descriptor Validation
Verify descriptor presence and format during integration and interoperability testing.
Client Configuration
Use descriptor semantics to configure notifications, indications, or presentation metadata.
Debug Diagnostics
Capture descriptor values alongside characteristic data for deeper BLE troubleshooting.
Implementation Checklist
- Read descriptor metadata after characteristic discovery to confirm behavior contracts.
- Respect descriptor read/write requirements before ATT operations.
- Document descriptor values in exported BLE session logs for reproducibility.
- Keep descriptor handling aligned with Bluetooth SIG format definitions.
FAQ
What is Value Trigger Setting in Bluetooth GATT?
Value Trigger Setting is defined as a Bluetooth GATT descriptor entry with type org.bluetooth.descriptor.value_trigger_setting and UUID 0x290A.
What UUID identifies Value Trigger Setting?
The UUID for Value Trigger Setting is 0x290A.
How should I parse Value Trigger Setting?
Payload length is profile-defined or variable based on field formats.
Where does this definition come from?
This page is generated from the Bluetooth SIG mirror XML in the oesmith/gatt-xml repository.
How does this page support BLE implementation?
The page combines structured tables, practical Q&A, and JSON-LD metadata to help teams validate integrations and troubleshoot consistently.