I’m receiving an invalid card number error on a completely fresh install on my Tinkerboard. This is preventing my Spotify Connect plugin from working correctly. I already checked with the authors of the plugin and they indicated it’s a Volumio issue (as evidenced by the Invalid Card Number error). My setup is very simple, it’s just line-out, no USB anything connected, no special hardware, nothing. I’ve had this issue since April, which is why the log is from April. I’ve tried updating Volumio to any new versions since, including trying fresh installs again but nothing has worked.
I don’t seem to see anything in your logs concerning issues with Spotify Connect. Are you sure everything else works fine (with volspotconnect2 uninstalled)?
I just checked and playback works normally using the Web Radio (I don’t have any music at all installed locally) while the plugin is uninstalled. I reinstalled the plugin today and here is the log output you requested after running the command below. Definitely looks like something is going wrong as the service is restarting itself after entering a failed state.
Ash, I executed startconnect.sh (./startconnect.sh) and it gave me this:
cat startconnect.sh
#this file is generated by the plugin. You should not edit it unless you know what you do. It will be overwritten by the plugin each time a change in config is detected
cd /data/plugins/music_service/volspotconnect2
./vollibrespot -b 320 -c /tmp \
--disable-audio-cache \
--name 'Volumio' --initial-volume 100\
--device plughw:1,2 \
--mixer alsa \
--mixer-name 'Headphone,1' --mixer-card 'hw:1,2' \
I modified it to this for the last 3 lines, but I’m still not having any luck. Does the problem seem to be in aplay?
Seems like there is something amiss with the mixer names that Volumio is reporting. Here it mentions Headphone, but when querying the confuguration it, it seems to return Headpone,1?
So, some more digging.
# Volume change script
cat /tmp/getvolume
# Current alsa config
cat /etc/asound.conf
# Check if we have a valid mixer
amixer -M get -c 1 "Headphone,1"
You might have to play around with these combinations,
This should fix your issue. The card/mixer is not reported differently in this case by Volumio audio_interface api.
I would rather this be solved directly in Volumio, rather than patching the SpotifyConnect interface.