Subsonic Forum

by **teamhood** » Wed Nov 30, 2016 2:49 am

Hey All -
I've been using Subsonic Premium for quite a few years without any real trouble. I went out and bought some Sonos speakers today and I have been having a heck of time trying to get this to work. I got it to fully work, one time, when I added in the 'Remote Network' fix. Sonos was able to play/Brose my entire Subsonic for about 12 hours, but then for no real reason stopped working. By no reason, I mean literally nothing what changed and it just stopped. I have added back that Fix, and I am able to get through the login screen within the Sonos controller, but then when I go to the service, it states ' Unable to Browse'.

I am on Subsonic V6. I have Sonos enabled. I see Subsonic in Sonos Controller service, but when I go to try and add it, it lags, but gets to the login and then gives the error 'Connection Error - There was a problem adding the account'

I was looking at the Subsonic log via the Web URL and I notice the following:
11/29/16 7:43:12 PM CST] INFO BootstrapVerificationFilter Servlet container: jetty-6.1.x
[11/29/16 7:43:16 PM CST] INFO SonosService Found Sonos controllers: [192.168.0.183, 192.168.0.184]
[11/29/16 7:43:16 PM CST] INFO SonosServiceRegistration Enabling Sonos music service, using Sonos controller IP 192.168.0.183, SID 242, and Subsonic URL http://192.168.122.1:4040/ws/Sonos
[11/29/16 7:43:16 PM CST] INFO SonosServiceRegistration Sonos controller returned: <html><head><title>success</title></head><body>success!</body></html>

I have a question; Why is Subsonic going to that URL? That is not a valid IP on my LAN. The correct IP for Subsonic is 192.168.0.200

Any Thoughts?

by **Michael Bech Hansen** » Wed Nov 30, 2016 5:46 pm

Not much help, but I get exactly the same.

/M

by **manwithaplan** » Wed Nov 30, 2016 6:39 pm

What I wonder is whether this would work on an older, more stable build of Subsonic, like 5.2.1 or the like. Folks HAD been using it with Sonos succesfully back then, but I'm not sure if maybe a more recent Sonos software update would mean that 5.2.1 of SS would not work any longer with it. I may have reason to care much more soon :-)

. Right now, I have no Sonos users of my server. Still curious.

by **Michael Bech Hansen** » Wed Nov 30, 2016 7:59 pm

I did have it working previously, but didn't use the Subsonic service from Sonos so deleted it.
Which versions of Sonos and Subsonic that worked I have no idea of, but certainly Sonos software has been updated at least once since it worked for me.

Hopefully Sindre will take care of this.
Subsonic is a workaround for several Sonos users with large collections, and I know several users who use Subsonic only to get around Sonos' track-count limitation.

/M

by **Michael Bech Hansen** » Wed Nov 30, 2016 9:22 pm

So I did some debugging and got it working again in my setup...

I run Subsonic off a Synology NAS, which have dual network interfaces, of which I currently only had one enabled/plugged in.
Using a network sniffer when configuring the Subsonic service in the Sonos app, I could see that the Sonos app tried to connect to the IP address corresponding to the secondary (but un-plugged) network interface on the NAS.
Plugging in a network cable in the secondary interface, everything works.

Whether the Sonos app has some cached memory of a past connection through the secondary network interface, or the Subsonic Sonos service picks the "wrong" network interface, I dont know.
Changing the name of Subsonic Sonos service through the web interface is reflected in the Sonos application immediately with only the one connection from the NAS.
But the secondary network interface is apparently essential to get things working in my setup.

Cheers,
Michael.

by **teamhood** » Thu Dec 01, 2016 8:56 pm

Very interesting. So what I did was the remote server fix and used a different IP on one of the SONOS speakers. Everything is working, but I believe if that speaker looses its IP then i will have to go back and redo the remote settings. There must def be a bug in the code on SS as it's launching a random IP for the subsonic server.

by **teamhood** » Thu Dec 01, 2016 8:57 pm

manwithaplan wrote:What I wonder is whether this would work on an older, more stable build of Subsonic, like 5.2.1 or the like. Folks HAD been using it with Sonos succesfully back then, but I'm not sure if maybe a more recent Sonos software update would mean that 5.2.1 of SS would not work any longer with it. I may have reason to care much more soon . Right now, I have no Sonos users of my server. Still curious.

If I have time over break, I could def spin up an instance and try this out.

Subsonic Forum

Sonos Help

Sonos Help

Re: Sonos Help

Re: Sonos Help

Re: Sonos Help

Re: Sonos Help

Re: Sonos Help

Re: Sonos Help

Who is online