Last update broke sonos discovery

[SebDominguez]

Hi there!

Describe the bug Just updated to the last version of tts-ultimate ans unfortunately it seems that my sonos cannot see the endpoint at the port 1980 anymore. To Reproduce Steps to reproduce the behavior: This is my docker run command

#! /bin/bash
docker run \
-d \
--restart unless-stopped \
-e "NODE_RED_CREDENTIAL_SECRET=XXX" \
-e "NODE_RED_CREDENTIAL_HASHED=XXX" \
--net=host \
-v $(pwd)/data:/data \
-e PUID=$(id -u) \
-e PGID=$(id -g) \
-e TZ=Europe/Madrid \
--name node-red \
nodered/node-red:latest

Screenshots

TTS-Ultimate Version

• V1.0.41

Are you running node-red behind homematic, docker or anything similar?

• Node-red running inside a docker container

Additional context I'm well aware of the networks problems that can occur when using a dockerized application. That's why I've used the --net=host option so the container share the network stack of the host so every ports and mdns stuff can pass through.

I've used the 1.0.20 so far and was able to use the node without problems.

[Supergiovane]

Hi please check the port forwarding if you're in nat mode. Try also to change the port and restart node-red

[SebDominguez]

Hi please check the port forwarding if you're in nat mode. Try also to change the port and restart node-red

I'm in host mode, and tried already 1981 port... I'm trying to rollback to 10.0.20

[Supergiovane]

Remember to always restart node-red after each change.

[SebDominguez]

I've restarted both the container and the host device

[SebDominguez]

I'm back in 10.0.20 with the exact same settings and all is working fine

I can even detect the sonos on the local network (with the 1.0.41 I had to use the fallback IP)

[SebDominguez]

Is there any tests I can do to see what could have change with 1.0.41 that may have broke my container?

[Supergiovane]

Hi i don't know how your container works, so i cannot help you, but 1.0.41 should work, because the sonos engine is the same. I suggest you to run a new docker from fresh and install the 1.0.41, to see if it works. I strongly discourage using docker, because you really doesn't have any good control on the docker settings, node-red setting file in docker, etc.. Instead, you should use Virtual machine.

[SebDominguez]

Yeah VM should be better for compatibility purposes but the host that I'm using is resource limited so VM will be a bit wasteful...

I'm making a container from scratch and let you know how this is going