Supported Resistance Level Range (0x2AD6): byte layout
GATT characteristic · org.bluetooth.characteristic.supported_resistance_level_range · read from the Bluetooth SIG’s repository on 2026-10-17 · commit 408f4a0 (2026-10-14)
Supported Resistance Level Range is Bluetooth GATT characteristic 0x2AD6, org.bluetooth.characteristic.supported_resistance_level_range in the Bluetooth SIG's assigned numbers. The SIG's GATT Specification Supplement file lays its value out as 3 fields: Minimum Resistance Level, Maximum Resistance Level and Minimum Increment. Every field has a fixed size, 3 octets in all.
- UUID
- 0x2AD6
- Identifier
org.bluetooth.characteristic.supported_resistance_level_range- The SIG’s description
- The Supported Resistance Level Range characteristic is used to represent the resistance level range supported by a fitness machine.The structure of this characteristic is defined below.
- Service the SIG’s files tie it to
- None: no file in the repository lists this characteristic under a service.
- Source file
- gss/org.bluetooth.characteristic.supported_resistance_level_range.yaml
Byte layout: 3 fields
In the order the SIG’s structure lists them. Type and size are as published; sizes count octets except where a struct is marked as sized in bits. The offset is printed only where every earlier field has a fixed size; where an earlier field can be absent or vary, the cell names what it depends on. “Present when” is read from the field’s own “Present if” line, shown in full in the field notes below.
| Offset | Field | Type | Size | Present when | Unit |
|---|---|---|---|---|---|
| 0 | Minimum Resistance Level | uint8 | 1 | Always (fixed size) | unitlessorg.bluetooth.unit.unitless |
| 1 | Maximum Resistance Level | uint8 | 1 | Always (fixed size) | unitlessorg.bluetooth.unit.unitless |
| 2 | Minimum Increment | uint8 | 1 | Always (fixed size) | unitlessorg.bluetooth.unit.unitless |
Field notes
Each field’s text in the SIG’s file, line by line.
- Minimum Resistance Level uint8 · 1
- Base Unit: org.bluetooth.unit.unitlessRepresented values: M = 1, d = 1, b = 0Unit is 1
- Maximum Resistance Level uint8 · 1
- Base Unit: org.bluetooth.unit.unitlessRepresented values: M = 1, d = 1, b = 0Unit is 1
- Minimum Increment uint8 · 1
- Base Unit: org.bluetooth.unit.unitlessRepresented values: M = 1, d = 1, b = 0Unit is 1
Guides on this site
The connected-device guides that name 0x2AD6:
Questions
- What is the UUID of the Supported Resistance Level Range characteristic?
- 0x2AD6. The Bluetooth SIG's characteristic_uuids.yaml lists Supported Resistance Level Range as 0x2AD6 with the identifier org.bluetooth.characteristic.supported_resistance_level_range. No file in the SIG's repository ties it to a service: the repository lists service and characteristic UUIDs separately.
- Are any Supported Resistance Level Range fields optional?
- No. Every field in the SIG's structure has a size that cannot be zero: Minimum Resistance Level (uint8, 1), Maximum Resistance Level (uint8, 1) and Minimum Increment (uint8, 1).
- What units does Supported Resistance Level Range use?
- The SIG's text names a unit for 3 of the 3 fields: Minimum Resistance Level: unitless (org.bluetooth.unit.unitless); Maximum Resistance Level: unitless (org.bluetooth.unit.unitless); Minimum Increment: unitless (org.bluetooth.unit.unitless).
- How many bytes is a Supported Resistance Level Range value?
- 3 octets. Every field has a fixed size in the SIG's structure: Minimum Resistance Level at offset 0 (uint8, 1), Maximum Resistance Level at offset 1 (uint8, 1) and Minimum Increment at offset 2 (uint8, 1).
Source
Read on 2026-10-17 from gss/org.bluetooth.characteristic.supported_resistance_level_range.yaml and assigned_numbers/uuids/characteristic_uuids.yaml in the Bluetooth SIG’s public repository (branch main, commit 408f4a0, committed 2026-10-14), by scripts/fetch-bluetooth-gatt.mjs. The file’s notice says it is proprietary to Bluetooth SIG, that furnishing it grants no licence, and that it is subject to change without notice; it is © Bluetooth SIG, Inc., and its text is quoted here for identification. Generated by AIFitnessAPI, which is not affiliated with Bluetooth SIG; the SIG’s file remains the authority. The full notice and the conventions used on these pages are on the reference hub.