App hangs on startup with "Searching for your Sonos System .."

[alexander-nitsche]

Current behaviour

I installed Debian Bullseye from scratch these days and today added the current stable version of the unofficial sonos controller to the system. I used the app already successfully with Debian Buster and Debian Stretch although not in this version. Now, when starting the app for the first time, it shows the usual "Searching for your Sonos System .." hint, but this hint does not disappear anymore.

This is the debug console output: sonos_controller_0_2_9.log

Expected behaviour

The hint "Searching for your Sonos System .." should disappear on application startup and the available sonos devices should be listed.

Environment

OS: Debian Bullseye
App: Unofficial Sonos Controller 0.2.9

[christophe-lejeune]

I have personally experienced similar problems with the 0.2.9 version (and 0.3.0 alpha's). Downgrading to 0.2.8 solved the problem for me.

[pascalopitz]

I have personally experienced similar problems with the 0.2.9 version (and 0.3.0 alpha's). Downgrading to 0.2.8 solved the problem for me.

How are you installing the app?

[christophe-lejeune]

I am personally happy with the app and with the performance... Initially, my message intended to help @alexander-nitsche (and other people facing similar issues). Thus, my message was not a help request in itself. In fact, my motivation was even the opposite: by posting here, I was hoping that I could share a (small) part of the work load, which can help @pascalopitz to concentrate on something else (as the very promising 0.3.0, for instance).

However, here are my settings, for information and documentation. I have two different computers. A laptop (Ubuntu 16.04) and a PC (Debian Bullseye). On both computers, I download the .deb package and install it with dpkg -i. The only difference is that, on Ubuntu, the regular user can perform this installation - thanks to sudo - while this command requires to log as root under Debian (su). After installation, the same kind of behavior was observed, that motivates downgrading to 0.2.8.

My 2 cents

[darkship]

did you check your https://github.com/pascalopitz/unoffical-sonos-controller-for-linux#firewall-settings?

[pini-gh]

I experience similar issue on my Librem 14 laptop running PureOS byzantium amd64 (almost Debian bullseye).

What's weird is that it works fine on my Librem 5 phone running PureOS byzantium arm64 connected to the very same home network as me L14.

Any idea about how to diagnose this issue?

EDIT: This might be related to my laptop settings. I've ran minissdpd on several of my PCs, and my L14 is the only one not seeing anything. It has no firewall configured, to my knowledge, but there must be something blocking the way.

EDIT again: It appears my L14 had firewalld running. After adding a new firewalld service with the requested ports, s-c-u behaved.

[DasJott]

I am using Noson mostly and that does simply find the sonos system.
I really don't know, why this one needs extra firewall config...

I am not using any firewall btw. and this app does no work. Installed as Snap on Solus.

[Stewori]

One more thing to try (worked for me): Some routers emit multiple wifis, typically one 5ghz and one 2ghz. I have to connect to the same wifi as the sonos happens to be in, otherwise the system cannot find it. I know it's odd behavior of the router, but for some reason only devices in the same wifi are visible to each other. Perhaps this can be solved in the router config; just saying it is a possible cause for this issue.