Skip to content
AF

Supported Speed Range (0x2AD4): byte layout

GATT characteristic · org.bluetooth.characteristic.supported_speed_range · read from the Bluetooth SIG’s repository on 2026-10-17 · commit 408f4a0 (2026-10-14)

Supported Speed Range is Bluetooth GATT characteristic 0x2AD4, org.bluetooth.characteristic.supported_speed_range in the Bluetooth SIG's assigned numbers. The SIG's GATT Specification Supplement file lays its value out as 3 fields: Minimum Speed, Maximum Speed and Minimum Increment. Every field has a fixed size, 6 octets in all.

UUID
0x2AD4
Identifier
org.bluetooth.characteristic.supported_speed_range
The SIG’s description
The Supported Speed Range characteristic is used to represent the speed 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_speed_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.

OffsetFieldTypeSizePresent whenUnit
0Minimum Speeduint162Always (fixed size)velocity (kilometre per hour)org.bluetooth.unit.velocity.kilometre_per_hour
2Maximum Speeduint162Always (fixed size)velocity (kilometre per hour)org.bluetooth.unit.velocity.kilometre_per_hour
4Minimum Incrementuint162Always (fixed size)velocity (kilometre per hour)org.bluetooth.unit.velocity.kilometre_per_hour

Field notes

Each field’s text in the SIG’s file, line by line.

Minimum Speed uint16 · 2
Base Unit: org.bluetooth.unit.velocity.kilometre_per_hourRepresented values: M = 1, d = -2, b = 0Unit is 1/100 of a kilometer per hour
Maximum Speed uint16 · 2
Base Unit: org.bluetooth.unit.velocity.kilometre_per_hourRepresented values: M = 1, d = -2, b = 0Unit is 1/100 of a kilometer per hour
Minimum Increment uint16 · 2
Base Unit: org.bluetooth.unit.velocity.kilometre_per_hourRepresented values: M = 1, d = -2, b = 0Unit is 1/100 of a kilometer per hour

Guides on this site

The connected-device guides that name 0x2AD4:

Questions

What is the UUID of the Supported Speed Range characteristic?
0x2AD4. The Bluetooth SIG's characteristic_uuids.yaml lists Supported Speed Range as 0x2AD4 with the identifier org.bluetooth.characteristic.supported_speed_range. No file in the SIG's repository ties it to a service: the repository lists service and characteristic UUIDs separately.
Are any Supported Speed Range fields optional?
No. Every field in the SIG's structure has a size that cannot be zero: Minimum Speed (uint16, 2), Maximum Speed (uint16, 2) and Minimum Increment (uint16, 2).
What units does Supported Speed Range use?
The SIG's text names a unit for 3 of the 3 fields: Minimum Speed: velocity (kilometre per hour) (org.bluetooth.unit.velocity.kilometre_per_hour); Maximum Speed: velocity (kilometre per hour) (org.bluetooth.unit.velocity.kilometre_per_hour); Minimum Increment: velocity (kilometre per hour) (org.bluetooth.unit.velocity.kilometre_per_hour).
How many bytes is a Supported Speed Range value?
6 octets. Every field has a fixed size in the SIG's structure: Minimum Speed at offset 0 (uint16, 2), Maximum Speed at offset 2 (uint16, 2) and Minimum Increment at offset 4 (uint16, 2).

Source

Read on 2026-10-17 from gss/org.bluetooth.characteristic.supported_speed_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.

← All Bluetooth GATT characteristics