Skip to content

fix: scale FTMS speed commands for Horizon T202 - #4904

Merged
cagnulein merged 1 commit into
masterfrom
fix/horizon-t202-ftms-speed
Aug 10, 2026
Merged

fix: scale FTMS speed commands for Horizon T202#4904
cagnulein merged 1 commit into
masterfrom
fix/horizon-t202-ftms-speed

Conversation

@cagnulein

@cagnulein cagnulein commented Aug 9, 2026

Copy link
Copy Markdown
Owner

Summary

  • Detects JFTM T202* Horizon treadmill devices.
  • Converts the FTMS target-speed command from km/h to mph for this model family.
  • Keeps the workaround scoped to the T202 and leaves other Horizon/FTMS treadmill paths unchanged.

Background

mail Horizon t202 on 9/8/2026

The supplied debug log showed the treadmill interpreting FTMS speed commands with an approximately 1.609 scaling factor:

  • QZ requested 1.0, the treadmill reported approximately 1.6.
  • QZ requested 1.4, the treadmill reported approximately 2.2.
  • A decrease command could therefore make the treadmill speed increase.

The log also showed that the FTMS path was active (JFTM T202-5_4DEE, FTMS service 0x1826, Control Point 0x2AD9, and horizon_treadmill_force_ftms=true).

Implementation

The T202 is identified from the BLE name prefix and the target speed is converted with the existing 0.621371 miles conversion before encoding FTMS_SET_TARGET_SPEED.

Test plan

  • git diff --check
  • Build QZ library with qmake/make (build/)
  • Verify the diff is limited to horizontreadmill.cpp and horizontreadmill.h
  • Validate on a physical Horizon/JFTM T202 with + and -

@cagnulein
cagnulein merged commit 3e6c278 into master Aug 10, 2026
26 of 28 checks passed
@cagnulein
cagnulein deleted the fix/horizon-t202-ftms-speed branch August 10, 2026 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant