Why Is My Foot Pedal Not Working?

The most common reason a USB foot pedal does nothing is that nothing useful has been assigned to it, or that what is assigned is not what the app in front of you is listening for. Before you decide the pedal is faulty, open a plain text editor, click into it so it has focus, and press the pedal. If a character appears, the pedal works and your problem is further up the chain. If nothing appears at all, start at the top of the list below.

What should I check first?

The cable, then the port, in that order. A detachable USB lead can be a charge-only cable: it carries power but no data, which is easy to miss because some pedals light up regardless. Swap it for a lead you have already used to move data.

Then take everything out from between the pedal and the computer. Unpowered hubs, monitor hubs, keyboard pass-through ports and USB-C dongles are all common culprits. Plug the pedal straight in and try again. If the cable is captive, as it is on our Pedal Three, that removes one variable but the port advice still stands.

The pedal types in a text editor but does nothing in my app. Why?

Then it is a focus problem or a mapping problem, not a hardware one. A foot pedal is a plain input device: it sends a keystroke or a mouse click to whichever window currently has focus. If your terminal is not the front window when you press, the keystroke lands somewhere else entirely, which looks exactly like a dead pedal.

The other possibility is that the pedal is sending the wrong kind of event. A pedal set to send a left mouse click will do nothing in an app that only watches for keys. A pedal set to send a modifier on its own, Shift or Ctrl with nothing after it, produces no visible result by design. Find out what the pedal is actually configured to send before assuming it is broken.

Could something else be intercepting the press?

Yes, and this is the cause people usually find last. Remapping tools sit between the device and the operating system and can swallow an input before any application sees it. On macOS that is typically a keyboard customisation utility, on Windows a keyboard manager or a vendor control panel. Quit them one at a time and retest after each.

macOS adds a second trap. A utility that reads or rewrites input needs Input Monitoring or Accessibility permission, granted in the privacy section of System Settings. That prompt appears once. If it was dismissed, or if the app was updated and the permission lapsed, the tool runs but sees nothing and your pedal appears dead with no error anywhere. Switching the permission off and on again, then restarting the tool, is a fast way to rule it out.

Only one pedal is dead. Is the unit faulty?

Usually not. If two of three pedals work, the cable, the port and the connection are all proven fine, so the fault is nearly always in what that one pedal is assigned to send. The most common version of this is a mapping that was edited in a configuration tool but never written to the device: many configurators hold your changes in the interface until you press an explicit save or write step, and the pedal keeps its old behaviour until you do.

The mechanical cause worth ruling out is travel. A pedal on a rug or a cable mat may not reach the bottom of its stroke. Put it on a hard floor and press deliberately.

Where do our own pedals sit in all this?

Pedal Three at $69 and Pedal Four at $85 are ordinary USB input devices, which is a deliberately boring thing to be. There is no companion app running in the background, no account and no driver to install, so a good number of the failure modes above do not apply to them. That is not the same as saying they cannot fail, and we have not tried every combination of hub, dongle and operating system. If you want a pedal to send something other than its default, treat that as a separate step and ask us before you buy.

If the machine in question is a Mac, how USB foot pedals behave on macOS covers the platform specifics in more detail.