Bluetooth GATT Characteristic Reference
Indoor Bike Data (0x2AD2)
The Indoor Bike Data characteristic is used to send training-related data to the Client from an indoor bike (Server).
Quick Summary
Payload length is 30 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 | Indoor Bike Data |
| UUID | 0x2AD2 |
| Type | org.bluetooth.characteristic.indoor_bike_data |
| XML Root | Characteristic |
| Source File | org.bluetooth.characteristic.indoor_bike_data.xml |
| Field Count | 16 |
Field Specification
Parsed field definitions from the source XML value structure.
| Field | Requirement | Format | Unit | Exponent | Notes |
|---|---|---|---|---|---|
| Flags | Mandatory | 16bit | - | - | - |
| Instantaneous Speed | C1 | uint16 | org.bluetooth.unit.velocity.kilometre_per_hour | -2 | Kilometer per hour with a resolution of 0.01 |
| Average Speed | C2 | uint16 | org.bluetooth.unit.velocity.kilometre_per_hour | -2 | Kilometer per hour with a resolution of 0.01 |
| Instantaneous Cadence | C3 | uint16 | org.bluetooth.unit.angular_velocity.revolution_per_minute | - | 1/minute with a resolution of 0.5 |
| Average Cadence | C4 | uint16 | org.bluetooth.unit.angular_velocity.revolution_per_minute | - | 1/minute with a resolution of 0.5 |
| Total Distance | C5 | uint24 | org.bluetooth.unit.length.metre | - | Meters with a resolution of 1 |
| Resistance Level | C6 | sint16 | org.bluetooth.unit.unitless | - | Unitless with a resolution of 1 |
| Instantaneous Power | C7 | sint16 | org.bluetooth.unit.power.watt | - | Watts with a resolution of 1 |
| Average Power | C8 | sint16 | org.bluetooth.unit.power.watt | - | Watts with a resolution of 1 |
| Total Energy | C9 | uint16 | org.bluetooth.unit.energy.kilogram_calorie | - | Kilo Calorie with a resolution of 1 |
| Energy Per Hour | C9 | uint16 | org.bluetooth.unit.energy.kilogram_calorie | - | Kilo Calorie with a resolution of 1 |
| Energy Per Minute | C9 | uint8 | org.bluetooth.unit.energy.kilogram_calorie | - | Kilo Calorie with a resolution of 1 |
| Heart Rate | C10 | uint8 | org.bluetooth.unit.period.beats_per_minute | - | Beats per minute with a resolution of 1 |
| Metabolic Equivalent | C11 | uint8 | org.bluetooth.unit.metabolic_equivalent | -1 | Metabolic Equivalent with a resolution of 0.1 |
| Elapsed Time | C12 | uint16 | org.bluetooth.unit.time.second | - | Second with a resolution of 1 |
| Remaining Time | C13 | uint16 | org.bluetooth.unit.time.second | - | Second with a resolution of 1 |
Bit Map
Bit-level enumerations extracted from the XML BitField definition.
| Field | Bit | Size | Name | 0 Means | 1 Means |
|---|---|---|---|---|---|
| Flags | 0 | 1 | More Data | False | True |
| Flags | 1 | 1 | Instantaneous Cadence present | False | True |
| Flags | 2 | 1 | Average Speed present | False | True |
| Flags | 3 | 1 | Average Candence present | False | True |
| Flags | 4 | 1 | Total Distance Present | False | True |
| Flags | 5 | 1 | Resistance Level present | False | True |
| Flags | 6 | 1 | Instantaneous Power present | False | True |
| Flags | 7 | 1 | Average Power present | False | True |
| Flags | 8 | 1 | Expended Energy present | False | True |
| Flags | 9 | 1 | Heart Rate present | False | True |
| Flags | 10 | 1 | Metabolic Equivalent present | False | True |
| Flags | 11 | 1 | Elapsed Time present | False | True |
| Flags | 12 | 1 | Remaining Time present | False | True |
Byte Layout and Decode
Payload length is 30 bytes.
function decodePayload(dataView, offset = 0) {
// Parse flags (16bit) according to Bluetooth format rules.
const instantaneous_speed = dataView.getUint16(offset + 0, true);
const average_speed = dataView.getUint16(offset + 2, true);
const instantaneous_cadence = dataView.getUint16(offset + 4, true);
const average_cadence = dataView.getUint16(offset + 6, true);
// Parse total_distance (uint24) according to Bluetooth format rules.
const resistance_level = dataView.getInt16(offset + 8, true);
const instantaneous_power = dataView.getInt16(offset + 10, true);
const average_power = dataView.getInt16(offset + 12, true);
const total_energy = dataView.getUint16(offset + 14, true);
return { flags, instantaneous_speed, average_speed, instantaneous_cadence, average_cadence, total_distance };
}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 Indoor Bike Data in Bluetooth GATT?
Indoor Bike Data is defined as a Bluetooth GATT characteristic entry with type org.bluetooth.characteristic.indoor_bike_data and UUID 0x2AD2.
What UUID identifies Indoor Bike Data?
The UUID for Indoor Bike Data is 0x2AD2.
How should I parse Indoor Bike Data?
Payload length is 30 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.