Sonos Error at startup

AvatarED007

Re: MMM-Sonos - Display what is currently playing on your Sonos network

When I start the MagicMirror, then your Sonos module creates the following Error:

[10:19:19.329] [ERROR]  [Error: ENOENT: no such file or directory, open '/home/pi/MagicMirror/modules/MMM-MyWastePickup/schedule_custom.csv'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/home/pi/MagicMirror/modules/MMM-MyWastePickup/schedule_custom.csv'
}
[10:19:19.335] [LOG]    MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
[10:19:19.336] [LOG]    If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
[10:19:19.458] [ERROR]  Failed to get groups: Request failed with status code 503. Retrying in 1 seconds ...
Stopped all listeners to Sonos devices
[10:19:20.688] [ERROR]  Failed to get groups: Request failed with status code 405. Retrying in 4 seconds ...
Stopped all listeners to Sonos devices

BR

sdetweil

@AvatarED007 said in Sonos Error at startup:

/home/pi/MagicMirror/modules/MMM-MyWastePickup/schedule_custom.csv’

I don’t think this is Sonos module,

looks like MMM-MyWastePickup is missing its schedule file

AvatarED007

@sdetweil

No this line you can forgot.

This is the Error an below lines
[10:19:19.458] [ERROR] Failed to get groups: Request failed with status code 503. Retrying in 1 seconds …
Stopped all listeners to Sonos devices

sdetweil

@AvatarED007 didn’t see that!..

A 503 Service Unavailable Error is an HTTP response status code indicating that a server is temporarily unable to handle the request. This may be due to the server being overloaded or down for maintenance

tbouron

@AvatarED007 Do you have more logs after what you shared? Did the module managed to connect to at least one Sonos device?

FYI, error 503 and 405 suggest that the module is trying to discover a device on your network and get the groups, but fails at doing so. There are quite a lot possibilities why this can happen:

Is your mirror on the same network as your Sonos devices?
Are your Sonos devices on and connected?
Are your Sonos devices up to date?

AvatarED007

@tbouron thanks for your feedback.

All the Sonos devices are online and the MagicMirror ison the same network.

[14:13:03.186] [LOG]    Zones have changed. Rediscovering all groups ...
[14:13:03.799] [ERROR]  (node:18039) UnhandledPromiseRejectionWarning: Error: Request failed with status code 405
    at createError (/home/pi/MagicMirror/modules/MMM-Sonos/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/home/pi/MagicMirror/modules/MMM-Sonos/node_modules/axios/lib/core/settle.js:17:12)
    at IncomingMessage.handleStreamEnd (/home/pi/MagicMirror/modules/MMM-Sonos/node_modules/axios/lib/adapters/http.js:237:11)
    at IncomingMessage.emit (events.js:205:15)
    at endReadableNT (_stream_readable.js:1154:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:9)
[14:13:03.804] [ERROR]  (node:18039) UnhandledPromiseRejectionWarning: Error: Request failed with status code 405
    at createError (/home/pi/MagicMirror/modules/MMM-Sonos/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/home/pi/MagicMirror/modules/MMM-Sonos/node_modules/axios/lib/core/settle.js:17:12)
    at IncomingMessage.handleStreamEnd (/home/pi/MagicMirror/modules/MMM-Sonos/node_modules/axios/lib/adapters/http.js:237:11)
    at IncomingMessage.emit (events.js:205:15)
    at endReadableNT (_stream_readable.js:1154:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:9)
[14:13:03.808] [ERROR]  (node:18039) 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(). (rejection id: 2)
[14:13:03.811] [ERROR]  (node:18039) 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(). (rejection id: 2)
[14:13:03.813] [ERROR]  (node:18039) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[14:13:03.819] [ERROR]  (node:18039) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[14:13:04.723] [ERROR]  (node:18039) UnhandledPromiseRejectionWarning: Error: Request failed with status code 405
    at createError (/home/pi/MagicMirror/modules/MMM-Sonos/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/home/pi/MagicMirror/modules/MMM-Sonos/node_modules/axios/lib/core/settle.js:17:12)
    at IncomingMessage.handleStreamEnd (/home/pi/MagicMirror/modules/MMM-Sonos/node_modules/axios/lib/adapters/http.js:237:11)
    at IncomingMessage.emit (events.js:205:15)
    at endReadableNT (_stream_readable.js:1154:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:9)
[14:13:04.724] [ERROR]  (node:18039) UnhandledPromiseRejectionWarning: Error: Request failed with status code 405
    at createError (/home/pi/MagicMirror/modules/MMM-Sonos/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/home/pi/MagicMirror/modules/MMM-Sonos/node_modules/axios/lib/core/settle.js:17:12)
    at IncomingMessage.handleStreamEnd (/home/pi/MagicMirror/modules/MMM-Sonos/node_modules/axios/lib/adapters/http.js:237:11)
    at IncomingMessage.emit (events.js:205:15)
    at endReadableNT (_stream_readable.js:1154:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:9)
[14:13:04.726] [ERROR]  (node:18039) 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(). (rejection id: 7)
[14:13:04.728] [ERROR]  (node:18039) 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(). (rejection id: 7)
^C[14:13:21.111] [LOG]    Shutting down server...

tbouron

@AvatarED007 Hum, it doesn’t make any sense. The discover should retry even if there is an error, something is wrong here.

Can post the entire log file please? Also, are you sure all your sonos devices are up to date?

AvatarED007

@tbouron

I do not have more log. At startup no errors. Yes I have all on the latest version 10.6.1

tbouron

@AvatarED007 If there is no error at start up, that means the module is able to fetch the groups fine. But based on the latest logs you shared, it fails to fetch again the groups when the change, which would indicate that somehow the module (hence the mirror) loose the connection to the speakers later on. Maybe your mirror has a flaky connection?

Unfortunately, I cannot reproduce this so it’s going to be impossible to assist further