[SOLVED] Spotify connect stopped playing audio

[Tim Curtis]

I can confirm that compiling the librespot executable from the dev branch of the code (at commit 2ea7436) resolves the issue for me. I also discovered that older versions of the Spotify client (for me on Mac) seemed to cause a different authentication error. This probably explains why the Spotify community support folks are asking if the affected TVs are due a firmware update...

In addition to the dev build did u also have to set $ap_port = '' in /var/www/inc/renderer.php?

[Tim Curtis]

Looks like one of the librespot devs is suggesting that we may need to move to 0.5.0 dev
https://github.com/librespot-org/librespot/issues/1322

If thats the case I'll build a package and upload it tomorrow.

[the_bertrum]

The post I made on the Spotify forum has a lot of people agreeing. Many different devices have the issue. I expect it will be fixed at the Spotify end pretty soon if there are so many different clients that struggle.

https://community.spotify.com/t5/Other-P...22#M115008

[the_bertrum]

Although, there's also this: https://community.spotify.com/t5/Other-P...-p/5401177 so maybe they just don't care ™.
Is one of the differences in 0.5.0 that it uses the new endpoint perhaps?

[DRONE7]

If I may draw a (very) long bow here...

Jim Stafford- Wildwood Weed.
Last phrase = 'and we just smiled and waved sittin' there on that sack of seeds"
5000+ and counting CD's ;-)

[the_bertrum]

If I may draw a (very) long bow here...

Jim Stafford- Wildwood Weed.
Last phrase = 'and we just smiled and waved sittin' there on that sack of seeds"
5000+ and counting CD's ;-)

Yeah, I hear you...
I almost exclusively listen to radio or my own purchased collection precisely so I don't have to rely on the whims of "the man", but Spotify is great for parties

Incidentally, I tried the "use google dns" hack, but it didn't have any effect for me.

[new_bloke]

I can confirm that compiling the librespot executable from the dev branch of the code (at commit 2ea7436) resolves the issue for me. I also discovered that older versions of the Spotify client (for me on Mac) seemed to cause a different authentication error. This probably explains why the Spotify community support folks are asking if the affected TVs are due a firmware update...

In addition to the dev build did u also have to set $ap_port = '' in /var/www/inc/renderer.php?

I didn't, although I'm running an old build of Moode currently. I see other issues, such as the Spotify active overlay not displaying, and the volume control being different, likely caused by the different way the dev version handles player events...
I'm happy to try on the latest version of Moode and report back, if that's helpful...

[the_bertrum]

Incidentally, I tried the "use google dns" hack, but it didn't have any effect for me.

Further incidentally, I forgot about DNS caching. Using google dns (8.8.8.8 and 8.8.4.4) then rebooting everything does work around this problem, at least so far....

[Tim Curtis]

I just resub'd to Premium for a few months on a discount coupon and its playing perfectly on my end with current 0.4.2 librespot.

Below is some log output from /var/log/moode_librespot.log. It shows successful AP fallback.
To get this log turn debug logging on in System Config then restart Spotify Connect.

Code:

pi@moode9:~ $ cat /var/log/moode_librespot.log
[2024-09-05T11:32:27Z INFO  librespot] librespot 0.4.2 22f8aed (Built on 2023-10-15, Build ID: Sbkqf7EN, Profile: release)
[2024-09-05T11:32:27Z TRACE librespot] Command line argument(s):
[2024-09-05T11:32:27Z TRACE librespot]          name "Moode9 Spotify"
[2024-09-05T11:32:27Z TRACE librespot]          bitrate "320"
[2024-09-05T11:32:27Z TRACE librespot]          format "S16"
[2024-09-05T11:32:27Z TRACE librespot]          ap-port "13561"
[2024-09-05T11:32:27Z TRACE librespot]          mixer "softvol"
[2024-09-05T11:32:27Z TRACE librespot]          initial-volume "0"
[2024-09-05T11:32:27Z TRACE librespot]          volume-ctrl "log"
[2024-09-05T11:32:27Z TRACE librespot]          volume-range "60"
[2024-09-05T11:32:27Z TRACE librespot]          cache "/var/local/www/spotify_cache"
[2024-09-05T11:32:27Z TRACE librespot]          disable-audio-cache
[2024-09-05T11:32:27Z TRACE librespot]          backend "alsa"
[2024-09-05T11:32:27Z TRACE librespot]          device "_audioout"
[2024-09-05T11:32:27Z TRACE librespot]          onevent "/var/local/www/commandw/spotevent.sh"
[2024-09-05T11:32:27Z TRACE librespot]          v
[2024-09-05T11:32:27Z DEBUG librespot_discovery::server] Zeroconf server listening on 0.0.0.0:41069
[2024-09-05T11:34:55Z DEBUG librespot_discovery::server] POST "/" {}
[2024-09-05T11:34:55Z WARN  librespot_core::apresolve] Ignoring blacklisted access point ap-gue1.spotify.com:4070
[2024-09-05T11:34:55Z WARN  librespot_core::apresolve] Ignoring blacklisted access point ap-gue1.spotify.com:443
[2024-09-05T11:34:55Z WARN  librespot_core::apresolve] Ignoring blacklisted access point ap-gue1.spotify.com:80
[2024-09-05T11:34:55Z WARN  librespot_core::apresolve] Ignoring blacklisted access point ap-gew4.spotify.com:80
[2024-09-05T11:34:55Z WARN  librespot_core::apresolve] Failed to resolve Access Point: Unable to resolve any viable access points.
[2024-09-05T11:34:55Z WARN  librespot_core::apresolve] Using fallback "ap.spotify.com:443"
[2024-09-05T11:34:55Z INFO  librespot_core::session] Connecting to AP "ap.spotify.com:443"
[2024-09-05T11:34:55Z INFO  librespot_core::session] Authenticated as "moodeaudio" !
[2024-09-05T11:34:55Z DEBUG librespot_core::session] new Session[0]
[2024-09-05T11:34:55Z INFO  librespot_playback::mixer::softmixer] Mixing with softvol and volume control: Log(60.0)
[2024-09-05T11:34:55Z DEBUG librespot_connect::spirc] new Spirc[0]
[2024-09-05T11:34:55Z DEBUG librespot_connect::spirc] canonical_username: moodeaudio
[2024-09-05T11:34:55Z DEBUG librespot::component] new MercuryManager
[2024-09-05T11:34:55Z DEBUG librespot_playback::player] new Player[0]
[2024-09-05T11:34:55Z INFO  librespot_playback::convert] Converting with ditherer: tpdf
[2024-09-05T11:34:55Z INFO  librespot_playback::audio_backend::alsa] Using AlsaSink with format: S16
[2024-09-05T11:34:55Z DEBUG librespot_playback::player] command=AddEventSender
[2024-09-05T11:34:55Z DEBUG librespot_playback::player] command=VolumeSet(0)
[2024-09-05T11:34:55Z INFO  librespot::player_event_handler] Running ["/var/local/www/commandw/spotevent.sh"] with environment variables {"PLAYER_EVENT": "volume_set", "VOLUME": "0"}
.
.
.

This would suggest that the 0.4.2 release is still ok and possibly Spotify's AP network config got messed up preventing some regions from being able to connect to an AP for that region.

In any case I did build a 0.5.0-dev package and I'll test that later today.

[MagnusT]

With no changes to anything, now everything works again as it should. Spotify did something ...