Sonos Players not found: JUPNP cannot get xml from url

Add-ons Bindings
, ,
1

Hi,

I am new to OH and I have an issue adding my Sonos Players. At first I thought its because of Docker, so I installed it directly to the host. Unfortunately, they are still not found.

Platform information:
    Hardware: Intel NUC / 8 GB / SSD
    OS: Debian 10
    Java Runtime Environment: openjdk 11.0.8 2020-07-14
    openHAB version: 3.0.0 release build
Network: Amplifi Mesh, Sonos players using SonosNet (one of them is connected via ethernet to the Amplifi main router)

So a SCAN does not find anything, thus I added the players to a thing file, which results in the same ERROR state as seeing in this thread: Sonos, no players found

I then turned jupnp logging to DEBUG and saw this interesting thing:

2021-01-11 20:43:29.110 [INFO ] [org.jupnp.transport.spi.StreamClient] - Timeout of 10 seconds while waiting for HTTP request to complete, aborting: (StreamRequestMessage) GET http://192.168.132.189:1400/xml/device_description.xml
2021-01-11 20:43:29.111 [WARN ] [p.protocol.RetrieveRemoteDescriptors] - Device descriptor retrieval failed, no response: http://192.168.132.189:1400/xml/device_description.xml
2021-01-11 20:43:30.509 [INFO ] [org.jupnp.transport.spi.StreamClient] - Timeout of 10 seconds while waiting for HTTP request to complete, aborting: (StreamRequestMessage) GET http://192.168.132.132:1400/xml/group_description.xml
2021-01-11 20:43:30.509 [WARN ] [p.protocol.RetrieveRemoteDescriptors] - Device descriptor retrieval failed, no response: http://192.168.132.132:1400/xml/group_description.xml
2021-01-11 20:43:35.477 [INFO ] [org.jupnp.transport.spi.StreamClient] - Timeout of 10 seconds while waiting for HTTP request to complete, aborting: (StreamRequestMessage) GET http://192.168.132.15:1400/xml/group_description.xml
2021-01-11 20:43:35.477 [WARN ] [p.protocol.RetrieveRemoteDescriptors] - Device descriptor retrieval failed, no response: http://192.168.132.15:1400/xml/group_description.xml

those are the IP addresses of my Sonos players. So I tried to wget those URLs from the host Openhab is running on, which worked fine:

wget http://192.168.132.132:1400/xml/group_description.xml
--2021-01-11 20:46:20--  http://192.168.132.132:1400/xml/group_description.xml
Connecting to 192.168.132.132:1400... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/xml]
Saving to: ‘group_description.xml’

group_description.xml                                                [ <=>                                                                                                                                                     ]     824  --.-KB/s    in 0s      

2021-01-11 20:46:20 (7.23 MB/s) - ‘group_description.xml’ saved [824]

also the content of the XML looks ok:

<root>
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<device>
<deviceType>urn:smartspeaker-audio:device:SpeakerGroup:1</deviceType>
<friendlyName>Kinderzimmer</friendlyName>
<manufacturer>SONOS</manufacturer>
<UDN>uuid:RINCON_B8E9375E893A01400</UDN>
<apiVersion>1.22.1</apiVersion>
<minApiVersion>1.1.0</minApiVersion>
<serviceList>
<service>
<serviceType>urn:smartspeaker-audio:service:SpeakerGroup:1</serviceType>
<serviceId>urn:smartspeaker-audio:serviceId:SpeakerGroup</serviceId>
<controlURL>/ssdp/notfound</controlURL>
<eventSubURL>/ssdp/notfound</eventSubURL>
<SCPDURL>/ssdp/notfound</SCPDURL>
</service>
</serviceList>
</device>
</root>

loading the file also takes less than the 10 seconds that are used as a timeout by jupnp.

any idea whats up there?

2

No, not exactly. Like you saw in the thread I had a similar issue that I was unable to solve. I suspect some other services interferes. I made it work by spinning up another virtual server and running openhab from there with out any other services. So I have my databases mqtt server and other stuff separate from my openhab. Whether thats the difference or simply a fresh install I don’t know.

1 Like
3

Is your Java version OpenJDK 11 or Zulu 11 ?
If it is not Zulu 11, please change to Zulu and try again as this is the recommended Java JDK.
I saw simolar issues in the past with the Wemo binding that could be solved by changing Java version.

4

On Debian it is OpenJDK, but the Behaviour is the same with the official Docker Container that’s running Zulu.

Anyway I will try to change the Debian install to Zulu as well, thanks.

5

so, I finally found out what was going on: I had an instance of AirSonos running on the same host. Stopping that Sonos in OpenHAB now works fine.

so thanks for the hints :slight_smile:

1 Like
6

I think the problem I described here is similar, at least I get the same output now that I activated the logs.
But I don’t use AirSonos.

Do you have any more insights on what the exact conflict was? Thanks