If your pad speaks Bluetooth FTMS, it works. Here's who does.
Mosey contains no pad-specific code. It looks for the standard Fitness Machine Service that many pads broadcast, reads speed and incline from it, and drives the belt through it. So the question is never "does Mosey support my pad" but "does my pad speak the standard". Two rules of thumb: a listing that says Zwift or Kinomap compatible almost certainly does; one that says "works with our app only" almost certainly doesn't. Pads without incline walk the same rounds flat.
| Pad | Status | Why we think so | Incline |
|---|---|---|---|
| Sportstech sPad500 | Verified | The pad Mosey was built on. Speed, incline, start, stop and pace all confirmed live. Its FitShow module exposes standard FTMS alongside the vendor protocol. | 5 levels (≈ 15 % at the top) |
| Sportstech sWalk | Should work | FTMS confirmed by Sportstech's own Zwift list and QZ users. Some reports of a flaky link; the protocol is right. | — |
| Sportstech sWalk Plus | Should work | Same family and module as the sWalk. | — |
| Sportstech F37s | Should work | FTMS per Sportstech's Zwift list. A full-size treadmill. | yes |
| KingSmith WalkingPad Z1 | Should work | Routed to the generic FTMS driver in QZ. Some firmware gates control behind a vendor unlock; readings work regardless. | — |
| KingSmith WalkingPad R3 Hybrid+ | Should work | FTMS confirmed in QZ's device table. | — |
| KingSmith WalkingPad X218 | Should work | FTMS confirmed in QZ's device table. | — |
| KingSmith WalkingPad A1 | Won't work | Proprietary KingSmith protocol, no FTMS. Reverse-engineered by the ph4-walkingpad project; Mosey speaks only the standard. | — |
| KingSmith WalkingPad A1 Pro | Won't work | Proprietary, no FTMS. | — |
| KingSmith WalkingPad C1 | Won't work | Proprietary, no FTMS. | — |
| KingSmith WalkingPad C2 | Won't work | Proprietary, no FTMS. | — |
| KingSmith WalkingPad R1 / R1 Pro | Won't work | Proprietary, no FTMS. | — |
| KingSmith WalkingPad R2 | Won't work | A second, different KingSmith protocol. No FTMS. | — |
| KingSmith WalkingPad X21 | Won't work | Same second protocol as the R2. No FTMS. | — |
| KingSmith K12 Pro / MXG / G1C | Won't work | KingSmith's second protocol. The brand runs at least three incompatible Bluetooth stacks; only Z1, R3 and X218 speak the standard. | — |
| Urevo SpaceWalk 3S (URTM024) | Should work | FTMS confirmed in QZ's source. | — |
| Urevo SpaceWalk E1L | Won't work | Proprietary — unlike its sibling. The treadspan project needed a hardware bridge imitating the vendor app. | — |
| Urevo SpaceWalk E4W | Unknown | Sold with the UREVO SmartCoach app; no FTMS evidence either way yet. | — |
| Mobvoi Home Treadmill / Pro / Plus | Should work | Mobvoi advertises Zwift and Kinomap, which are FTMS-only; QZ confirms FTMS. | — |
| Toputure TP6 | Should work | Explicitly flagged FTMS in QZ. | — |
| WELLFIT walking pads and TM treadmills | Should work | WELLFIT states its machines support FitShow, Zwift, Kinomap "and other apps that support the FTMS protocol". | some models |
| FYSIQ walking pad | Should work | The listing states the FTMS Bluetooth protocol outright. | — |
| LifeSmart TM series | Should work | FTMS confirmed in QZ. Full-size treadmills. | yes |
| THERUN T15 | Should work | FTMS confirmed in QZ. | yes |
| Egofit Walker Pro / Plus (M1T) | Should work | Uses the FitShow app, and FitShow modules expose standard FTMS beside the vendor protocol — the same pattern as the sPad500. Not yet verified by us. | fixed 5 % |
| Any pad sold with the "FitShow" app (FS-… names) | Should work | The FitShow module answers both its own protocol and FTMS. Common across the budget tier. | varies |
| Bluefin Fitness Task 2.0 | Should work | Advertises Kinomap, which is FTMS-only. Unverified. | — |
| DeerRun (all models, PitPat app) | Won't work | The PitPat protocol is proprietary with an unlock handshake and no FTMS fallback. | — |
| Superun (PitPat app) | Won't work | Same PitPat module as DeerRun. | — |
| Sperax RM01 / RM-02 / RM-P series | Won't work | Proprietary (Sperax Fitness app), no FTMS. Firmware varies across batches; we've seen no FTMS unit. | — |
| LifeSpan treadmill desks | Won't work | Proprietary serial protocol. | — |
| Goplus / Gymax walking pads | Unknown | Sold with the Gymax app; protocol undocumented. | — |
| Lichico / YRUN (Besyfit app) | Unknown | Protocol undocumented. | some models |
| Citysports ZX1 and others | Unknown | OEM-rebadged; the Bluetooth module can differ batch to batch. | — |
| KESSER walking pads | Unknown | OEM-rebadged; undocumented. | — |
| Redliro walking pads | Unknown | Undocumented. | — |
| Walkolution | Won't work | Manual, motor-less pads — there is no belt to drive. | — |
Same pad, different name
This list is not the world. Nearly every walking pad is built by a handful of factories in Zhejiang and Guangdong and sold under a local brand — one design can carry five names across Amazon.de, Amazon.com, Otto and Best Buy, and the same brand can switch factories between batches. So the name on the box tells you little. What decides whether Mosey works is the Bluetooth module inside, and there are only a few of those:
| Module family | How you recognise it | Mosey |
|---|---|---|
| FitShow | The box says to install the FitShow app; the pad shows up in Bluetooth as FS-…. Made by FitShow (Xiamen), sold to dozens of brands — they publish no list of them. | Works — the module speaks FTMS beside its own protocol |
| FitHome | Bluetooth name like JJ-BT…; the module inside the Sportstech sPad500. | Works — verified |
| KingSmith, newer | WalkingPad Z1, R3, X218; KS Fit app; Bluetooth name KS-HD-…, KS-AP-…, KS-NG-…. Also sold as Toputure. | Works |
| KingSmith, older | WalkingPad A1, C1, C2, R1, R2, X21, K12; KS Fit app. Also the Xiaomi-branded WalkingPads. | Won't — two proprietary protocols, no FTMS |
| PitPat | The box says PitPat; Bluetooth name PITPAT-…. DeerRun, Superun and many Amazon brands. | Won't — proprietary with an unlock handshake |
| Sperax | Sperax Fitness app; models RM-… | Won't |
| Zwift or Kinomap on the box | Whatever the brand: both apps talk only FTMS, so the pad must. | Works |
How to check yours in one minute: turn the pad on, open your phone's Bluetooth settings or the app the box told you to install, and read the device name. FS-…, JJ-BT…, KS-HD/AP/NG-… or a Zwift badge means Mosey will find it. PITPAT-…, RM-… or an older KS-… means it won't. Or just install Mosey: if the pad speaks the standard it appears in the list during setup, and if it doesn't, nothing breaks.
Knowing you're on the belt
One more thing the module decides. Mosey starts each walk at a crawl and lifts to the walk's own pace the moment the pad feels your steps — which it can only do on pads that count footfalls and say so over Bluetooth. The sPad500 does (verified). On a pad that doesn't, Mosey assumes you're on the belt and the walk starts at its own pace right away, as it did before. Either way the walk works; the door-holding is the extra.
A word on names
Mosey is independent. It is not affiliated with, endorsed by or connected to any of the makers named on this page; their product names are their trademarks and appear here only to say which devices speak the standard. Compatibility is our best knowledge and can change with a firmware update. And a walking pad is a motorized machine: the terms say how to use Mosey with one safely.
Your pad isn't here?
Install Mosey and look: if your pad speaks the standard it simply appears in the list during setup. If it doesn't, nothing breaks — and an email with the model name gets it onto this page, whichever way it turns out. Evidence for this list comes from the QDomyos-Zwift device drivers, the walkingpad-controller and ph4-walkingpad projects, manufacturers' own Zwift and Kinomap pages, and our own pad.