bluealsa PCM errors with 0.31.1

[fragande]

Sorry in advance for my lack of knowledge, but I'm running into issues with a fresh install of Raspotify on my RPi Zero W running Raspberry Pi OS Lite "Bullseye". I borked my old working Buster setup by trying to build bluealsa from source with AAC support. My playback device is a BT speaker.

The errors I'm getting are:

Nov 23 17:15:29 raspberrypi librespot[443]: ALSA lib bluealsa-pcm.c:763:(_snd_pcm_bluealsa_open) Couldn't get BlueALSA PCM: PCM not found
Nov 23 17:15:29 raspberrypi librespot[443]: [2021-11-23T17:15:29Z ERROR librespot_playback::player] Audio Sink Error Connection Refused: <AlsaSink> Device default May be Invalid, Busy, or Already in Use, ALSA function 'snd_pcm_open' failed with error 'ENODEV: No such device'

Running librespot manually does work fine however, so I'm not sure what is causing this. It seems it may be related to other recent issues? Got it working by downgrading to 0.16.0.

[JasonLG1979]

This may be similar to #457

If you could edit the systemd unit file with:

sudo systemctl edit --full raspotify

Find the line that starts with RestrictAddressFamilies= and make it look like this:

RestrictAddressFamilies=AF_UNIX AF_INET AF_INET6 AF_NETLINK

And see if that fixes your issue?

If so great. That change has already been commited to master I just haven't done a new release yet.

If not we'll do some more digging.

[fragande]

Forgot to mention I already tried that by editing /usr/lib/systemd/system/raspotify.service directly, but maybe there's a difference? Anyway, the method above didn't make a difference either. Still the same error after editing, saving and rebooting.

[JasonLG1979]

No it shouldn't matter I don't think how you edit it?

After you edit it you have to call sudo systemctl daemon-reload and sudo systemctl restart raspotify for it to take effect.

Edit:

Rebooting should be about the same as reload and restart. But you could try it any way?

[JasonLG1979]

So if I understand correctly you're transmitting over bluetooth from alsa correct?

[JasonLG1979]

It looks like you may not have the bluealsa alsa sink configure correctly?

[JasonLG1979]

You might look here:

https://github.com/dtcooper/raspotify/wiki/Play-via-Bluetooth-Speaker-on-Raspberry-Pi-Desktop#play-via-bluetooth-speaker-without-raspberry-pi-desktop

I can't vouch for the howto as I've never done it as I have no need. If I wanted to stream Spotify to a bluetooth speaker I'd just stream it from the controlling device and skip using a Raspberry Pi as a middle man.

[JasonLG1979]

@bablokb might be able to help better than I?

[fragande]

Sorry, I'm a knucklehead when it comes to stuff like this, but yes, I'm using bluealsa to stream over BT which I believe creates an ALSA PCM device? I'm not sure how it works or what the correct terminology is here ...

I believe it's configured correctly using asound.conf as it works when calling librespot manually. Also works fine when using 0.16.0 as mentioned before. It's only when using 0.31.0 I get these errors. When installing the 0.16.0 .deb over 0.31.0 everything started working without changing anything else.

I use several devices to control Spotify streaming to this BT Speaker (phone, PC and tablet) so that's why I'm using Raspotify for this. I realize a WiFi speaker is miles better, but this solution has worked OK so far.

[JasonLG1979]

Sorry, I'm a knucklehead when it comes to stuff like this,

It's all good. I'm probably the one who broke it,lol!!!

Try adding:
AF_BLUETOOTH

To the RestrictAddressFamilies= so it looks like:

RestrictAddressFamilies=AF_UNIX AF_INET AF_INET6 AF_NETLINK AF_BLUETOOTH

[fragande]

That seems to have done the trick! 0.31.0 up and running without any errors in systemd logs. Thank you very much.

[JasonLG1979]

Good deal. I'll add that to master. It will be in the next release.

[JasonLG1979]

We'll keep this open until the release that includes it is released.

[JasonLG1979]

763a7c8