Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No Rooms and Music visible #70

Open
parduhn opened this issue Jan 30, 2021 · 0 comments
Open

No Rooms and Music visible #70

parduhn opened this issue Jan 30, 2021 · 0 comments

Comments

@parduhn
Copy link

parduhn commented Jan 30, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant