SteamOS Bluetooth failure decision tree
Scope
This flow covers adapter state, discovery, pairing, trust, connection, profile, Steam Input/application routing, radio interference, and resume behavior.
Start safe
Charge the device, disconnect it from other hosts, record its model/firmware and prior bond, and keep a wired/local control method available. Do not remove the bond before capturing state.
Decision tree
- No controller: compare Gaming Mode/Desktop visibility and check radio/adapter state.
- Device not discovered: place it in the exact pairing mode, stop other host connections, then scan once.
- Pairing fails: verify agent prompt, PIN method, existing bond on both ends, and time-stamped logs.
- Paired but not connected: compare trusted/connected state and reconnect after one reboot.
- Connected but unusable: separate Bluetooth transport from Steam Input, controller order, application focus, and game support.
- Drops after resume: record suspend duration, battery, interference, and whether all devices or one model fail.
Evidence to capture
The first four commands are read-only. Entering bluetoothctl interactively is unnecessary for this evidence set:
Stop conditions
Stop if the adapter vanishes, kernel/firmware faults repeat, the device battery is damaged, enterprise policy controls pairing, or removing the bond would strand the only input device. Escalate with exact device addresses redacted.
Restore baseline
Stop scanning, reconnect the original host/device, restore controller order and Steam Input profile, and undo test radio changes. Remove/re-pair only one device after evidence is saved and a second control path exists.
Frequently asked questions
Should I remove and re-pair the device immediately?Should I remove and re-pair the device immediately?
Why can a device show connected but not work in a game?Why can a device show connected but not work in a game?
Sources
Version history
- 2026-07-15: Phase 6 Bluetooth transport, bond, profile, and application-routing tree.