Foot pedal and keyboard shortcut fire at the same time

Pedal Three adds foot-operated inputs to a keyboard workflow. If pressing a pedal appears to trigger two actions, inspect the path from the pedal's assignment to the application's command rules. A duplicate sequence, overlapping remappers or a modifier held on the main keyboard can create different outcomes. Capture exactly what happens before removing useful bindings indiscriminately.

Are there two actions or one action repeated?

Describe the visible result. Opening a panel twice differs from opening a panel and typing a character into it. Compare a short pedal tap with a hold, and test with both hands away from the keyboard. This helps identify whether a manually held modifier is combining with the pedal's output.

Use a disposable workspace and a navigation command for the diagnosis. Keep send, delete and execute actions outside the test. If the same command repeats, record whether repetition stops on release. If two distinct commands occur, inspect the mapping sequence and rule scope next.

Is more than one utility handling the event?

List the device configuration tool, host remapper, application shortcut settings and any automation utility that watches the same input. Some tools only configure hardware; others remain active and translate events. Do not count them as equivalent merely because both show a list of keys.

Pause one relevant translation rule through its normal reversible controls, then repeat the test. Keep the original settings written down. The aim is to establish which layer adds the extra action, not to disable every input tool and rebuild the desktop from memory.

Does the application have overlapping bindings?

Inspect the command assigned to the detected chord in the context where it fires. An application may evaluate conditional bindings differently depending on which panel is focused. VS Code's keyboard troubleshooting command shows detected input and the command it selects, which helps distinguish an app rule from an earlier translation.

A macro that types a chord and then a separate key can also produce a second action after focus changes. Check whether the sequence contains an unnecessary confirmation or repeated event. Replace it with a simpler supported assignment when that meets the intended use.

What should the final input route look like?

Write the route as one clear sequence: pedal output, required translation and destination command. Test with the main keyboard idle, then during the ordinary hand movements that accompany your task. Confirm that neither device's normal behaviour changed unexpectedly. The Pedal Three controls need configuration, and a dependable setup makes each physical press correspond to an outcome you can explain.