Device Information
- Model: WalkingPad Z1F
- BLE device name: KS-HD-Z1D
- Protocol: FTMS (auto-detected correctly by the library)
- Firmware: V0.0.6
- Integration: mcdax/hass-walkingpad (latest via HACS)
- Library: walkingpad-controller >=0.4.11
- HA version: 2026.7.0
Description
The device connects successfully and all sensors populate correctly
(steps, distance, duration, calories, speed, state, mode). However,
every FTMS control point command times out and the belt cannot be
started from HA.
What I've ruled out
- Not a hardware issue — the KS Fit app can start and stop the
belt successfully when HA is disconnected
- Not a BLE conflict — the device's BLE remote also works when
HA releases the connection
- Not a connection issue — the library connects, detects FTMS
protocol, reads firmware version, speed range, and machine features
correctly
Relevant log entries
walkingpad_controller.controller: Detected FTMS protocol from BLE name 'KS-HD-Z1D' (prefix 'KS-HD-')
walkingpad_controller.ftms: FTMS: Connected to 82:20:00:29:B1:4F
walkingpad_controller.ftms: FTMS: Supplement service detected
walkingpad_controller.ftms: FTMS: Speed range: 1.60 - 6.40 km/h (step 0.10)
walkingpad_controller.ftms: FTMS: Machine features: 0x00001244, Target features: 0x00000001
walkingpad_controller.ftms: FTMS: Firmware version: V0.0.6
WARNING walkingpad_controller.ftms: FTMS: Control point response timeout for opcode 0x00
WARNING walkingpad_controller.ftms: FTMS: REQUEST_CONTROL was rejected — proceeding anyway
WARNING walkingpad_controller.ftms: FTMS: Control point response timeout for opcode 0x07
WARNING walkingpad_controller.ftms: FTMS: START_OR_RESUME rejected and belt is not moving
Hypothesis
The Z1F firmware V0.0.6 appears to require a different control point
initialization sequence than what the library currently sends. The
KS Fit app presumably satisfies this sequence correctly. This may be
similar to the vendor pre-amble already implemented for the MC-21
family, but specific to the KS-HD-Z1D device.
Happy to provide BLE packet captures or any additional diagnostics
if that would help identify the initialization sequence KS Fit is using.
WARNING walkingpad_controller.ftms: FTMS: Control point response timeout for opcode 0x08
Device Information
Description
The device connects successfully and all sensors populate correctly
(steps, distance, duration, calories, speed, state, mode). However,
every FTMS control point command times out and the belt cannot be
started from HA.
What I've ruled out
belt successfully when HA is disconnected
HA releases the connection
protocol, reads firmware version, speed range, and machine features
correctly
Relevant log entries
walkingpad_controller.controller: Detected FTMS protocol from BLE name 'KS-HD-Z1D' (prefix 'KS-HD-')
walkingpad_controller.ftms: FTMS: Connected to 82:20:00:29:B1:4F
walkingpad_controller.ftms: FTMS: Supplement service detected
walkingpad_controller.ftms: FTMS: Speed range: 1.60 - 6.40 km/h (step 0.10)
walkingpad_controller.ftms: FTMS: Machine features: 0x00001244, Target features: 0x00000001
walkingpad_controller.ftms: FTMS: Firmware version: V0.0.6
WARNING walkingpad_controller.ftms: FTMS: Control point response timeout for opcode 0x00
WARNING walkingpad_controller.ftms: FTMS: REQUEST_CONTROL was rejected — proceeding anyway
WARNING walkingpad_controller.ftms: FTMS: Control point response timeout for opcode 0x07
WARNING walkingpad_controller.ftms: FTMS: START_OR_RESUME rejected and belt is not moving
Hypothesis
The Z1F firmware V0.0.6 appears to require a different control point
initialization sequence than what the library currently sends. The
KS Fit app presumably satisfies this sequence correctly. This may be
similar to the vendor pre-amble already implemented for the MC-21
family, but specific to the KS-HD-Z1D device.
Happy to provide BLE packet captures or any additional diagnostics
if that would help identify the initialization sequence KS Fit is using.
WARNING walkingpad_controller.ftms: FTMS: Control point response timeout for opcode 0x08