Foot pedal loses its mapping after switching USB ports

Pedal Three connects by USB and can be assigned shortcut actions through a supported configuration path. If moving its cable to another port changes the apparent mapping, first determine whether the device assignment changed or a host rule stopped matching. The port move is a useful trigger to reproduce. It is not proof that the pedal forgot its configuration.

What output appears on the new connection?

Use a blank local document and a harmless known assignment. Compare the output on the original and new ports without changing the profile. Write down whether ordinary input arrives, whether only the remapped action fails and whether modifiers behave differently. Keep other hardware connections stable during the comparison.

If the new path includes a dock or adapter, note that distinction. You are no longer comparing only two sockets on the same host. A direct connection can be a useful baseline when the computer supports it, but avoid unplugging a shared dock while it is carrying active storage or other important work.

Does the remapper still identify the device?

Open its device list or event inspector and see which entry receives the pedal press. A rule may match a device identifier, a particular connection attribute or another condition. Use the software's documented matching behaviour rather than assuming that a friendly device name is the whole rule.

The Karabiner device-rule specification illustrates how identifiers can scope input changes. Inspect the values reported by your own setup before editing. Different tools expose different fields, and not every field uniquely identifies an individual unit.

Could a profile or background process have changed?

Check which profile is active and whether the translating utility is still running. Reconnection can coincide with reopening an application or waking the computer, so the port may not be the only changed condition. Restore one dependency at a time and observe which step restores the expected action.

Keep the original settings exported or recorded before making replacements. Avoid a factory reset while basic input still works and the fault could be a matching rule. Resetting removes information and may create a larger configuration task without explaining the original behaviour.

How do you make the setup easier to recover?

Save the working connection route, active profile and the rule's actual matching criteria. Test a reconnect using the simplest input before returning to normal shortcuts. If the issue remains, provide those observations in a support request without unrelated device data. Consult Pedal Three's stated setup requirements and distinguish a device mapping from the computer-side rule that interprets it.

Back to blog