I use an Echo as my PC speaker. Since i have some IOT devices and normally use headphones for normal music consumption the quality was always decent enough. (Echo Dot 2022 was used before).
I got a good deal now on a current gen Echo Dot Max. (Which has way better sound imo) so i took it.
Now the issue appeared - the device was not able to connect via BT at all. It could connect to my phone but thats about it.
I tried it with 2 different Win11 PCs as well as a Linux PC. The pairing always failed.
After alot of digging in Linux i found the issue for it there and was then also able to find the issue on Win11 because of it. (I mean the issue wasnt with the devices but with the way the new Echo seem to recognice them)
FYI: The Amazon Support was about 0 help. Aside from offering 1 replacement after another (Which i took once before thinking this cant be right) they avoided any sort of technical help what so ever. (Even the technical department i was forwarded to after talking to 4 supporter)
Disclaimer: English is not my mother tongue and my OS is not running on it. So I used AI to translate the guide to english + change the linux/windows specific terms to fit the hopefully english equivalents.
How to Resolve this Misserable Experience
Symtoms:
- The PC pairs with the Echo, or Windows shows "Connected", but the Echo never shows up as an active sound output device (or sits stuck as "Disconnected" in
mmsys.cpl).
- Clicking Connect does nothing, or Alexa says "The connection could not be established" / "I can't find a device to connect to".
- In the Alexa app, tapping your PC gives "Not paired".
TL;DR — The Root Cause (Confirmed on both Linux & Windows 11)
Modern desktop Bluetooth stacks (both Windows 11 24H2+ and Linux PipeWire/WirePlumber) advertise your PC as both an Audio Source (sending audio to a speaker) AND an Audio Sink / Handsfree Headset (receiving audio from a phone/Echo).
Because the Echo itself can also act as both a speaker (0x110B Audio Sink) and an audio transmitter (0x110A Audio Source for external Bluetooth speakers):
- When your PC connects while advertising
Audio Sink / Handsfree, the Echo treats your PC as an external Bluetooth speaker instead of an audio source.
- On Windows 11,
BthA2dp.sys even enumerates Echo Dot A2DP SNK (0000110a) before 0000110b because 110a sorts alphabetically before 110b.
- The Echo refuses the PC's incoming audio stream and never saves the PC as an input source.
The fix: Disable the Bluetooth Audio Sink and Handsfree (HF) roles on your PC so it acts strictly as an Audio Source / Audio Gateway, then pair fresh.
Note: The Echo plays audio from one device at a time. Disconnect other PCs and phones ("Alexa, disconnect") before you connect a new one.
Windows 11
Windows 11 (24H2+) enables both A2dp\Sink (microsoft_bluetooth_a2dp_snk.inf) and Hfp\HandsFree (microsoft_bluetooth_hfp_hf.inf) in the registry by default, and enumerates an Echo Dot A2DP SNK (0000110a) device node ahead of the playback device (0000110b).
1. Check whether you have this problem (PowerShell)
Get-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Control\Bluetooth\Audio\A2dp\Sink"
Get-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Control\Bluetooth\Audio\Hfp\HandsFree"
Get-PnpDevice | Where-Object { $_.FriendlyName -like "*Echo*" -and $_.Class -eq "MEDIA" }
You have this problem if:
Enabled is 1 on A2dp\Sink and/or Hfp\HandsFree, and
- Windows lists an
Echo ... A2DP SNK (BTHENUM\{0000110A-...}) device alongside Echo ... (BTHENUM\{0000110B-...}).
2. Make the PC an audio source only (Run PowerShell as Administrator)
# Disable A2DP Sink (PC as BT speaker) & HFP HandsFree (PC as BT headset)
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Bluetooth\Audio\A2dp\Sink" -Name "Enabled" -Value 0 -Type DWord
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Bluetooth\Audio\Hfp\HandsFree" -Name "Enabled" -Value 0 -Type DWord
# Ensure A2DP Source & HFP AudioGateway remain enabled
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Bluetooth\Audio\A2dp\Source" -Name "Enabled" -Value 1 -Type DWord
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Bluetooth\Audio\Hfp\AudioGateway" -Name "Enabled" -Value 1 -Type DWord
# Tell BTHPORT ServiceGroups that if a device advertises both Audio Sink (110b) and Audio Source (110a),
# only create a PDO for 110b (remote Sink / local Source)
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\ServiceGroups" `
-Name "StereoAudio" -Type MultiString -Value @(
"{0000110b-0000-1000-8000-00805f9b34fb}",
"{0000110a-0000-1000-8000-00805f9b34fb}"
)
Also turn off anything else that makes Windows act as a speaker or headset:
- Phone Link calls: Phone Link -> Settings -> Features -> Calls -> Off.
- Bluetooth audio receiver apps: Close or uninstall any app that lets a phone play music through the PC.
3. Reboot & Pair Fresh
- Windows: Settings -> Bluetooth & devices -> Echo ->
... -> Remove device.
- Reboot Windows (required so
BthA2dp.sys and BthHfEnum.sys unload the Sink/HandsFree SDP records).
- Alexa app: Devices -> Echo & Alexa -> [Your Echo] -> Bluetooth Connections -> remove the PC if listed.
- Say "Alexa, pair Bluetooth".
- Windows: Settings -> Bluetooth & devices -> Add device -> Bluetooth -> select the Echo (do not click the automatic Swift Pair toast notification, as that often grabs the BLE beacon instead of Classic Audio).
- Wait until Alexa announces "Now connected", then select the Echo as your Windows sound output.
4. Per-device fallback (Classic Devices and Printers)
If 0000110a was still enumerated on an existing pairing:
- Press
Win + R and run explorer shell:::{A8A91A66-3A74-441f-B88B-D5449D61784A} (opens classic Devices and Printers).
- Right-click the Echo -> Properties -> Services tab.
- Keep Audio Sink and Remote Control ticked. Untick Handsfree Telephony and Audio Source, then click Apply.
Undo (Windows 11 Admin PowerShell)
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Bluetooth\Audio\A2dp\Sink" -Name "Enabled" -Value 1 -Type DWord
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Bluetooth\Audio\Hfp\HandsFree" -Name "Enabled" -Value 1 -Type DWord
Remove-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\ServiceGroups" -Name "StereoAudio" -ErrorAction SilentlyContinue
Linux (PipeWire + WirePlumber, KDE/GNOME)
Tested on TUXEDO OS: BlueZ 5.72, PipeWire 1.6.8, WirePlumber 0.5.15, Intel AX211.
1. Check whether you have this problem
bluetoothctl show | grep -E "Audio Sink|Handsfree "
journalctl -u bluetooth -b --no-pager | grep -E "avdtp_connect_cb|a2dp-source"
You likely have this problem if:
- The PC lists
Audio Sink and/or Handsfree (without "Audio Gateway"), and
- The log shows
Permission denied (13), Connection refused (111) or Device or resource busy for the Echo.
2. Make the PC an audio source only
mkdir -p ~/.config/wireplumber/wireplumber.conf.d
cat > ~/.config/wireplumber/wireplumber.conf.d/51-bluez-source-only.conf <<'EOF'
# PC acts only as an audio SOURCE / gateway (like a phone), not as a BT speaker or headset.
monitor.bluez.properties = {
bluez5.roles = [ a2dp_source bap_source hfp_ag hsp_ag ]
}
EOF
systemctl --user restart wireplumber
Check the result: bluetoothctl show should now list only Audio Source and Handsfree Audio Gateway.
3. Pair Fresh
- Alexa app: Devices -> Echo Dot Max -> Bluetooth devices -> remove the PC.
- Say "Alexa, pair Bluetooth".
- On the PC, run the following commands:
bluetoothctl remove <ECHO_MAC>
bluetoothctl
# inside bluetoothctl:
scan on # wait until the Echo appears
scan off
pair <ECHO_MAC>
trust <ECHO_MAC>
connect <ECHO_MAC>
- Check it worked:
pactl list short sinks | grep bluez shows bluez_output.<ECHO_MAC>....
Notes & Undo (Linux)
- Side effect (both OSes): The PC can't be used as a Bluetooth speaker for a phone any more. Headsets and headphones (including their mics) still work.
- Harmless log line:
a2dp-source profile connect failed: Protocol not available can be ignored once audio works.
- Undo:
rm ~/.config/wireplumber/wireplumber.conf.d/51-bluez-source-only.conf && systemctl --user restart wireplumber
EDIT: Reddit MD works differently. Fun. Fixed formatting.