Has to be the most useless error message ever written. Sonos system is now unusable and Sonos don’t seem to care.
This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.
Every time I see that error I get the feeling it was used as a placeholder in library code and was intended to be replaced with a real message when the library code was used.
As a long retired coder I have to admit I was never brave enough to submit something so poorly done for a team review, much less try to check it into the main project repository.
Sonos is aware of this and are working to make it more meaningful. Checkout the Trello Board at the link below that shows this issue and more of what’s being investigated.
+24The times I have debugged this, it resolves to an error 500 from their cloud. Http error 500 is “internal server error” which is no more useful than “something went wrong”.
As a coder this particular error most often means “the code crashed” on the server, and there’s nothing user actionable to fix that: the developer has to dig through telemetry to figure that out.
+18I am getting that error fewer times now. When I did get it most of the time the requested operation completed in spite of the Something Went Wrong error.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.