New Volumio Spotify Plugin Open Beta-Testing

yes good luck for alpha testing. I personally go back to lms plugin Spotify Integration, I prefer playing music :roll_eyes:

Hi,
When will Spotify plugin finally work? Is anyone working on the issues? Volumio without Spotify is like car without fuel for me. Donā€™t take it badly, but if it takes a long time, Iā€™ll have to go somewhere else, because my family canā€™t exist without music :slight_smile:

3 Likes

Spotify plugin is working great, both control from Volumio and from phone/tablet are working in the same plugin. Version 3.0.6 is the released version. My previous post is a bug report. That does not impact most users as it is a special use case.

1 Like

Lucky you

Maybe we missed it, but where did you post specific details of your system, the problems you have encountered, the circumstances which lead to the problem and the link to your logs?

Otherwise keep on moaning to no effect. Spotify is working fine for most.

For my part on a Raspberry 3 when I do the next track several times in a row I have everything that crashes and stops working. Is this a known problem?

The problems I have have been reported by people here. I calmly waited and tested newer versions of the plugin.
I play music from the Spotify app on my mobile. Connection to RPI succeeds only on the fifth time, very often it is not even possible to connect. When the music from spotify is playing on the RPI, it plays 2-5 songs and then the RPI disconnects itself. Subsequently, RPI and Volumio are dead, unresponsive.
Iā€™ll try a clean install and see if anything changes.

Additional information:

  1. ā€œPositionā€ is also missing from the http://volumio/dev page or any getState (REST, Socket or Command line APIs). This occurs immediately after clear and play from the UI, it shows position:0 then disappears
  2. The queue does not show what item in the queue is playing (probably due to the above position issue)
  3. Previous does not work correctly; starts the same track over, next appear to be working OK
  4. /api/v1/commands/?cmd=play&N=0 and sio.emit(ā€œplayā€,{ā€œvalueā€:0}) both work that confirms the position is referenced somewhere.

Are you sure, the nature and the frequency of the problems others and I are encountering make me doubfullā€¦

Problem are present both on 3.232 or last beta
Problem to play album, i canā€™t play a full album, I have to launch a particular song then skipping doesnā€™t work with strange behaviour
problem using spotify connect, song start then after a few second is passing to next song bu behaviour is not consistent

Here is, for example, a piece of log trying to launch an album via the main playing button


info: CoreCommandRouter::volumioGetState
info: CoreCommandRouter::volumioGetQueue
info: CoreStateMachine::getQueue
info: CorePlayQueue::getQueue
info: CoreCommandRouter::executeOnPlugin: system , getHwuuid
Starting Live Log...
process exited with code nullinfo: CoreCommandRouter::volumioGetState
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
info: Killing previous LiveLog session
info: Live Log process terminated: null
info: CoreCommandRouter::executeOnPlugin: spop , handleBrowseUri
info: In handleBrowseUri, curUri=spotify/myalbums
info: CoreCommandRouter::volumioAddQueueItems
info: CoreStateMachine::addQueueItems
info: CorePlayQueue::addQueueItems
info: Adding Item to queue: spotify:album:3oBVhtKCiey1ieB1QHN6MZ
info: Exploding uri spotify:album:3oBVhtKCiey1ieB1QHN6MZ in service spop
info: CorePlayQueue::saveQueue
info: CoreCommandRouter::volumioPushQueue
info: CoreStateMachine::updateTrackBlock
info: CorePlayQueue::getTrackBlock
info: CoreCommandRouter::volumioPlay
info: CoreStateMachine::play index 18
info: CoreStateMachine::setConsumeUpdateService undefined
info: CoreStateMachine::stop
info: CoreStateMachine::setConsumeUpdateService undefined
info: CoreStateMachine::stPlaybackTimer
info: CoreStateMachine::updateTrackBlock
info: CorePlayQueue::getTrackBlock
info: CoreStateMachine::pushState
info: CorePlayQueue::getTrack 17
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: MRS: Pushing multiroomSync output update for this device
info: MRS: Pushing multiroomSync output
info: CoreStateMachine::serviceStop
info: CorePlayQueue::getTrack 17
info: CoreCommandRouter::serviceStop
info: [1663697055663] ControllerWebradio::stop

info:
---------------------------- MPD announces state update: player
info: sendMpdCommand stop took 70 milliseconds
info: ControllerMpd::getState

info: CoreStateMachine::play index undefined
info: CoreStateMachine::setConsumeUpdateService undefined
info: CorePlayQueue::getTrack 18
info: CoreStateMachine::startPlaybackTimer
info: CorePlayQueue::getTrack 18
info: [1663697055734] ControllerSpotify::clearAddPlayTrack
info: Setting this device active
info: sendMpdCommand status took 4 milliseconds


info: sendMpdCommand playlistinfo took 0 milliseconds

info: ControllerMpd::pushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CorePlayQueue::getTrack 18
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: MRS: Pushing multiroomSync output update for this device
info: MRS: Pushing multiroomSync output
info: CorePlayQueue::getTrack 18
info: Received update from a service different from the one supposed to be playing music. Skipping notification.Current spop Received mpd
info: ------------------------------ 14ms
[Vollibrespot] : Fetching autoplay context uri
[Vollibrespot] : Event: SessionActive { became_active_at: 1663697056123 }
[Vollibrespot] : SessionActive!
[Vollibrespot] : Event: PlaybackStarted { track_id: SpotifyId { id: 334595643878137285476942457234044355589, audio_type: Track } }
[Vollibrespot] : Event: PlaybackLoading { track_id: SpotifyId { id: 334595643878137285476942457234044355589, audio_type: Track } }
[SpotifyConnect]  A connect session has begun
[SpotifyConnect]  Device palyback is active!
[Vollibrespot] : error 400 for uri hm://autoplay-enabled/query?uri=
[Vollibrespot] : AutoplayError: MercuryError
[Vollibrespot] : Event: GotToken { token: Token { access_token: "BQCzE5gVEv8SxiDNf-N4hTVUuZBcC8pAsBDlCg2-IVsbTK4F8ViZYn_wTK8TNK_M7E6gmd9RsNFE-ZhXoXm17fnGsID8gR1gyfe3oQbVSEBh03oYKHTr9VOU3xTvZi0ZbhnmT2y2w-av5eyuPbT6yMcvyjXcfkbRxpudNta9ssLm4qPS2A-Avgs6dDQJAr8e2h7k", expires_in: 3600, token_type: "Bearer", scope: ["streaming", "user-read-playback-state", "user-modify-playback-state", "user-read-currently-playing", "user-read-private"] } }
error: Received malformed Token, ignoring
[Vollibrespot] : Loading  with Spotify URI 
[Vollibrespot] :  (173658 ms) loaded
[Vollibrespot] : Event: PlaybackStopped { track_id: SpotifyId { id: 334595643878137285476942457234044355589, audio_type: Track } }
[SpotifyConnect]  Device palyback is inactive
info: MRS: STARTING volumioStreaming
 volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/rm -f /tmp/hls/*
 volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart volumioStreaming
pam_unix(sudo:session): session opened for user root by (uid=0)
pam_unix(sudo:session): session closed for user root
pam_unix(sudo:session): session opened for user root by (uid=0)
info: An error occurred while starting playback Not Found
Stopping VolumioStreamingService...
------------------------------------ BT MESSAGE: BT STATUS: running
volumioStreaming.service: Main process exited, code=killed, status=15/TERM
volumioStreaming.service: Succeeded.
Stopped VolumioStreamingService.
------------------------------------ BT MESSAGE: BT STATUS: waiting
Started VolumioStreamingService.
pam_unix(sudo:session): session closed for user root
info: MRS: volumioStreaming STARTED
 volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/rm -f /tmp/hls/*
pam_unix(sudo:session): session opened for user root by (uid=0)
pam_unix(sudo:session): session closed for user root

Here trying to change ā€œmulti user optionā€ in the option of the plugin : it doesntā€™ work

info: Checking Spotify Web API
[Vollibrespot] : ReqToken
info: New Spotify Access Token Received
info: Initializing Spotify Web API
info: Initliazing Spotify Browsing Facility
info: CoreCommandRouter::volumioAddToBrowseSources[object Object]
info: [1663697454359] CoreMusicLibrary::Adding element Spotify
info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources
Cannot find translation for sourceMedia Servers
Cannot find translation for sourceSpotify
info: Idenfitied this device as Connect device: c6e56cf6b68c07041768b06e2f29a439e7724b0e
kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
info: CoreCommandRouter::getUIConfigOnPlugin
info: CALLMETHOD: music_service spop saveVolspotconnectSettings [object Object]
info: CoreCommandRouter::executeOnPlugin: spop , saveVolspotconnectSettings
{"shareddevice":false,"initvol":["33"],"normalvolume":false,"bitrate":{"value":320,"label":"320"},"volume_ctrl":{"value":"fixed","label":"fixed"},"gapless":true,"autoplay":true,"debug":false,"icon":{"value":"avr","label":"AV Receiver"}}
[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 volspotconnect.service
pam_unix(sudo:session): session opened for user root by (uid=0)
Stopping Volspotconnect2 Daemon...
volspotconnect.service: Main process exited, code=killed, status=15/TERM
volspotconnect.service: Succeeded.
------------------------------------ BT MESSAGE: BT STATUS: running
Stopped Volspotconnect2 Daemon.
------------------------------------ BT MESSAGE: BT STATUS: waiting
Started Volspotconnect2 Daemon.
pam_unix(sudo:session): session closed for user root
vollibrespot v0.2.5 8922128 2022-05-31 (librespot 08d8bcc 2020-10-07) -- Built On 2022-05-31
Reading Config from "/tmp/volspotify.toml"
[Vollibrespot] : Using Alsa backend with device: volumio
[SpotifyConnect] Vollibrespot Daemon service restarted!
[Vollibrespot] : Connecting to AP "ap-gew1.spotify.com:443"
[Vollibrespot] : Authenticated as "chourmovs" !
[Vollibrespot] : Using alsa sink
[Vollibrespot] : Country: "FR"
[Vollibrespot] : Metadata pipe established
[Vollibrespot] : Event: Volume { volume_to_mixer: 34734 }
[SpotifyConnect] Volume Spotify: 53.000686655985355 Volumio: 53
info: Checking Spotify Web API
[2022/09/20 18:12:02.825553,  0] ../source3/libsmb/nmblib.c:917(send_udp)
  Packet send failed to 127.0.0.1(137) ERRNO=Invalid argument
[2022/09/20 18:12:02.825714,  0] ../source3/nmbd/nmbd_packets.c:180(send_netbios_packet)
  send_netbios_packet: send_packet() to IP 127.0.0.1 port 137 failed
[2022/09/20 18:12:02.825780,  0] ../source3/libsmb/nmblib.c:917(send_udp)
  Packet send failed to 127.0.0.1(137) ERRNO=Invalid argument
[2022/09/20 18:12:02.825837,  0] ../source3/nmbd/nmbd_packets.c:180(send_netbios_packet)
  send_netbios_packet: send_packet() to IP 127.0.0.1 port 137 failed
[2022/09/20 18:12:02.825894,  0] ../source3/libsmb/nmblib.c:917(send_udp)
  Packet send failed to 127.0.0.1(137) ERRNO=Invalid argument
[2022/09/20 18:12:02.825949,  0] ../source3/nmbd/nmbd_packets.c:180(send_netbios_packet)
  send_netbios_packet: send_packet() to IP 127.0.0.1 port 137 failed
[2022/09/20 18:12:02.826006,  0] ../source3/libsmb/nmblib.c:917(send_udp)
  Packet send failed to 127.0.0.1(137) ERRNO=Invalid argument
[2022/09/20 18:12:02.826060,  0] ../source3/nmbd/nmbd_packets.c:180(send_netbios_packet)
  send_netbios_packet: send_packet() to IP 127.0.0.1 port 137 failed
[2022/09/20 18:12:02.826117,  0] ../source3/libsmb/nmblib.c:917(send_udp)
  Packet send failed to 127.0.0.1(137) ERRNO=Invalid argument
[2022/09/20 18:12:02.826172,  0] ../source3/nmbd/nmbd_packets.c:180(send_netbios_packet)
  send_netbios_packet: send_packet() to IP 127.0.0.1 port 137 failed
[2022/09/20 18:12:07.836591,  0] ../source3/libsmb/nmblib.c:917(send_udp)
  Packet send failed to 192.168.211.255(138) ERRNO=Invalid argument

Even if i can always play some songs here and here, everything that used to work a couple of weeks ago looks broken. Why such regression ?.
and I also get issue if I try to install LMS plugin to try to circumvent this situation :frowning: (See dedicated topic)
Please help even in PM

I really like volumio and its community. Iā€™m superstar / premium subscriber. I have zero local library but Spotify and Tidal premiums only.
I was also a Roon user and the (only?) reason I chose Volumio was the Spotify integration. Now if Spotify is not reliably working Iā€™ve given up on [ unistall / reboot / install ] spop once or twice a week and I use other streamers directly. Since only Tidal works properly Iā€™m considering switching back to Roon as (for me) there is now no advantage of Volumio over Roon - maybe to say now there are Roon advantages over Volumio.
I understand the troubles Volumio devs having now with librespot etc. and I appreciate their hard work time ago while updates were quite often but usualy from nowhere to nowhere. But there is no commitment or deadline for fix and no devs update since Aug 5.

To put it another way, would anybody buy streamer without Spotify support nowadaysā€¦? Volumio Integro - Volumio

Hey, it was vacation time so patience and relaxation. Iā€™m sure fixes will be done as promised.

Just a quick update following the installation of the new beta Volumio.

The Spotify plugin worked fine before the upgrade but now albums will skip several tracks sometimes the whole album after playing the first track on the album.

Thanks for your work on this.

confirmed

Just wanted to follow up since I got no response to my previous post. I frequently lose connection via Spotify Connect and music will just stop playing. Spotify works via AirPlay for the most part. Log below.

Edit to add: I was running 3.0.4 at this time but I have this problem no matter which version of the plug-in I am running, including 3.0.6.


info: CoreCommandRouter::volumioGetState
info: CoreCommandRouter::volumioGetQueue
info: CoreStateMachine::getQueue
info: CorePlayQueue::getQueue
info: CoreCommandRouter::executeOnPlugin: system , getHwuuid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : Loading  with Spotify URI 
[Vollibrespot] :  (261922 ms) loaded
[Vollibrespot] : Event: Next { track_id: SpotifyId { id: 143640362090137082786254072860299566318, audio_type: Track } }
[Vollibrespot] : Event: TrackChanged { old_track_id: SpotifyId { id: 294965212406835724871371003656451360112, audio_type: Track }, track_id: SpotifyId { id: 143640362090137082786254072860299566318, audio_type: Track } }
[SpotifyConnect]  august
info: Is Connect Playback
info: [1664144630581] ControllerSpotify::pushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: MRS: Updating multiroomSync output
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid

info: CoreCommandRouter::volumioGetState
info: CoreCommandRouter::volumioGetQueue
info: CoreStateMachine::getQueue
info: CorePlayQueue::getQueue
info: CoreCommandRouter::executeOnPlugin: system , getHwuuid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid

info: CoreCommandRouter::volumioGetState
info: CoreCommandRouter::volumioGetQueue
info: CoreStateMachine::getQueue
info: CorePlayQueue::getQueue
info: CoreCommandRouter::executeOnPlugin: system , getHwuuid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : Loading  with Spotify URI 
[Vollibrespot] :  (195097 ms) loaded
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid

info: CoreCommandRouter::volumioGetState
info: CoreCommandRouter::volumioGetQueue
info: CoreStateMachine::getQueue
info: CorePlayQueue::getQueue
info: CoreCommandRouter::executeOnPlugin: system , getHwuuid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : Event: Next { track_id: SpotifyId { id: 320139414694566493340466508042817982141, audio_type: Track } }
[Vollibrespot] : Event: TrackChanged { old_track_id: SpotifyId { id: 143640362090137082786254072860299566318, audio_type: Track }, track_id: SpotifyId { id: 320139414694566493340466508042817982141, audio_type: Track } }
[SpotifyConnect]  this is me trying
info: Is Connect Playback
info: [1664144891916] ControllerSpotify::pushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: MRS: Updating multiroomSync output
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : couldn't parse packet from 192.168.0.111:5353: query type 65 is invalid
[Vollibrespot] : Unable to load audio item.
[Vollibrespot] : SessionError: Connection reset by peer (os error 104)
volspotconnect.service: Succeeded.
volspotconnect.service: Service RestartSec=2s expired, scheduling restart.
volspotconnect.service: Scheduled restart job, restart counter is at 5.
Stopped Volspotconnect2 Daemon.
Started Volspotconnect2 Daemon.
vollibrespot v0.2.5 8922128 2022-05-31 (librespot 08d8bcc 2020-10-07) -- Built On 2022-05-31
Reading Config from "/tmp/volspotify.toml"
[Vollibrespot] : Using Alsa backend with device: volumio
[Vollibrespot] : Failed to register IPv6 receiver: Os { code: 19, kind: Uncategorized, message: "No such device" }

After going back and rereading this thread, Iā€™m not sure what the status of this plugin is. Is it considered stable or are bugs being addressed? Iā€™ve seen others post about problems similar to mine and then there are other saying it is stable for most. Iā€™m running Spotify 3.0.6 on Volumio 3.369. The Spotify plugin is mostly unusable for me. It starts out ok and will play a Spotify playlist, but eventually stops responding. I normally notice something has gone wrong while attempting to skip a song. It will just restart the current song and then stop responding until I stop/restart the plugin.

1 Like

You are lost like everyone over there, Spotify is not officially supported by volumio and itā€™s difficult to understand why since I is very popular and its API is opened to developper. My idea is that volumio who offer good sounding solution prefer to favor HQ tidal and Qobuz solutions. Maybe they are right, Qobuz really make the difference
That said, community dĆ©velopper also seems to encounter big issues with new buster plugin architecture since lot of plugins are totally broken in v3. I wish I add the time and skills to help them, the fact they are not so many, they donā€™t look to discuss and help each other, and maybe they are not as ā€œmotivated by high quality coding geniousā€ as they should beā€¦

If you keep adding your views here, people will just say your complaining/whiningā€¦

The plugin doesnā€™t work for many, but looks like the devs are back from vacation, but busy working on other stuffā€¦

1 Like

I do think you are completely wrongā€¦
But please, give me the list of ā€˜lot ofā€™ broken plugins published as stable ā€¦ Iā€™m curious