Spotify Connect 2 Not Visible on Network

vladimirb · July 8, 2020, 8:04am

Hi,

I am on the latest version of Volumio 2.779 using the latest plugin of Volumio Spotify Connect 2 1.0.3 (I also use Spotify 2.0.2 and it works fine.)

However, Spotify Connect 2 is not visible to the other devices on my home network. For example, my Android phone Spotify App does not see Volumio Spotify Connect as available device

It all worked fine until I recently upgraded both Volumio and the plugins to the latest.

What information (logs, files etc) do you want me to provide in order to help me resolve the problem.

Thanks in advance.

balbuze · July 8, 2020, 8:19am

Disable the plugin and reboot. Enable it. Let us know

vladimirb · July 8, 2020, 9:46am

Thanks for your prompt response.

Still the same, unfortunately: Volumio Spotify Connect 2 cannot be seen from the other devices on the network, like from my Android phone Spotify App.

balbuze · July 8, 2020, 9:58am

What is your Dac and volume mixer setting?

vladimirb · July 8, 2020, 10:06am

Output device: Allo Boss
I2S: On
DAC Model: Allo Boss

DSD Playback Mode: DSD Direct
DSD Auto Volume Level: Off
Volume Normalization: Off
Audio Buffer Size: 2 MB
Buffer Before Play: 10%
Persistent Queue: On
Playback Mode: Continuous

Mixer Type: Hardware
Mixer Control Name: Digital
Default Startup Volume: Disabled
Max Volume Level: 100
One Click Volume Steps: 10
Volume Curve Mode: Natural
MPD Clients Volume Control: Off

Audio Resampling: Off

balbuze · July 8, 2020, 11:05am

Very weird as I use it on the same hw… Have you saved in the plugin settings?

vladimirb · July 8, 2020, 11:13am

Volumiuo Spotify Connect Configuration:

Normalisation Volume: On
Bitrate: 320
Multi-user device: On
Gapless playback: On
Autoplay: On
Debug mode: Off

vladimirb · July 8, 2020, 11:33am

I’ve got a feeling that this has something to do with my network.

I use wired network connection:
IP Address 192.168.1.10

I also have wireless Hot Spot:
IP Address: 192.168.211.1

Wired Network:
Automatic IP: On

Wireless networking: On
Automatic IP: On

However, under Wireless Network Connection it cannot see my home WiFi. It shows several of my neighbors’ WiFi’s

billjon · July 9, 2020, 12:43am

This worked for me. Also note, after I enabled I rebooted.

ashthespy · July 9, 2020, 3:26pm

@vladimirb Could you share some logs?

Either from the /dev page using the livelog feature or via ssh.

# Volumio logs
journalctl -f -o cat
# vollibrespot logs
journalctl -f -o cat -u volspotconnect2.service

Note you might need sudo before these commands depending on the version of Volumio your running

If you open up logs and attempt a connection, we should be able to get a better idea of what is going on

vladimirb · July 9, 2020, 11:18pm

I accessed the log via /dev page.
First I disabled Spotify Connect 2 plugin, then I rebooted Volumio and after coming back I re-enabled the plugin again.

Here is the log:

Starting Live Log…
info: ------------------------------ 1356ms
info: CoreCommandRouter::volumioGetState
info: CorePlayQueue::getTrack 0
info: CoreCommandRouter::volumioGetQueue
info: CoreStateMachine::getQueue
info: CorePlayQueue::getQueue
info: CoreCommandRouter::executeOnPlugin: system , getHwuuid
info: CALLMETHOD: system_controller system enableLiveLog true
info: CoreCommandRouter::executeOnPlugin: system , enableLiveLog
info: Launching a new LiveLog session
volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig eth0
pam_unix(sudo:session): session opened for user root by (uid=0)
pam_unix(sudo:session): session closed for user root
volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0
pam_unix(sudo:session): session opened for user root by (uid=0)
pam_unix(sudo:session): session closed for user root
volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig eth0
pam_unix(sudo:session): session opened for user root by (uid=0)
pam_unix(sudo:session): session closed for user root
volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0
pam_unix(sudo:session): session opened for user root by (uid=0)
pam_unix(sudo:session): session closed for user root
info: CoreCommandRouter::volumioGetState
info: CorePlayQueue::getTrack 0
info: CoreCommandRouter::executeOnPlugin: multiroom , getMultiroom
info: Listing playlists
info: CoreCommandRouter::executeOnPlugin: appearance , getUiSettings
info: CoreCommandRouter::executeOnPlugin: wizard , getShowWizard
info: CoreCommandRouter::executeOnPlugin: system , getShowWizard
info: CoreCommandRouter::executeOnPlugin: system , getPrivacySettings
info: CoreCommandRouter::executeOnPlugin: my_volumio , getMyVolumioStatus
info: CoreCommandRouter::volumioGetQueue
info: CoreStateMachine::getQueue
info: CorePlayQueue::getQueue
info: CoreCommandRouter::volumioGetVisibleSources
info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources
info: CoreCommandRouter::executeOnPlugin: my_volumio , detectVolumioHardware
info: Could not detect Volumio Device: Error: Command failed: aplay -l | grep es90x8q2m-dac-dai-0
[SpotifyConnect] Stopping Vollibrespot daemon
[SpotifyConnect] Closing metadata listener
info: Disabling plugin volspotconnect2
info: Done.
volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl stop volspotconnect2.service
pam_unix(sudo:session): session opened for user root by (uid=0)
Stopping Volspotconnect2 Daemon…
Stopped Volspotconnect2 Daemon.
pam_unix(sudo:session): session closed for user root
[SpotifyConnect] Vollibrespot Daemon service stoped!
info: ___________ PLUGINS: Run onVolumioReboot Tasks ___________
info: PLUGIN onReboot : networkfs
volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/umount -f /mnt/NAS/NASuGarazi
pam_unix(sudo:session): session opened for user root by (uid=0)
pam_unix(sudo:session): session closed for user root
volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl reboot
pam_unix(sudo:session): session opened for user root by (uid=0)
Started Turns off Raspberry Pi display backlight on shutdown/reboot.
Started Synchronise Hardware Clock to System Clock.
Stopping Bluetooth.
Stopped target Bluetooth.
Stopping system-ifup.slice.
Removed slice system-ifup.slice.
Stopping system-systemd\x2dfsck.slice.
Removed slice system-systemd\x2dfsck.slice.
Stopping Spotify Daemon…
Stopping dhcpd.service…
Stopping Host and Network Name Lookups.
Stopped target Host and Network Name Lookups.
Stopping dnsmasq.service…
Stopping Authenticate and Authorize Users to Run Privileged Tasks…
Stopping Disk Manager (legacy version)…
Stopping Bluetooth service…
Stopping Graphical Interface.
Stopped target Graphical Interface.
Stopping Entropy daemon using the HAVEGE algorithm…
Stopping Multi-User System.
Stopped target Multi-User System.
Stopping mount disks automatically with standby…
Stopping UPnP Renderer front-end to MPD…
Stopping volumio-remote-updater.service…
Stopping Volumio Streaming Daemon…
Stopping Volumio Log Rotation Service…
Stopping OpenBSD Secure Shell server…
Stopping Login Prompts.
Stopped target Login Prompts.
Stopping Getty on tty1…
Stopping Login Service…
Stopping LSB: start Winbind daemon…
Stopping LSB: start Samba SMB/CIFS daemon (smbd)…
exiting on receipt of SIGTERM
Terminating
Received signal 15; terminating.
Stopping SDP server
Exit
Stopping LSB: start Samba daemons for the AD DC…
Stopping LSB: Start NTP daemon…
Stopping LSB: Brings up/down network automatically…
haveged: Stopping due to signal 15
haveged starting up
Stopping LSB: Advanced IEEE 802.11 management daemon…
Stopping LSB: set CPUFreq kernel parameters…
[2020/07/09 23:08:11.261966, 0] …/lib/util/pidfile.c:153(pidfile_unlink)
Failed to delete pidfile /var/run/samba/smbd.pid. Error was No such file or directory
Stopping Shairport Sync - AirPlay Audio Receiver…
Stopping Music Player Daemon…
Stopping D-Bus System Message Bus…
Starting Store Sound Card State…
Disconnected from D-Bus, exiting.
Got SIGTERM, quitting.
Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.211.1.
Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.10.
ntpd exiting on signal 15
avahi-daemon 0.6.31 exiting.
Stopping NTP server: ntpd.
Exiting.
Discovery: ERRORError: dns service error: unknown
info: mDNS Advertisement raised the following error Error: dns service error: unknown
info: mDNS Browse raised the following error Error: dns service error: unknown
haveged.service: main process exited, code=exited, status=143/n/a
Stopped Entropy daemon using the HAVEGE algorithm.
Unit haveged.service entered failed state.
Stopped mount disks automatically with standby.
Stopped volumio-remote-updater.service.
Stopped Volumio Log Rotation Service.
Stopped Login Service.
Stopped Avahi mDNS/DNS-SD Stack.
Stopped D-Bus System Message Bus.
Stopped OpenBSD Secure Shell server.
Stopped Disk Manager (legacy version).
Stopped Getty on tty1.
Stopped Authenticate and Authorize Users to Run Privileged Tasks.
Stopped Bluetooth service.
Stopped dnsmasq.service.
Stopped dhcpd.service.
Stopped Spotify Daemon.
Stopped UPnP Renderer front-end to MPD.
Stopped Shairport Sync - AirPlay Audio Receiver.
Stopped Volumio Streaming Daemon.
Stopped LSB: Start NTP daemon.
Stopped LSB: Advanced IEEE 802.11 management daemon.
Stopped LSB: set CPUFreq kernel parameters.
Stopped Music Player Daemon.
Started Store Sound Card State.
Network Interface Plugging Daemon…stop eth0…done.
Stopped LSB: Brings up/down network automatically.

ashthespy · July 12, 2020, 2:03pm

That doesn’t really help as all it captures is the shut down process…
Just open the live log and enable the plugin (if it’s not already enabled) and try connecting to it.

To rule out network issues, try logging in directly with your credentials (by disabling the multi user toggle)

vladimirb · July 12, 2020, 9:35am

Thanks very much for your prompt reply.
I disabled the plugin first and started capturing the log, enabled it with turning off Multi-user Device option and logged in using my credentials.
We are getting there
The good news is that Volumio Spotify Connect 2 has become visible and it works now!
Does Multi-user device has to be turned off? It would be great if I could play Volumio from more than one device but I can live with that.
The other thing that I just spotted is that the Volumio http://volumio.local/playback does not display the song currently being played but the last radio station I played before I started using Spotify.

Here is the log:

Starting Live Log…
info: Fetching Streaming Services browse cache
info: CoreCommandRouter::volumioRemoveToBrowseSourcesQOBUZ
info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources
info: CoreCommandRouter::volumioRemoveToBrowseSourcesTIDAL
info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources
info: CoreCommandRouter::executeOnPlugin: system , getSystemVersion
info: CoreCommandRouter::executeOnPlugin: system , getConfigParam
info: CALLMETHOD: system_controller system enableLiveLog true
info: CoreCommandRouter::executeOnPlugin: system , enableLiveLog
info: Launching a new LiveLog session
info: Enabling plugin volspotconnect2
info: Loading plugin “volspotconnect2”…
info: PLUGIN START: volspotconnect2
[SpotifyConnect] Creating VLS config file
info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam
info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam
[SpotifyConnect] Starting metadata listener
volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl start volspotconnect2.service
pam_unix(sudo:session): session opened for user root by (uid=0)
Starting Volspotconnect2 Daemon…
Started Volspotconnect2 Daemon.
pam_unix(sudo:session): session closed for user root
[SpotifyConnect] Vollibrespot Daemon service started!
e[34m [Metrics] e[39m SpotifyConnect: e[31m 0s 214.33ms e[39m
info: Done.
vollibrespot v0.2.1 1438440 2020-05-15 (librespot 659de68 2020-05-10) – Built On 2020-05-15
Reading Config from “volspotify.toml”
[Vollibrespot] : Using Alsa backend with device: plughw:1
[Vollibrespot] : Connecting to AP “gae2-accesspoint-b-2npm.ap.spotify.com:443”
info: CoreCommandRouter::getUIConfigOnPlugin
[SpotifyConnect] config : toggling initvol/volume_ctrl
[Vollibrespot] : Authenticated as “xxxxxxx” !
[Vollibrespot] : Setting up new mixer: card:hw:1 mixer:Digital index:0
[Vollibrespot] : Alsa Mixer info min: 0 (MilliBel(-9999999)[dB]) – max: 207 (MilliBel(0)[dB]) HW: true
[Vollibrespot] : Using alsa sink
[Vollibrespot] : Metadata pipe established
[Vollibrespot] : Country: “NZ”
[Vollibrespot] : Event: Volume { volume_to_mixer: 0 }
[SpotifyConnect] 0
[SpotifyConnect] Volume: Spotify:0 Volumio: 0
info: CoreStateMachine::pushState
info: CorePlayQueue::getTrack 0
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CALLMETHOD: music_service volspotconnect2 saveVolspotconnectAccount [object Object]
info: CoreCommandRouter::executeOnPlugin: volspotconnect2 , saveVolspotconnectAccount
[SpotifyConnect] Creating VLS config file
info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam
info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam
[SpotifyConnect] Restarting Vollibrespot Daemon
volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart volspotconnect2.service
pam_unix(sudo:session): session opened for user root by (uid=0)
Stopping Volspotconnect2 Daemon…
Starting Volspotconnect2 Daemon…
Started Volspotconnect2 Daemon.
pam_unix(sudo:session): session closed for user root
vollibrespot v0.2.1 1438440 2020-05-15 (librespot 659de68 2020-05-10) – Built On 2020-05-15
Reading Config from “volspotify.toml”
[Vollibrespot] : Using Alsa backend with device: plughw:1
[SpotifyConnect] Vollibrespot Daemon service restarted!
[Vollibrespot] : Connecting to AP “gae2-accesspoint-b-cmmh.ap.spotify.com:443”
[Vollibrespot] : Authenticated as “xxxxxxx” !
[Vollibrespot] : Setting up new mixer: card:hw:1 mixer:Digital index:0
[Vollibrespot] : Alsa Mixer info min: 0 (MilliBel(-9999999)[dB]) – max: 207 (MilliBel(0)[dB]) HW: true
[Vollibrespot] : Using alsa sink
[Vollibrespot] : Country: “NZ”
[Vollibrespot] : Metadata pipe established
[Vollibrespot] : Event: Volume { volume_to_mixer: 0 }
[SpotifyConnect] 0
[SpotifyConnect] Volume: Spotify:0 Volumio: 0
info: CoreStateMachine::pushState
info: CorePlayQueue::getTrack 0
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo

vladimirb · July 12, 2020, 9:43am

Small correction:
When I started playing a song from my Android Spotify app http://volumio.local/playback did display the song being played.
When I previously started playing a song from my desktop Spotify application it did not display the song.
Not a big deal. This might be a bug in Spotify desktop application…

ashthespy · July 12, 2020, 2:02pm

On the windows client, I sometimes face issues with the mdns connection timing out, so that might be something to consider.

If your on the same network as your volumio device, the Android client should be able to see the it as a Spotify device - if the mdns packets are making it through your network support. You can test this be enabling the “debug” mode of the plugin, and looking at the logs again.

vladimirb · July 15, 2020, 2:18am

I played around a little bit with this.

The problem I mentioned above that Volumio does not display the song being played through Spotify Connect 2 occured when I accesses Volumio from my Android Spotify App and my Linux desktop Spotify client at the same time. However, I tried several times playing a song, stopping it, playing another from both sides (Android and Linux) and it worked fine!

The only thing that did not work was that Volumio was not visible on the network when I turn on Multi-user Device option. However, I can live with that as we have only one Spotify account in our house.

Thanks very much for your help and support!