[Announce] Spotty 4.0 - integrate local library with your Spotify collection (LMS 8+)

[gorman]

That's really odd. Something's blocking the local announcements. But you've already disabled way more than should be needed, and still it doesn't work. I'm running out of ideas...

I'm sorry to be taking so much time for this :-/

Rechecking the port, I now see that there's another service listening on it. Dnscache.

The DNS Client service (dnscache) caches Domain Name System (DNS) names and registers the full computer name for this computer. If the service is stopped, DNS names will continue to be resolved. However, the results of DNS name queries will not be cached and the computer's name will not be registered. If the service is disabled, any services that explicitly depend on it will fail to start.

I don't think this could be the source of the problem, though.

Is there any way to test Spotty on a different port? Launching it through command line or something, maybe... but probably the port is determined by Spotify Connect and its protocol, not up to us.

[von-Ah]

Is there a way to save an LMS queue of spotty tracks as a Spotify playlist to my Spotify account? I like how spotty will add ~200 songs for queueing up an ‘artist radio,’ while the Spotify app will only queue up 30 or so.

[mherger]

Is there a way to save an LMS queue of spotty tracks as a Spotify playlist to my Spotify account? I like how spotty will add ~200 songs for queueing up an ‘artist radio,’ while the Spotify app will only queue up 30 or so.

No, there's no writing of complete Spotify playlists from Spotty.

[von-Ah]

Understood. Thanks for the quick response.

[CJS]

Maybe this is a stupid question but... Any obvious reason why, from my daughter's iPhone, she does not see the Spotify Connect endpoints (one Boom and one SB2) that I have activated for the plugin?

I experience a similar issue. The Spotify app on my Android phone does not see my SB Boom that I have enabled as Spotify Connect endpoint in the LMS Spotty plugin (see screenshot below), unless I disable the firewall on my Linux Mint server that runs LMS. However I would like to keep the firewall enabled. Based on the suggestion by mherger in post 1209 to open port 5353/udp, I opened port 5353 as follows:

sudo ufw allow 5353/udp
sudo ufw enable

But after enabling the firewall again the Spotify app on my phone still does not see my SB Boom. If I disable the firewall the SB Boom does show up in the Spotify app, and I can start Spotify playback on my Boom. If I then enable the firewall again, playback stays working. So it seems that only discovery of Spotify Connect endpoints does not work with firewall enabled.

=> Any suggestions on which additional ports should be opened on my firewall to enable discovery of Squeezebox players as Spotify Connect endpoints?

[Man in a van]

Works here, LMS on a thin client running Windows, all settings default



ronnie

[CJS]

Works here, LMS on a thin client running Windows, all settings default
ronnie

Good for you . So you suggest I should run LMS on Windows?
Spotify Connect works fine with LMS (with Spotty plugin) running on Linux Mint with ufw firewall disabled. However I would like it to work with firewall enabled. So I am looking for firewall rules for Spotify Connect.

[Man in a van]

I have never used ufw but have just installed it on my Debian (Bookworm beta) computer

[email protected]:~$ sudo ufw status verbose
[sudo] password for ronnie:
Status: active
Logging: on (low)
Default: deny (incoming), allow (outgoing), disabled (routed)
New profiles: skip

To Action From
-- ------ ----
22/tcp ALLOW IN Anywhere
80/tcp ALLOW IN Anywhere
443 ALLOW IN Anywhere
6000:6007/tcp ALLOW IN Anywhere
6000:6007/udp ALLOW IN Anywhere
9000 ALLOW IN Anywhere
9090 ALLOW IN Anywhere
3483 ALLOW IN Anywhere

[email protected]:~$

Connected my Boom into the Debian LMS and installed Spotty.

I can use my iPHone 6s to playback spotify-connect on the Boom

i can playback album using squeezelite on the Boom.

However internet radio, BBC, fip, Radio Paradise does not playback

[23-04-18 00:43:13.7830] Slim::Player::Song:pen (424) Error: Couldn't create command line for ogf playback for [http://stream.radioparadise.com/flac]
[23-04-18 00:43:34.0549] Slim::Player::Song:pen (424) Error: Couldn't create command line for aac playback for [sounds://_LIVE_bbc_radio_two]
[23-04-18 00:43:44.9400] Slim::Player::Song:pen (424) Error: Couldn't create command line for aac playback for [sounds://_LIVE_bbc_radio_two]
[23-04-18 00:43:47.5536] Slim::Player::Song:pen (424) Error: Couldn't create command line for aac playback for [sounds://_LIVE_bbc_radio_two]
[23-04-18 00:47:00.7805] Slim::Player::Song:pen (424) Error: Couldn't create command line for aac playback for [sounds://_LIVE_bbc_6music]
[23-04-18 00:47:34.5264] Slim::Player::Song:pen (424) Error: Couldn't create command line for aac playback for [sounds://_LIVE_bbc_6music]
[23-04-18 00:47:42.9322] Slim::Player::Song:pen (424) Error: Couldn't create command line for aac playback for [sounds://_LIVE_bbc_radio_three]
[23-04-18 00:48:08.6125] Slim::Player::Song:pen (424) Error: Couldn't create command line for aac playback for [sounds://_LIVE_bbc_radio_three]
[23-04-18 00:48:16.0579] Slim::Player::Song:pen (424) Error: Couldn't create command line for aac playback for [sounds://_LIVE_bbc_radio_three]
[23-04-18 00:51:59.7500] Slim::Player::Song:pen (424) Error: Couldn't create command line for aac playback for [hlsplays://stream.radiofrance.fr/fip/fip_hifi.m3u8|]
[23-04-18 00:52:07.2016] Slim::Player::Song:pen (424) Error: Couldn't create command line for aac playback for [hlsplays://stream.radiofrance.fr/fip/fip_hifi.m3u8|]
[23-04-18 00:53:10.0383] Slim::Player::Song:pen (424) Error: Couldn't create command line for aac playback for [hlsplays://stream.radiofrance.fr/fip/fip_hifi.m3u8|]

I'll try and play later today, off to bed now.

Have you tried using the Boom IP address in the ufw rules ?

atb

ronnie

[Man in a van]

All good now

Logitech Media Server Status
Logitech Media Server Version: 8.4.0 - 1680780553 @ Thu 06 Apr 2023 01:56:49 PM CEST
Hostname: debian
IP: 192.168.1.188
HTTP Port: 9000
OS: Debian - EN_GB - utf8
Platform: i686-linux
Perl Version: 5.36.0 - i686-linux-gnu-thread-multi-64int
Audio::Scan: 1.06
IO::Socket::SSL: 2.081
Database Version: DBD::SQLite 1.58 (sqlite 3.22.0)
Total Players Recognized: 2

​
login as: ronnie
[email protected]'s password:
Linux debian 6.1.0-7-686-pae [NODE="1"]Home[/NODE] SMP PREEMPT_DYNAMIC Debian 6.1.20-2 (2023-04-08) i686

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Tue Apr 18 09:20:09 2023 from 192.168.1.153
[email protected]:~$ sudo ufw enable
[sudo] password for ronnie:
Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
Firewall is active and enabled on system startup
[email protected]:~$ sudo ufw status numbered
Status: active

To Action From
-- ------ ----
[ 1] 22/tcp ALLOW IN Anywhere
[ 2] 80/tcp ALLOW IN Anywhere
[ 3] 443 ALLOW IN Anywhere
[ 4] 6000:6007/tcp ALLOW IN Anywhere
[ 5] 6000:6007/udp ALLOW IN Anywhere
[ 6] 9000/tcp ALLOW IN Anywhere
[ 7] 9000/udp ALLOW IN Anywhere
[ 8] 9090/tcp ALLOW IN Anywhere
[ 9] 9090/udp ALLOW IN Anywhere
[10] 3483/tcp ALLOW IN Anywhere
[11] 3483/udp ALLOW IN Anywhere

[email protected]:~$ sudo reboot

Broadcast message from [email protected] on pts/1 (Tue 2023-04-18 09:41:34 BST):

The system will reboot now!

[email protected]:~$

This was my problem; when I installed LMS I downloaded the deb and used the package manager to perform the install (I wanted to tested if it worked).

The was a message about sandboxing that i ignored as everything seemed to work (I was not using ufw at this time)

This morning I upgraded to LMS v8.4.0 and got the same sandbox message. I then ran sudo dpkg -i ..............deb

I can now playback (into the BOOM) all my favourite internet radio stations, local music files and use spotty in the LMS web face

Using the Spotify Desktop I can select the BOOM as a Spotify-Connect player and it works (just a slight delay on starting)

ronnie

Edit: just to add that I am using the Local Player Plugin (which could do with some love )

[CJS]

All good now

[email protected]:~$ sudo ufw status numbered
Status: active

To Action From
-- ------ ----
[ 1] 22/tcp ALLOW IN Anywhere
[ 2] 80/tcp ALLOW IN Anywhere
[ 3] 443 ALLOW IN Anywhere
[ 4] 6000:6007/tcp ALLOW IN Anywhere
[ 5] 6000:6007/udp ALLOW IN Anywhere
[ 6] 9000/tcp ALLOW IN Anywhere
[ 7] 9000/udp ALLOW IN Anywhere
[ 8] 9090/tcp ALLOW IN Anywhere
[ 9] 9090/udp ALLOW IN Anywhere
[10] 3483/tcp ALLOW IN Anywhere
[11] 3483/udp ALLOW IN Anywhere

Using the Spotify Desktop I can select the BOOM as a Spotify-Connect player and it works (just a slight delay on starting)
Edit: just to add that I am using the Local Player Plugin (which could do with some love )

Thanks ronnie for this investigation! When I compare your firewall status on Debian with my firewall status on Linux Mint 20.3, the main difference is that you have opened ports 6000 to 6007. Are these ports opened to make Spotify Connect work? If so, where did you find information that these ports are used by Spotify Connect?

FYI, I have only little time to investigate further today. I was thinking that maybe I need to add an application based rule to ufw for Spotify Connect, that opens a range of udp ports (and maybe only for connection from a limited range of IP addresses on my local LAN).That is why I wonder what is the purpose of opening ports 6000 to 6007.

[Man in a van]

CJS

I know nothing about ufw so I did a web search and found this

Edit:

https://www.digitalocean.com/community/tutorials/how-to-set-up-a-firewall-with-ufw-on-debian-11-243261243130246d443771547031794d72784e6b36656d4a326e49732e

the suggestion under the header Specific Port Ranges

seemed a good one so that's what I did

Whilts searching I found an old question about Ubuntu / Port opening and Spotify-Connect from around the time the facility was added into the Spotify Desktop. (I have no idea about a link, sorry).

Any way, as I remember it, it said Spotify-Connect did not require specific port opening (or something like that)

Sorry I can't be more specific, but I think it should just work.

When I use a raspberrypi and Spotify I usually build a Librespot instance on the pi and use that as a Spotify-Connect player, rather than the LMS instance (for me , it's a more convenient way to use Spotify).

Hope ths helps

ronnie

[CJS]

Thanks Man in a van for your reply. From your reply it was not clear to me if you opened ports 6000 to 6007 to make the Spotty Spotify Connect function work for you. I opened these ports on my Linux Mint system that runs LMS. But unfortunately that did not help. With these ports opened my SB Boom still does not show up as Spotify Connect endpoint in the Spotify app on my Android phone. For completeness I show you the status of my ufw firewall after opening ports 6000 to 6007:

$ sudo ufw status verbose
Status: active
Logging: off
Default: deny (incoming), allow (outgoing), disabled (routed)
New profiles: skip

To                         Action      From
--                         ------      ----
137,138/udp (Samba)        ALLOW IN    Anywhere
139,445/tcp (Samba)        ALLOW IN    Anywhere
3483/tcp                   ALLOW IN    Anywhere
3483/udp                   ALLOW IN    Anywhere
9000/tcp                   ALLOW IN    Anywhere
9090/tcp                   ALLOW IN    Anywhere
80/tcp                     ALLOW IN    Anywhere
443/tcp                    ALLOW IN    Anywhere
2049                       ALLOW IN    192.168.178.19
22/tcp                     ALLOW IN    Anywhere
6000:6007/tcp              ALLOW IN    Anywhere
6000:6007/udp              ALLOW IN    Anywhere​

As said, opening ports 6000 to 6007 did not help, so I have now closed them again. Anyway, it is not a big deal. I can still stream Spotify tracks to all my Squeezebox players by controlling Spotty using LMS Material apk on my phone. And if I spent time, I am sure I can make Spotify Connect work by opening a larger range of ports in my ufw firewall.

There is still one question I have:

CJS
I know nothing about ufw so I did a web search and found this
the suggestion under the header Specific Port Ranges
seemed a good one so that's what I did

You say you "found this", but it seems that you forgot to add a link.
If the suggestion that you found about "Specific Port Ranges" is related to ports used by Spotify Connect, then it would be helpful if you could provide an URL. No need however to spent significant time on finding back this info.

[Man in a van]

CJS

link added into my previous post (sorry about that, I'm currently binge watching "Taggert"

Have you tried from the Sotify Desktop ?




It works on my old Moto G (Android 5.1)



As a last ditch fix, have you cleared all browser caches, restarted / reset the router, power down the Boom for 24 hours

ronnie

[mherger]

In the Spotify apps there's an option to only show local devices - or those known on the Spotify servers. If you disable "local only" in the app, you should be able to see your devices.

I do understand that this might be ok if it's just about you and your device. But it wouldn't help in the case where you want to have devices show up in everybody's phones in the local network.

[Man in a van]

Edit: I just realised that Michael likely means the Spotify Desktop and smartphones app settings, sorry. doh!




For info; I'm on default settings







ronnie