Sonos problems with Docker

Setup, Configuration and Use Installation
, ,
21

Hi Patrick,

I set it to
8086

I’ve tried another port but in my case it still did not work.

BR
/Franz

22

OK, thought maybe you have used another port but that’s the default and I still can’t see how that interferes with UPNP.

Anyway, to get rid of my virtual machine, I now installed the second openhab instance on a raspberry pi. I have one running pihole and I just installed openhab on that one. I only have the Sonos things / items and connect to the main openhab installation via the remote binding. Solves it for me.

23

Hi.

I’m struggling as well with this issue.

I’m trying to make openhab 3.2.0.M4-debian work from Docker.

I’ve updated log4j2.xml to increase jupnp log level to WARN.

<Logger level="WARN" name="org.jupnp"/>

In the logs I receive this messages:

2021-11-26 12:40:14.796 [WARN ] [p.protocol.RetrieveRemoteDescriptors] - Device descriptor retrieval failed, no response: http://xxxxxxx:8200/rootDesc.xml

2021-11-26 12:40:35.777 [WARN ] [p.protocol.RetrieveRemoteDescriptors] - Device descriptor retrieval failed, no response: http://yyyyyyyy:1400/xml/group_description.xml

xxxxxx and yyyyy are the IP addresses of a DLNA MediaServer and a Sonos device. From within the openhab container, I can successfully curl to both this urls.

In my case, running influxdb with network_mode host vs with port 8086 exposed doesn’t make a difference.

I’m using pfSense as router and I’ve added a LAN rule to specifically allow LAN 1400 and 8200 ports, just in case.

The only difference in my case is that I added a nginx reverse proxy to the stack.

@FranzS - Do you have this working by just setting the influxdb network mode to host?

EDIT: @pgruetter - I’ll have to implement your workaround for now. Thanks.

24

@m_g_s_g , yes Setting host worked!

26

The workaround helped for me as well, however I had to apply it to some other containers too like telegraf, grafana, etc. Thanks guys!

1 Like