Get an AirPods-style device to appear in the Omarchy Bluetooth panel
Issue #13254 (open, 4.0.4-1, bluez 5.87-2) supports the symptom, the 08-FF-44-4F-EE-C5 placeholder name, the bluetoothctl pairing path and recovery by restarting the shell. The reporter labels the cause 'likely, not confirmed', and the record says so. On this 4.0.4-1 workstation, /usr/share/omarchy/shell/plugins/panels/bluetooth/Model.js defines hasHumanName() at line 36, rejecting isAddressLike labels, and deviceLists() skips devices failing it at line 110, matching the cited lines. omarchy restart shell routes to omarchy-restart-shell, which sets relock=1 and re-locks when the session is locked with no live locker, so the warning in the fix is accurate. The bluetoothctl [NEW] example line would read [CHG] ... Name: for a device BlueZ already cached, but it is an example and does not affect the commands. Not exercised.
Symptom
AirPods (Max, Pro) in pairing mode never show under Available in the bar's Bluetooth panel while it scans. After pairing them with bluetoothctl they connect and play audio, but the panel still does not list them under Connected. bluetoothctl devices showed the device earlier with its address as its name, for example Device 08:FF:44:4F:EE:C5 08-FF-44-4F-EE-C5. They appear only after restarting the shell.
Cause
The panel's deviceLists() in shell/plugins/panels/bluetooth/Model.js skips any device whose name fails hasHumanName(), which rejects address-like names. BlueZ first records nameless BLE devices (Apple devices advertise this way) under an address placeholder. When BlueZ later learns the real Name and Alias, the panel apparently does not re-evaluate the device, so it stays filtered out until the shell restarts. Reported on 4.0.4-1, and the filter is present in this workstation's 4.0.4-1 Model.js lines 36-38 and 110. The reporter marks the exact cause as likely, not confirmed.
Fix
Pair from the terminal, then restart the shell so the panel re-reads the device list:
bluetoothctl
# inside bluetoothctl:
scan on
# wait for the real name to appear, e.g. [NEW] Device 08:FF:44:4F:EE:C5 Rade's AirPods Max
pair 08:FF:44:4F:EE:C5
trust 08:FF:44:4F:EE:C5
connect 08:FF:44:4F:EE:C5
scan off
quit
omarchy restart shell
Run omarchy restart shell from your own desktop session only. If the lock screen has crashed, it re-locks the session.
Verify
bluetoothctl info <MAC> shows Paired: yes, Connected: yes and the real Name:. The device is listed under Connected in the bar's Bluetooth panel.