Hello
I have been unable to make this module work and I think I have narrowed it down to a Sonos Boost in my system
Every time the boost is plugged in I get the following errors and the module displays nothing
0|mm | [10.06.2021 18:56.52.463] [ERROR]
0|mm | (node:31409) UnhandledPromiseRejectionWarning: Error: upnp: Request failed with status code 405///<HTML><HEAD><TITLE>Error 405</TITLE></HEAD><BODY><H1>Error 405</H1><P>Method Not Allowed</P></BODY></HTML>
0|mm | at /home/pi/MagicMirror/modules/MMM-Sonos/node_modules/sonos/lib/services/Service.js:90:25
0|mm | at runMicrotasks (<anonymous>)
0|mm | at processTicksAndRejections (internal/process/task_queues.js:97:5)
0|mm | [10.06.2021 18:56.52.464] [ERROR] (node:31409) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 9
)
My take is that an unrecognised command is sent to the boost and the error is not properly handled/ignored
This is the boost device object in my system, nothing seems to distinguish it from the speaker devices
Sonos {
host: '192.168.1.162',
port: 1400,
options: {
endpoints: {
transport: '/MediaRenderer/AVTransport/Control',
rendering: '/MediaRenderer/RenderingControl/Control',
device: '/DeviceProperties/Control'
},
spotify: { region: '3079' }
},
_events: [Object: null prototype] {
newListener: [AsyncFunction: implicitListen]
},
_eventsCount: 1
}
I will try to trace it down to the actual error but documenting here what I have found thus far
Hello
I have been unable to make this module work and I think I have narrowed it down to a Sonos Boost in my system
Every time the boost is plugged in I get the following errors and the module displays nothing
My take is that an unrecognised command is sent to the boost and the error is not properly handled/ignored
This is the boost device object in my system, nothing seems to distinguish it from the speaker devices
I will try to trace it down to the actual error but documenting here what I have found thus far