Subsonic Forum

by **phillipmcmahon** » Tue May 12, 2015 1:31 pm

I have just upgraded my Sonos system to the 5.4 beta release and it appears to break the subsonic integration. I have tried both methods of adding the service. First by using the built-in Sonos functionality in Subsonic and just receive an error stating that it cannot be enabled.

Enabling Sonos music service, using Sonos controller IP 192.168.1.101, SID 242, and Subsonic URL http://192.168.1.50:4040/ws/Sonos
Failed to enable/disable music service in Sonos controller 192.168.1.101: org.apache.http.client.HttpResponseException: Method Not Allowed

The trying to add the service via the customsd.htm page on one of my Sonos devices. On submission of the values that worked with the 5.3 software I now get a internal server error.

I am more than happy to help debug etc. but just need told what to do.

Phill

by **lpr** » Tue May 12, 2015 4:41 pm

I just updated to 5.4 beta and my current Subsonic integration is working... Hope we can find what broke yours.

by **phillipmcmahon** » Tue May 12, 2015 4:46 pm

lpr wrote:I just updated to 5.4 beta and my current Subsonic integration is working... Hope we can find what broke yours.

now that is strange.

all i did for my upgrade was the standard process. my custom subsonic service was then no longer available once everything restarted. no amount of trying via customsd.htm or the in-built Subsonic option seems to work for me.

phill

by **phillipmcmahon** » Tue May 12, 2015 4:54 pm

lpr wrote:I just updated to 5.4 beta and my current Subsonic integration is working... Hope we can find what broke yours.

Based on all being well for you and the strange server error I decided the reboot every component in the Sonos collection and now the in-built Sonos/Subsonic capability is working but the customsd.htm route isn't.

I get the following in subsonic.log

12/05/15 18:57:21 CEST] INFO SonosService Found Sonos controllers: [192.168.1.109, 192.168.1.101, 192.168.1.114, 192.168.1.112, 192.168.1.122, 192.168.1.115, 192.168.1.125, 192.168.1.108, 192.168.1.113, 192.168.1.111]
[12/05/15 18:57:21 CEST] INFO SonosServiceRegistration Disabling Sonos music service, using Sonos controller IP 192.168.1.109, SID 242, and Subsonic URL http://192.168.1.50:4040/ws/Sonos
[12/05/15 18:57:21 CEST] WARN SonosService Failed to enable/disable music service in Sonos controller 192.168.1.109: org.apache.http.client.HttpResponseException: Method Not Allowed
[12/05/15 18:57:21 CEST] INFO SonosServiceRegistration Disabling Sonos music service, using Sonos controller IP 192.168.1.101, SID 242, and Subsonic URL http://192.168.1.50:4040/ws/Sonos
[12/05/15 18:57:21 CEST] WARN SonosService Failed to enable/disable music service in Sonos controller 192.168.1.101: org.apache.http.client.HttpResponseException: Method Not Allowed
[12/05/15 18:57:21 CEST] INFO SonosServiceRegistration Disabling Sonos music service, using Sonos controller IP 192.168.1.114, SID 242, and Subsonic URL http://192.168.1.50:4040/ws/Sonos
[12/05/15 18:57:21 CEST] INFO SonosServiceRegistration Sonos controller returned: <html><head><title>success</title></head><body>success!</body></html>
[12/05/15 18:57:21 CEST] INFO SonosService Found Sonos controllers: [192.168.1.109, 192.168.1.101, 192.168.1.114, 192.168.1.112, 192.168.1.122, 192.168.1.115, 192.168.1.125, 192.168.1.108, 192.168.1.113, 192.168.1.111]
[12/05/15 18:57:21 CEST] INFO SonosServiceRegistration Enabling Sonos music service, using Sonos controller IP 192.168.1.109, SID 242, and Subsonic URL http://192.168.1.50:4040/ws/Sonos
[12/05/15 18:57:21 CEST] WARN SonosService Failed to enable/disable music service in Sonos controller 192.168.1.109: org.apache.http.client.HttpResponseException: Method Not Allowed
[12/05/15 18:57:21 CEST] INFO SonosServiceRegistration Enabling Sonos music service, using Sonos controller IP 192.168.1.101, SID 242, and Subsonic URL http://192.168.1.50:4040/ws/Sonos
[12/05/15 18:57:21 CEST] WARN SonosService Failed to enable/disable music service in Sonos controller 192.168.1.101: org.apache.http.client.HttpResponseException: Method Not Allowed
[12/05/15 18:57:21 CEST] INFO SonosServiceRegistration Enabling Sonos music service, using Sonos controller IP 192.168.1.114, SID 242, and Subsonic URL http://192.168.1.50:4040/ws/Sonos
[12/05/15 18:57:21 CEST] INFO SonosServiceRegistration Sonos controller returned: <html><head><title>success</title></head><body>success!</body></html>

The .101 and .109 devices are a Boost and Sub respectively. The .114 device is a Play:1.

Attempting the custom addition via http://192.168.1.114:1400/customsd.htm returns a server error with values I know to be working on the previous 5.3 software. I am using the autofill of my browser so am confident I am not introducing typos.

I have raised a ticket with Sonos as all things being equal the only thing that has changes is my Sonos software to a beta version so I imagine they broke something via their customsd.htm submission...

I will update this thread once they give me some information.

Phill

by **phillipmcmahon** » Fri May 15, 2015 6:55 pm

It seems to be the endpoint and secure endpoint value that is causing 5.4 to return an error when using the customsd.htm page

http://server.phillipmcmahon.com:4040/w ... cmahon.com causes an error whereas http://server.phillipmcmahon.com:4040/ws/Sonos is accepted.

Is someone willing to test my external access to Subsonic using this value (without the ?ip=...) to see if it works correctly?

Thanks,

Phill

by **phillipmcmahon** » Thu Jun 18, 2015 4:56 pm

I am pretty sure after talking to Sonos that they won't fix what has changed in 5.4 and broken external Subsonic use using the current method.

The element of the URL causing the issue is the part after (and including) the ? in the service URL.

http://SUBSONIC_IP:4040/ws/Sonos?ip=SUBSONIC_IP

@Sindre - I don't know whether programmatically you can make this work again and not require the parameter in the URL as currently documented?

This would be a great feature to lose.

Phill

by **sindre_mehus** » Sun Jun 21, 2015 10:28 am

Thanks for letting me know. I'll install Sonos 5.4 and see what I can do.

Sindre

by **sindre_mehus** » Sun Jun 21, 2015 7:03 pm

I've upgraded to Sonos 5.4 beta (build 29590161), but I'm not able to reproduce the problem.

Both the automatic and manual registration procedures works on my system, also using the "?ip=xxx" part.

Can you please provide a screenshot of the values entered on the customsd.htm page?

Thanks
Sindre

by **phillipmcmahon** » Sun Jun 21, 2015 7:10 pm

Thanks for the quick response.

The value I enter, and which still works on version 5.3 is

http://server.phillipmcmahon.com:4040/w ... cmahon.com

I get the server error message with this. If I remove the "?ip=server.phillipmcmahon.com" then I can add the service but it is now no longer available externally.

Happy you try and add my system and I can give you an account if needed.

Phill

by **phillipmcmahon** » Sun Jun 21, 2015 7:20 pm

I get this pretty generic error message (see attached)

by **sindre_mehus** » Sun Jun 21, 2015 7:30 pm

Thanks!

I do get the same error when using your URL. Seems to break if the URL is 70 characters or longer, so I'm guessing that's a limit in Sonos.

As a work-around, try to use the IP address instead.

Sindre

by **phillipmcmahon** » Sun Jun 21, 2015 7:36 pm

Ah ha, speedy diagnosis

Thanks sir!

I will have to use some other dynamic DNS name. My ISP aggressively dishes out new WAN IP addresses meaning using the IP is next to useful for people I share this out with.

Appreciate you looking into this for me.

5.4 adds some nice features BTW. Better Google Music and Spotify integration. Bonus!

Phill

by **phillipmcmahon** » Sun Jun 21, 2015 7:46 pm

Registered a new shorter ddns.net entry and will use that to add the service to external Sonos users. Works perfectly!

Phill

by **sindre_mehus** » Sun Jun 21, 2015 7:54 pm

That's great!

Did it work with the long URL in Sonos 5.3?

by **phillipmcmahon** » Sun Jun 21, 2015 8:16 pm

sindre_mehus wrote:That's great!

Did it work with the long URL in Sonos 5.3?

Yes it did, never a problem.

Possibly something to let users know about once 5.4 comes online. Saying that, I wonder how many users use the external library access feature. For me it is a killer feature. Your software always rocked but with this new Sonos integration it will surely get more and more of a user base. The chap at Sonos I spoke with was seriously interested in this and wasn't aware of it. You are the solution to their 65k limit plus a few other items.

Thanks again for the speedy help.

Subsonic Forum

Sonos 5.4 beta breaks integration

Sonos 5.4 beta breaks integration

Re: Sonos 5.4 beta breaks integration

Re: Sonos 5.4 beta breaks integration

Re: Sonos 5.4 beta breaks integration

Re: Sonos 5.4 beta breaks integration

Re: Sonos 5.4 beta breaks integration

Re: Sonos 5.4 beta breaks integration

Re: Sonos 5.4 beta breaks integration

Re: Sonos 5.4 beta breaks integration

Re: Sonos 5.4 beta breaks integration

Re: Sonos 5.4 beta breaks integration

Re: Sonos 5.4 beta breaks integration

Re: Sonos 5.4 beta breaks integration

Re: Sonos 5.4 beta breaks integration

Re: Sonos 5.4 beta breaks integration

Who is online