Troubleshooting

Troubleshooting

Symptom	Cause / fix
Monitor shows no controller (Mac)	Another program holds the Xbox controller (old PadBridge version, 360Controller kext). Try another USB cable or hub; some cables only charge.
Monitor shows no controller (Linux)	User not in the input group, or not logged in again since being added.
PS4 controller appears on the Mac as "(Bluetooth)" although it is on the cable	The cable only charges. Use a data cable or disconnect Bluetooth (hold the PS button for 10 s).
LED ring / light bar "Nicht verfügbar" (Linux)	udev rule from part 2 missing; replug the pad after setting it up.
Status orange "keine Antwort" (no answer)	On the peer, receiving is off or PadBridge is not running, the firewall blocks, wrong host/port, or different keys (the most common case with a new installation that created its own). Packets with a wrong signature are dropped silently: copy the key and paste it on the other side (part 5).
"Port 48100 nicht verfügbar" (not available)	The old padbridge-netpad or an older PadBridge holds the port. A service from 0.5 on hands it to the window by itself.
A second start opens no second window	On purpose: it brings the open window to the front.
"ViGEmBus ist nicht installiert" (Windows)	Install the driver (part 3). MIDI and keyboard/mouse work without it.
Status page does not load	Firewall: open TCP 48180 (Windows: allow private networks on the first start). Phone and computer must be in the same network or connected through Tailscale.
Pad missing on Linux	No write access to /dev/uinput (input group, log in again).
Two pads in the game	Switch off gamepad support in Moonlight.
Bitwig sees no MIDI	Load snd-virmidi (part 6) and pick VirMIDI, not "PadBridge".
LED ring does not follow the clock	The DAW must send clock to PadBridge or VirMIDI, and the MIDI target must match the DAW (this computer or peer).
Keyboard/mouse on the Mac has no effect	Accessibility permission missing or outdated after a new build (part 1).
"kein MIDI-Port ‚PadBridge'" (no MIDI port, Windows)	Create a port with exactly this name in loopMIDI and restart PadBridge (part 3).
MIDI device "lässt sich nicht öffnen" (cannot be opened, Windows)	Another program (DAW, vendor editor) has it open. Close it there, or use the PadBridge port in the DAW instead.
Keys stay stuck	Should not happen: the peer releases everything after 500 ms without packets. If it does, switch "aktiv" off and on again.