DeviceOK
SearchDevice checks
Home / Fixes / Bluetooth Device Not Showing or Pairing

hardware · evidence-led troubleshooting

Bluetooth Device Not Showing or Pairing

Use a focused DeviceOK test first, then follow the evidence from browser/device state before changing drivers, firmware, or hardware.

Reviewed 2026-08-113 diagnostic steps2 official sources
Run Bluetooth LESee fault tree ↓

What this symptom means

Nothing useful can be tested until the device or browser path is visible. Start with connection, power, permission and OS recognition before app settings.

Diagnostic principleUSB-C connector shape does not tell you data speed, video capability or charging power. Separate device enumeration, transport/data rate, alternate-mode video and power delivery before buying replacement hardware.

Fault tree

USB / peripheral connection fault tree

Use the observation that best matches what you can reproduce. Do not treat every cause as equally likely.

1
Cable capability mismatch

Evidence: Charging works but video/data does not, or low-speed data works but high-bandwidth mode fails.

Next: Identify the cable's certified power/data capability and test a known-good full-featured cable.

2
Hub/dock topology

Evidence: Direct connection works but the same device fails through a hub/dock.

Next: Add the dock back only after a direct baseline succeeds; check power and bandwidth sharing.

3
Permission/API support

Evidence: OS sees the device but WebUSB/WebHID/Serial cannot open it.

Next: Confirm the device is actually supported by that browser API and not claimed by a protected OS driver.

4
Power budget

Evidence: Device resets, disconnects under load or works with externally powered hub.

Next: Check host/hub power and device requirements.

Interpret the result

Evidence matrix

A test result is useful only if it changes the next troubleshooting branch.

ObservationWhat it supportsPrioritize next
Direct port worksThe device and host can establish a working path without the intermediate accessory.Hub, dock, cable topology or power sharing.
Charging onlyPower is present but this does not prove data or DisplayPort support.Cable data lanes, host port capability, device mode or adapter.
Browser API cannot see deviceEither the API is unsupported, the device class is excluded/protected, or the OS has not exposed it.Browser capability and OS-level detection before hardware diagnosis.
Disconnects under loadThe connection exists but stability/power/bandwidth is insufficient.Cable length/quality, hub power, port power, firmware or device fault.

Fast baseline

Rule out the simple causes first

  1. 1

    Make sure the device is powered and in pairing/advertising mode.

  2. 2

    For normal headphones, keyboards, mice, and controllers, use OS Bluetooth settings rather than Web Bluetooth.

  3. 3

    Use DeviceOK Web Bluetooth only for compatible BLE/GATT devices.

Full sequence

Work from reversible checks to invasive ones

Do not install unofficial driver packs or firmware from download sites just because the device is missing.

  1. 1

    If the device is absent from the operating system too, focus on power, pairing mode, distance, adapter state, and Bluetooth drivers.

  2. 2

    If it pairs in the OS but is absent from Web Bluetooth, that can be normal for unsupported profiles/services.

  3. 3

    Remove/re-pair only after simpler checks.

Platform branches

Where the setting lives

USB-C

  • Treat power, data and video as separate capabilities
  • Check 60W/240W and data-rate markings on certified USB-C cables where present
  • Use direct host connection for the baseline

Browser APIs

  • Chromium-based support is broader for WebHID/WebUSB/Web Serial
  • Permission requires a user gesture and device selection
  • Some device classes are intentionally unavailable to websites

Docks

  • Check upstream port capability
  • Check dock power-delivery rating
  • Check display topology and shared bandwidth
If it works in DeviceOK

If the matching DeviceOK test succeeds, prioritize the affected app, browser policy, operating-system setting, or configuration before assuming complete hardware failure.

If it also fails here

A missing browser device must be compared with OS detection and API support before calling hardware failed. Compare the simplest direct connection and official diagnostic path before replacement.

Escalation threshold

When software troubleshooting has stopped being high value

  • Device not recognized on multiple hosts
  • Connector is physically loose/damaged
  • Cable/adapter gets abnormally hot
  • Electrical smell, arcing or visible damage
Safety
  • Stop using any cable, charger or port that becomes abnormally hot, sparks, smells burnt or shows melted insulation.
Changed one variable?The first milestone is simple detection. Only after the device appears should you troubleshoot signal quality or app behavior. Retest under the same condition so the result is comparable.
Retest Bluetooth LE