Skip to content
DarkBeaconHelp
← All guides

DARKBEACON GUIDE

Fix a device that the App cannot find

Check selection, power, cable, supported connection, and application state before trying recovery or reset.

On this page

Applies to: Blade keyboards (61, 68, 84, 87, and 100), Flux keyboards (61, 68, 84, 87, and 100), Flux 68, Flux 84, and Flux 87 regional models, Devil Breaker and related keyboards, Steampunk, Other supported wireless keyboards shown in the App

Symptoms

The App shows no device, the wrong device, an unsupported state, or repeated disconnect and reconnect messages.

Applies to

Use this guide before reset, update, or recovery when a supported keyboard is missing or unstable in the App.

Low-risk checks

  1. Confirm that this device model is supported. If the App shows a PS5 mode card, follow Use PS5 keyboard mode to return to PC mode without clearing settings; configuration and firmware updates are unavailable in PS5 mode.
  2. Quit the App completely and reopen it. Check for a clear OS permission or application-update prompt; do not start a firmware update while the connection is unstable.
  3. Connect the keyboard directly to a PC port with the original or another known-good data cable, avoiding docks and hubs. Allow one full detection cycle.
  4. For wireless use, switch back to USB first. Once the USB connection is stable, switch to the matching Bluetooth or 2.4G connection.
  5. If disconnects repeat, leave the cable and device still for a while and note whether movement, sleep, mode switching, or a specific page triggers them.
  6. Once the keyboard is reliably identified in PC mode over USB, check the App for an applicable software or firmware update. Follow Update device firmware before starting; updating is not a prerequisite for these detection checks.

Recovery steps

Restart the App once; if the operating system itself also fails to see the device, restart the computer once. The App is working again when its home page shows the card for the correct device model and clicking that card opens the device's settings page.

On Windows, ordinary typing or a device listed without warnings does not guarantee that DarkBeacon App can read its settings. If the App reports Access denied or cannot identify the keyboard fully, another device-control application or a third-party driver may be interfering. This is a possibility, not a confirmed cause. See Recover from an interrupted or failed update for safe application-access checks and an explanation of possible driver interference; do not reset the keyboard or uninstall HID drivers blindly.

Stop conditions

Stop reconnecting if the device or cable becomes hot, smells unusual, has visible damage, disconnects during an update, or fails with more than one known-good data cable and port. Do not factory-reset a device that cannot maintain power.

Contact support

Provide the model, OS, App version, connection, visible message, last successful state, and shortest safe reproduction. Follow Submit feedback and diagnostics and remove private identifiers.