Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connect only working from one device #58

Open
amsound opened this issue Apr 13, 2022 · 9 comments
Open

Connect only working from one device #58

amsound opened this issue Apr 13, 2022 · 9 comments

Comments

@amsound
Copy link

amsound commented Apr 13, 2022

Hi Michael,

Not sure what's going on but my phone connects to Spotty via Connect fine but a couple of other devices do not work. The device shows it's connected however LMS doesn't play or show anything.

I have uploaded a log for you on your dropbox "alex server connect logging.log"

You help would be much appreciated.

@michaelherger
Copy link
Owner

This would happen in a few cases:

  • other phones/devices aren't on the same network (mobile vs. wlan)
  • "local announcements" are disabled or can't work due to some conflict on the host system (what OS are you running LMS on? What other services)?
  • LMS is run in Docker (don't know the condition by heart)

Anything that might apply to your situation?

@amsound
Copy link
Author

amsound commented Apr 14, 2022

All devices def on the same wifi network.
Not sure what are local announcements are?
Running on a pretty vanilla version of Debian 9

@michaelherger
Copy link
Owner

Check the Spotty settings. there's a checkbox to "disable local announcements" (which can get checked automatically if it repeatedly fails to use them). When these announcements are disabled, only the account connected to LMS would be able to see the player.

@amsound
Copy link
Author

amsound commented Apr 17, 2022

No, this is not selected and there are no other options selected. I should re-iterate all devices can "see" the player. This isn't the issue.

I have just re-installed my whole system using Debian 11 64bit and LMS 8.3 and I'm experiencing the same.

@amsound
Copy link
Author

amsound commented Apr 23, 2022

Any thoughts Michael?

@KlausMu
Copy link

KlausMu commented Dec 12, 2022

I have the same issue. No matter if the option

Don't announce Squeezebox players running in Spotify Connect mode in your network. Check this option if you don't want your Spotify Connect enabled Squeezebox player to show up in all Spotify apps in your network.

is set or not, I have the following behaviour:
I have two spotifiy accounts registered in "Spotty Spotify for Squeezebox". When I select "My Apps - Spotty - 'Account name' - Albums", the device immediately disappears in the Spotify Connect device list in one account and appears at the same second in the other account (checked with the Spotify Android app running on two phones with different accounts). No way to have the spotty device in two accounts at the same time.

Any hint?

@michaelherger
Copy link
Owner

Make sure you do NOT disallow announcements using that option. And once you've reset that switch, give it some time. And make sure your devices are all on the same network. Mobile phones sometimes stick to cell instead of switching to wifi etc.

@KlausMu
Copy link

KlausMu commented Dec 12, 2022

I think I found the issue. I'm running LMS in docker. As mentioned here, Spotty only works correctly when it is running in host mode.
Only when running in host mode, I can see Spotty listening on these ports (sudo netstat -tulpn | grep LISTEN). Otherwise these entries are missing:
tcp 0 0 0.0.0.0:35963 0.0.0.0:* LISTEN 2196328/spotty
tcp 0 0 0.0.0.0:35397 0.0.0.0:* LISTEN 2196330/spotty
tcp 0 0 0.0.0.0:37369 0.0.0.0:* LISTEN 2196327/spotty

@sophof
Copy link

sophof commented Feb 21, 2024

I think I found the issue. I'm running LMS in docker. As mentioned here, Spotty only works correctly when it is running in host mode. Only when running in host mode, I can see Spotty listening on these ports (sudo netstat -tulpn | grep LISTEN). Otherwise these entries are missing: tcp 0 0 0.0.0.0:35963 0.0.0.0:* LISTEN 2196328/spotty tcp 0 0 0.0.0.0:35397 0.0.0.0:* LISTEN 2196330/spotty tcp 0 0 0.0.0.0:37369 0.0.0.0:* LISTEN 2196327/spotty

Thanks, this was the issue for me as well!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants