Bluetooth GATT Characteristic Reference
Supported Heart Rate Range (0x2AD7)
The Supported Heart Rate Range characteristic is used to send the supported Heart Rate range as well as the minimum Heart Rate increment supported by the Server.
Quick Summary
Payload length is 3 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 | Supported Heart Rate Range |
| UUID | 0x2AD7 |
| Type | org.bluetooth.characteristic.supported_heart_rate_range |
| XML Root | Characteristic |
| Source File | org.bluetooth.characteristic.supported_heart_rate_range.xml |
| Field Count | 3 |
Field Specification
Parsed field definitions from the source XML value structure.
| Field | Requirement | Format | Unit | Exponent | Notes |
|---|---|---|---|---|---|
| Minimum Heart Rate | Mandatory | uint8 | org.bluetooth.unit.period.beats_per_minute | - | Beats per minute with a resolution of 1 |
| Maximum Heart Rate | Mandatory | uint8 | org.bluetooth.unit.period.beats_per_minute | - | Beats per minute with a resolution of 1 |
| Minimum Increment | Mandatory | uint8 | org.bluetooth.unit.period.beats_per_minute | - | Beats per minute with a resolution of 1 |
Byte Layout and Decode
Payload length is 3 bytes.
function decodePayload(dataView, offset = 0) {
const minimum_heart_rate = dataView.getUint8(offset + 0);
const maximum_heart_rate = dataView.getUint8(offset + 1);
const minimum_increment = dataView.getUint8(offset + 2);
return { minimum_heart_rate, maximum_heart_rate, minimum_increment };
}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 Supported Heart Rate Range in Bluetooth GATT?
Supported Heart Rate Range is defined as a Bluetooth GATT characteristic entry with type org.bluetooth.characteristic.supported_heart_rate_range and UUID 0x2AD7.
What UUID identifies Supported Heart Rate Range?
The UUID for Supported Heart Rate Range is 0x2AD7.
How should I parse Supported Heart Rate Range?
Payload length is 3 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.