Bluetooth GATT Characteristic Reference
Height (0x2A8E)
Height of the User
Quick Summary
Payload length is 2 bytes. 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 | Height |
| UUID | 0x2A8E |
| Type | org.bluetooth.characteristic.height |
| XML Root | Characteristic |
| Source File | org.bluetooth.characteristic.height.xml |
| Field Count | 1 |
Field Specification
Parsed field definitions from the source XML value structure.
| Field | Requirement | Format | Unit | Exponent | Notes |
|---|---|---|---|---|---|
| Height | Mandatory | uint16 | org.bluetooth.unit.length.meter | -2 | Unit is in meters with a resolution of 0.01 . |
Byte Layout and Decode
Payload length is 2 bytes.
function decodePayload(dataView, offset = 0) {
const height = dataView.getUint16(offset + 0, true);
return { height };
}Use Cases and Integration Notes
BLE Telemetry
Map characteristic values into dashboards and alerts for device observability.
Firmware Regression
Compare decoded fields across builds to detect protocol or scaling changes.
App Integration
Build stable parsing paths that convert raw payloads into typed app models.
Implementation Checklist
- Validate payload length and mandatory fields before decode.
- Decode with Bluetooth-specified signedness, unit, and exponent handling.
- Convert units at presentation boundaries to avoid drift in business logic.
- Persist raw packets and decoded values for reproducible troubleshooting.
FAQ
What is Height in Bluetooth GATT?
Height is defined as a Bluetooth GATT characteristic entry with type org.bluetooth.characteristic.height and UUID 0x2A8E.
What UUID identifies Height?
The UUID for Height is 0x2A8E.
How should I parse Height?
Payload length is 2 bytes.
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.