Bluetooth GATT Characteristic Reference
Three Zone Heart Rate Limits (0x2A94)
Data structure containing the limits between the heart rate zones for the 3-zone heart rate definition (Hard, Moderate and Light).
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 | Three Zone Heart Rate Limits |
| UUID | 0x2A94 |
| Type | org.bluetooth.characteristic.three_zone_heart_rate_limits |
| XML Root | Characteristic |
| Source File | org.bluetooth.characteristic.three_zone_heart_rate_limits.xml |
| Field Count | 2 |
Field Specification
Parsed field definitions from the source XML value structure.
| Field | Requirement | Format | Unit | Exponent | Notes |
|---|---|---|---|---|---|
| Three zone Heart Rate Limits - Light (Fat burn) / Moderate (Aerobic) Limit | Mandatory | uint8 | org.bluetooth.unit.period.beats_per_minute | 0 | Unit is in beats per minute with a resolution of 1 |
| Three zone Heart Rate Limits - Moderate (Aerobic) / Hard (Anaerobic) Limit | Mandatory | uint8 | org.bluetooth.unit.period.beats_per_minute | 0 | Unit is in beats per minute with a resolution of 1 |
Byte Layout and Decode
Payload length is 2 bytes.
function decodePayload(dataView, offset = 0) {
const three_zone_heart_rate_limits_light_fat_burn_moderate_aerobic_limit = dataView.getUint8(offset + 0);
const three_zone_heart_rate_limits_moderate_aerobic_hard_anaerobic_limit = dataView.getUint8(offset + 1);
return { three_zone_heart_rate_limits_light_fat_burn_moderate_aerobic_limit, three_zone_heart_rate_limits_moderate_aerobic_hard_anaerobic_limit };
}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 Three Zone Heart Rate Limits in Bluetooth GATT?
Three Zone Heart Rate Limits is defined as a Bluetooth GATT characteristic entry with type org.bluetooth.characteristic.three_zone_heart_rate_limits and UUID 0x2A94.
What UUID identifies Three Zone Heart Rate Limits?
The UUID for Three Zone Heart Rate Limits is 0x2A94.
How should I parse Three Zone Heart Rate Limits?
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.