05-11-2025, 05:05 PM
Folks, would appreciate any insights on solving the above error
Variables as follows:
> Moode 9.3.3 2025-04-29, running on RaspPi 4, with ProtoDac HAT
> successful Bluetooth pairings with a (i) Google Nest and (ii) a Anker/Soundcore Bluetooth speaker. No issues with their co-existence, and both work faultlessly as audio outputs all the time
> implies nothing fundamentally wrong at the Moode end
What prompted the error:
> tried this AM to Bluetooth-pair Moode with my Android 12 phone
> phone was discovered by Moode, and pairing apparently completed
> however, when I try to output audio via Bluetooth to the phone, Moode throws the 'Failed to open "ALSA Bluetooth" (alsa); Failed to open ALSA device "_audioout": No such device' error
Actions so far:
> with a separate paired Android 10 phone, I get the same error message in Moode
> have rebooted Pi, but get same error when trying to output audio to either Android phone
> in the Bluetooth config screen have deleted all pairings, and tried both phones again - same error message occurs
Any pointers gratefully received
Best, Simon P
Variables as follows:
> Moode 9.3.3 2025-04-29, running on RaspPi 4, with ProtoDac HAT
> successful Bluetooth pairings with a (i) Google Nest and (ii) a Anker/Soundcore Bluetooth speaker. No issues with their co-existence, and both work faultlessly as audio outputs all the time
> implies nothing fundamentally wrong at the Moode end
What prompted the error:
> tried this AM to Bluetooth-pair Moode with my Android 12 phone
> phone was discovered by Moode, and pairing apparently completed
> however, when I try to output audio via Bluetooth to the phone, Moode throws the 'Failed to open "ALSA Bluetooth" (alsa); Failed to open ALSA device "_audioout": No such device' error
Actions so far:
> with a separate paired Android 10 phone, I get the same error message in Moode
> have rebooted Pi, but get same error when trying to output audio to either Android phone
> in the Bluetooth config screen have deleted all pairings, and tried both phones again - same error message occurs
Any pointers gratefully received
Best, Simon P
