SONOS "" not found

[aleks-83]

Hi,

when i try to control my sonos speakers with the adapter i get the answer
SONOS "" not found
Doesnt matter with command I try.

2019-10-31 05:08:22.841 - info: sonos.0 (8376) try to control id sonos.0.root.10_0_0_50.play with {"val":true,"ack":false,"ts":1572494902839,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1571502439311}
2019-10-31 05:08:22.841 - warn: sonos.0 (8376) SONOS "" not found

Win 10
JS 2.0.38
Sonos 2.0.0
Web 2.4.8 (if necessary)

[Apollon77]

Starte mal Adapter neu. Der Fehler kommt wenn er etwas von einem Sonos bekommt oder senden soll oder so den Er nicht kennt/discovern kann.
Letzens gab es den Bug das in solchen Fällen eine exception geflogen ist und der Adapter gecrasht ist ... jetzt kommt das quasi als Fehlerbehandlung.

Grund: für mich unbekannt, ich hab aber auch keine Sonos

[Atomschorsch]

Check your speaker IPs. I had the same error in the log, and after deleting and reinstalling the SONOS adapter, I found out that my speakers have been found at another IP address. Maybe I should use static IP addresses for the speakers.

[aleks-83]

All my smart home devices are setup with static IPs in my router.
But thanks for the hint, anyway.
Maybe it's usefull for others.

[Jey-Cee]

Saw this issue (a lot messages) after installing the adapter with js-controller 3.

`

sonos.0	2020-04-09 08:48:17.525	warn	(16835) SONOS "" not found
sonos.0	2020-04-09 08:48:17.525	info	(16835) try to control id sonos.0.root.192_168_0_21.group_muted with {"val":false,"ack":false,"ts":1586422097459,"q":0,"from":"system.adapter.sonos.0","user":"system.user.admin","lc":1586422097404}

`

[x1n3f]

Hello,
i had the same issue. Maybe it will help:
I have configured 3 Sonos loudspeakers in Sonos adapter at first. I had "SONOS "" not found" in the logs.

When I have increased the log level on SONOS adapter, everything was ok (connection, etc.)

I have all 3 loudspeakers grouped with the Sonos app. After I have configured only one of the speakers in IOBroker, then everything worked with ttx.

[Raabensohn]

Hey, same problem here...
any solutions yet?
restart, log level does not do the trick... :-/

runs on Docker

[Chris-We]

having the same issue.

[Chris-We]

So I found out that the error seems to have something to to with the firewall of my Synology Diskstation I'm running iobroker on as a docker container.
Unfortunately It seems to be not sufficient to open the ports mentioned at the Sonos support page: https://support.sonos.com/s/article/688?language=de

which ports is the adapter using?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions.
Dieses Problem wurde automatisch als veraltet markiert, da es in letzter Zeit keine Aktivitäten gab. Es wird geschlossen, wenn nicht innerhalb der nächsten 7 Tage weitere Aktivitäten stattfinden. Bitte überprüft, ob das Problem auch in der aktuellsten Version des Adapters noch relevant ist, und teilt uns dies mit. Überprüft auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind bzw. aktualisiert diese. Vielen Dank für Eure Unterstützung.

[stale]

This issue has been automatically closed because of inactivity. Please open a new issue if still relevant and make sure to include all relevant details, logs and reproduction steps. Thank you for your contributions.
Dieses Problem wurde aufgrund von Inaktivität automatisch geschlossen. Bitte öffnet ein neues Issue, falls dies noch relevant ist und stellt sicher das alle relevanten Details, Logs und Reproduktionsschritte enthalten sind. Vielen Dank für Eure Unterstützung.