Belt Control — treadmill control in the browser

When the treadmill won't connect

Almost every Bluetooth problem with these pads is one of six things. Each one looks different, and telling them apart is most of the fix.

Nothing shows up in the device list

That list is drawn by your browser, not by this page, and it only shows what's switched on and nearby right now. An empty list usually means one of these:

On a Mac, an empty list often means a permission

Chrome needs your permission to use Bluetooth, under System Settings → Privacy & Security → Bluetooth. Without it the list opens, finds nothing, and shows no error at all — which looks exactly like a treadmill that's switched off. Turn it on, restart Chrome, and try again.

There's no Connect button, or pressing it does nothing

Then your browser can't connect to Bluetooth devices. Firefox and Safari can't — and on an iPhone or iPad, every browser is Safari underneath, so installing Chrome there doesn't help. Chrome, Edge, Opera and Samsung Internet can, on a computer or on Android.

There's no workaround for the iPhone. Use a computer or an Android device instead — see the full browser list.

One more thing: the page has to be loaded over a secure connection. That means an address starting https://, so beltcontrol.com is fine. Opening a downloaded copy of the page from your own hard drive isn't.

It connects, then drops out after a couple of seconds

That's certain KingSmith pads — the KS-C2 and its relatives — behaving exactly as designed. They hang up on anything that connects and then just listens, within about three seconds. It isn't a fault, and it isn't a range problem.

Belt Control knows the greeting those pads expect, so it shouldn't happen here. If you're seeing it with some other tool, that's why.

It connects, but the belt won't start

Common on the KS-C2, and the pad does tell us why. Three things to check, in order:

Also worth a glance at the treadmill's own display: an error code there is a hardware complaint, and no app can talk it out of one.

The numbers look wrong

Some of them are, and the app tries to be straight with you about which. Many newer pads don't count steps at all. Many older ones don't report calories. And where calories are a rough guess calculated from distance rather than a real measurement, the app marks them and keeps them out of your totals.

On the KS-C2 and its relatives, distance only updates every ten metres or so, so a short walk sits at zero for a while and then jumps. That's the treadmill's reporting pace, not a stalled connection.

Wherever a number is missing you'll see a dash. An app that invents a number to avoid an empty space is worse than one that admits it doesn't know.

It worked yesterday, and today my pad isn't offered

Your browser grants access to one device at a time, and only when you pick it from that list yourself — it won't hand it over any other way. Belt Control remembers your last treadmill and filters the list down to just that one, so reconnecting is a single click, but the list still has to open.

That's your browser's rule rather than ours, and it's a reasonable one for something that can start a motor.

Still stuck? The app keeps a record of what it tried and what your treadmill said back, and Send feedback attaches it to an email. That record is the useful part — it's how a pad nobody has seen before gets supported.

Open Belt Control