Ryan Ellis
Ryan Ellis
@bencevans Is this a sonos-cli issue, or something in the way I have node setup?
@bencevans Not all the devices are in a single group, but rather 4 of 5 different groups. (I've been using this in my office)
All speakers are now on 9.2 (build 46357250), but CLI has been broken for me from 9.1 yeah.
Same issue still: DEBUG=sonos* sonos list-zones sonos:main Sonos.GetAllGroups() +0ms sonos:service Service._request("GetZoneGroupState" {}) +0ms (node:6227) UnhandledPromiseRejectionWarning: StatusCodeError: 500 - "s:ClientUPnPError501" at new StatusCodeError (/usr/local/lib/node_modules/sonos-cli/node_modules/request-promise-core/lib/errors.js:32:15) at Request.plumbing.callback (/usr/local/lib/node_modules/sonos-cli/node_modules/request-promise-core/lib/plumbing.js:104:33) at Request.RP$callback [as _callback]...
@bencevans Any new luck here?
I believe about 16 Zones. It's an office.
@bencevans [email protected] ├── [email protected] ├── [email protected] └── [email protected] Appears to be the same
@bencevans Is there anything else you can think of for me to check on my side as to why this still isn't working for me?
@bencevans I can see Wireshark recording an HTTP/1.1 500 Internal Server Error\r\n, as well as a UPnP: Error 501 around urn:schemas-upnp-org:control-1-0 in the response. I'll bribe someone on our NW...