• Bluetooth
  • Intermediate
  • 3 min
  • Serial CLI

Recipe · Intermediate · Bluetooth

How to test BLE HID keyboard and mouse mode

If you are developing BLE input workflows, Bit Pirate can act as a BLE HID keyboard or mouse. Keep this recipe limited to your own paired test host.

Bluetooth connection between two devices.
Start the server, pair your own host, then send a small visible test action.
Step 1

Commands

Run the commands below after selecting the right Bit Pirate mode and confirming the wiring.

Result

What success looks like

The host shows the typed text or cursor action. If nothing happens, the BLE server may be running but not connected or paired.

Troubleshooting

  • Server was not started before keyboard/mouse commands.
  • Host paired with an old BLE profile; remove and re-pair.
  • No active text field selected for keyboard text.
  • Bluetooth state is stale; use reset and start again.

Next steps

  • Use keyboard bridge mode only in a safe text field.
  • Use reset before switching back to scanning/pairing tests.
  • Use USB HID mode if you need wired input instead of BLE.

BLE HID server FAQ

Which HID roles can the BLE server expose?

The BLE HID server can expose keyboard and mouse style reports to a paired host. Individual commands then send text, movement, clicks or other HID actions through that running service.

What should the host be ready to receive?

The host should be paired, connected and focused on an input context that can accept HID events. Treat BLE HID like a real keyboard or mouse rather than a text-only serial console.

When is USB HID better than BLE HID?

Use USB HID when you need a wired, lower-latency and less pairing-dependent workflow. Use BLE HID when wireless input is the point of the test.

Go deeper