search

jishi / node-sonos-http-api

An HTTP API bridge for Sonos easing automation. Hostable on any node.js capable device, like a raspberry pi or similar.
http://jishi.github.io/node-sonos-http-api/
MIT License
1.84k stars 463 forks source link

No system has yet been discovered. Please see ... #744

Open Snahz opened 4 years ago

Snahz commented 4 years ago

I had installed the api 2017 for a local XAMPP webserver. It worked until the end of 2019. I reinstalled node.js and node.js-sonos-api. This did not solve the problem. The URL http://192.168.168.4:5005/ shows me the familiar Sonos API page. When I run any command, I get the error message "No system has yet been discovered. Please see https://github.com/jishi/node-sonos-http-api/issues/77". I tried hints from that URL, but nothing helped. What can I do to get Sonos voice back up and running, what information do you need? Thank you.

Server is Windows 7 Pro All devices are in the same subnet with static ip (via DHCP) Server is wired to the LAN some Sonos as well, other with Wifi Router and Wifi access point are devices from Lancom (1781EF+, 452agn dual wireless)

jishi commented 4 years ago

Discovery relies in Multicast/broadcast so something is blocking that between your server and all of the Sonos players. It could be anything, really, if you have the possibility to wire the server directly into one of the Sonos players (that isn't connected via Wifi, only cable or SonosNet), as a test.

If wiring it directly works, then it is something outside the server. If it still doesn't work, it is some setting or driver on the server blocking it.