You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I get on start server/ npm run-script dev below error. On client no rooms and an favourites and libraries are visible (500: Cannot read property 'browse' of null)
I am using only first generation of Sonos devices: Version 11.2.4
(node:28389) UnhandledPromiseRejectionWarning: Error: Not A Sonos Device
at new MusicLibrary (/data/home/.../sonos-web/server/src/sonos/MusicLibrary.js:14:30)
at /data/home/.../sonos-web/server/src/sonos/SonosNetwork.js:49:29
at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:28389) 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: 1)
(node:28389) [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.
The text was updated successfully, but these errors were encountered:
Hi,
I get on start server/ npm run-script dev below error. On client no rooms and an favourites and libraries are visible (500: Cannot read property 'browse' of null)
I am using only first generation of Sonos devices: Version 11.2.4
(node:28389) UnhandledPromiseRejectionWarning: Error: Not A Sonos Device
at new MusicLibrary (/data/home/.../sonos-web/server/src/sonos/MusicLibrary.js:14:30)
at /data/home/.../sonos-web/server/src/sonos/SonosNetwork.js:49:29
at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:28389) 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: 1)(node:28389) [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.
The text was updated successfully, but these errors were encountered: