No Sonos player named

[advanceddigital]

Hi,

I'm doing some testing with the script but it's telling me that "No Sonos player named ... Players names are SoCo (IP address)". I have a zone named Desk and if I changed to SoCo it obviously doesn't work.

Any ideas?

Thank you,

Sebastian

[EliSchleifer]

Hi,

Sorry I missed this issue from a while back. Basically discovery is failing. If you are running this from inside docker make sure to use --network host so it will have access to the UDP subnet for discovery.

If that doesn't work you can hardcode the IP of the relevant Sonos Zone. For example in this case 'Desk' create a file Desk_ip.txt in the same folder as the script and put the IP address of Desk zone in the first line of the file

[advanceddigital]

Hi Eli, No worries and thank you for getting back, it was a misconfiguration in our end and it got fixed. Now, I’m facing an issue with the new controller version (10.1) and any parameter that has something to do with a room acting as a “coordinator”. The script failed and it don’t see it how to overcome it. I’m working on it but any help is highly appreciated. Thanks! Sebastian Mejia [Advanced Digital Systems]<http://www.thearcehouse.com/> Text Support: 551-404-5056 | Email Support: [email protected]<mailto:[email protected]> www.thearcehouse.com<http://www.thearcehouse.com/> | www.talk2josh.ai<http://www.talk2josh.ai/> [Facebook - Black Circle]<https://www.facebook.com/advanceddigitalsystems/> [LinkedIn - Black Circle] <https://www.linkedin.com/company-beta/9334036/> [https://static.wixstatic.com/media/e1aa082f7c0747168d9cf43e77046142.png/v1/fill/w_31,h_31,al_c,usm_0.66_1.00_0.01/e1aa082f7c0747168d9cf43e77046142.png] <https://www.instagram.com/advanceddigitalsystemsarce/> [https://static.wixstatic.com/media/d54427_95a188f10ca3421a9fa4c7a16025122f~mv2.png/v1/fill/w_115,h_34,al_c,usm_0.66_1.00_0.01/d54427_95a188f10ca3421a9fa4c7a16025122f~mv2.png] <http://www.thearcehouse.com/> [cid:[email protected]] <https://www.talk2josh.ai/> From: Eli Schleifer <[email protected]> Sent: Wednesday, April 24, 2019 4:38 PM To: EliSchleifer/sonos-doorbell <[email protected]> Cc: Sebastian Mejia <[email protected]>; Author <[email protected]> Subject: Re: [EliSchleifer/sonos-doorbell] No Sonos player named (#1) Hi, Sorry I missed this issue from a while back. Basically discovery is failing. If you are running this from inside docker make sure to use --network host so it will have access to the UDP subnet for discovery. If that doesn't work you can hardcode the IP of the relevant Sonos Zone. For example in this case 'Desk' create a file Desk_ip.txt in the same folder as the script and put the IP address of Desk zone in the first line of the file — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#1 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AEKIOAVRKFTG6R27H4HR7H3PSDAKPANCNFSM4FMAQIAA>.

[EliSchleifer]

I am seeing the same issue myself. I was going to try to rebuild my sonos setup at home and see what is happening.

[EliSchleifer]

Looks like Sonos broke discovery. and pip version of SoCo hasn't been upgraded yet.
SoCo/SoCo#660.

Working on local patch