Amazon problems again
Answered
starting this week I finding amazon would play 1 song, than tell me remote service error, internal server error. I logged out, rebooted, and when I try to log back in the tab just says something about authenticating but the page just does nothing.
-
I don't know where you got the idea that Bluesound is the only streamer "licensed" to work with Amazon. Plenty of others do, including the Wiim products.
Seems clear that the problem is, and always has been, in the authorization process. As I mentioned earlier, when logging back into Amazon after rebooting, I get directed to a version of the BlueOS control panel. Clicking on "configure music services" takes me to a list of services to choose from. Amazon is not on that list.
Even though the authorization process does not seem to be completing, I can still open Amazon Music from the BlueOS, see content, and sometimes even play a song or two before it stops and I get the "remote server error - internal server error" message.
And surprisingly, sometimes after getting that message I can simply try clicking on a song or playlist a few minutes later and once again hear a song or two before the cycle begins again.
For whatever reason, the Node's authorization as a valid device by Amazon seems to be intermittent. Very strange, but clearly not a problem of "an Amazon server beiing down", regardless of what Bluesound customer service tells you/us.
-1 -
Correction to my last post, while streaming from Amazon music to my Bluesound Node N130 via airplay using Amazon music app as control it randomly drops out of the Amazon music app and stops streaming, this doesn’t happen Bluetooth streaming to Amazon echo device, so is this just an issue with Bluesound/NAD devices ?
0 -
When logging out of Amazon music in BluOS app I don’t get the issue of it being missing from the list when adding a service, it’s there on my list and I can log back in, sometimes it will then stream a random number of tracks sometimes none before getting the Remote service error message. I stand corrected on my thought that only Bluesound/NAD were licensed to stream Amazon music because WIIM also can and maybe there are others also ? Certainly when I purchased my N130 Node when it was newly released here in the U.K. Bluesound/NAD were the only streamers I could find that could stream Amazon Music. Whatever the current situation has left me ditching my thoughts for purchasing the new Bluesound node N132 and looking at alternatives.
0 -
Top be clear, the BlueOS control panel I am/was referring to has a different form factor from the standard BlueOS "homepage". It only appears after the brief "Oops, no service configuration defined for Amazon Music" disappears, which in turn is after clicking "accept" on the Amazon login screen that comes up after starting the login process in BlueOS.
Clicking on "configure music services" on this version of the control panel takes you to a list of available services. It is here that Amazon is missing from the list. But all the others are there.
If I open the BlueOS directly, business as usual, the list of available music services does indeed include Amazon Music. And even though there is clearly some sort of authorization/validation breakdown going on, I can always open Amazon Music, see My Music content, and often even get a song or two to play before it craps out.
Just trying to keep my experience clear, in case anyone from Bluesound is actually interested.
By the way, there are threads popping up on at least several of the popular music/audio sites complaining about the same problem. I would expect to see more over the coming days if Bluesound can't get it resolved. They can blame Amazon all they want, but at the end of the day the simple fact is that for many users, the Node no longer meets the promise made when it was sold.
I guess the argument can be made by Bluesound that my Node 2i is almost four years old and has become obsolete, but trying to normalize the lifespan of a $500 streamer to be only 4 years would be a terrible message to put out into the marketplace. On the other hand, I guess that describes the smartphone market!
But if that indeed becomes the case, all the more reason to spend less than half on a Wiim streamer., which is what I guess is the only alternative if this doesn't get resolved within the next few days.
0 -
Yes, Bluesound and Amazon should be curious about the symptoms of this disease if they are seeking to make a diagnosis. Much data can be found in this thread. FWIW, our Amazon password has not changed in years.
0 -
Yes, both Amazon and Bluesound ought to be motivated. Ought to be.
0 -
Typing https://192.168.1.8 into Microsoft Edge browser address bar shows my Node 2i control panel, exactly like the one shown when circle is spinning. Anyone with access to the local network, can display the control panel.
0 -
Yes, entering the IP address of the your Node will take you to the original version of the control panel/user interface.
What seems so odd to me is that when accessing the list of available music services from that page , Amazon does not appear on the list.. All of the others are there, as normal.
But if I open the BluOS app the "usual" way, in either Android or W10, Amazon does appear on the list of available services.
0 -
I have also been suffering this issue since Sunday last. Some Amazon Music playlists won't open or play, others can be viewed but it seems a lottery as to whether individual tracks will play or return the server error message. Sometimes if I return to a track or playlist that wouldn't open a short while later, I can then open or play it, but another track I has played earlier now fails to respond.
I have complained about this on the Amazon UK customer forum, and referred them to this thread. As is usual with Amazon, the only response I got was a request from their rep to talk to a bot.
This can't be that hard for a Bluesound or Amazon tech to track down with a debugger to work out when the error message is generated and where it is coming from, surely?0 -
Having posted the above, I have just seen this response from Amazon to my and other complaints to them:
Hi everyone!
I've reported this to our technical team and they're working on taking care of it.
These situations are rare, and our goal is to help resolve any problems you encounter as quickly as possible.
I'll write back as soon as a resolution is available.
We apologize for any inconvenience caused.
0 -
Anyone thinking of WiiM… they also have the same issues with Amazon Music so little point jumping ship.
0 -
Yes there is a discrepancy with what Music streaming services the BluOS app sees and what the native Node streaming device sees when connecting to the streamers IP via a web browser, but without knowing the access route BluOS uses to retrieve streaming data don’t know if this is relevant to the current problem and has now been reported that WIIM streamers are also now having the same issue it would suggest more likely an Amazon issue. If it is an Amazon technical issue I find it difficult to understand why it hasn’t been fixed by now. With 40+ years working in IT (IBM mainframe not networking) experience tells me most IT problems are change related. So Amazon what have you changed ?
0 -
From info on another forum (Steve Hoffman), users of Wiim can stream Amazon HD using some 'connect' feature of the Wiim system, like Tidal Connect works with the Node. ??
0 -
Regarding Wiim streamers; I have two of them. Both are working just fine with Amazon Music. I sent emails to two acquaintances who use Wiim streamers and Amazon Music. They aren't having any problems either, nor is my brother, who also has a Wiim with Amazon Music.
I could find no threads on the Web referring to Wiim users having the same problem as we are with the Node and Amazon Music. Seppi, pls provide a link. I would need to see some evidence before concluding that Wiim users are experiencing the same type of wide-spread problem that Node users are having.
Of course, if they are, then the problem clearly lies at Amazon. But I'm not yet convinced of that.
On a related note; I wonder if all Node users are experiencing the issue, or only a subset of them.
As regards Amazon Connect; this is an Amazon Music function by which you can control your streamer using the Amazon Music app, as opposed to the streamer's app Tidal offers the same capability, and this is standard operating procedure for Spotify.
Wiim devices are compatible with Amazon Connect, Tidal Connect and Spotify Connect. so they can be used either way; that is, via the Wiim app or via the streaming service's app.
If I remember correctly, Spotify Connect is the only means by which the Node can be used with Spotify.
0 -
AWS is one of Amazon's best revenue generators, with $90 billion dollars in 2023. The money they make from streaming companies has got to be miniscule, compared to total revenue. Probably not a high priority to fix things. Notice that Amazon Music on their echo speakers and on pcs with their App seems to be working fine.
0 -
Steve, post number 43 by WiiM support
https://forum.wiimhome.com/threads/wiim-ultra-firmware-v5-2-627135-update-aug-23-2024.4530/page-3
0 -
Indeed, it appears Bluesound and WiiM are in a race.
1 -
Lee, I don't know what you mean by "the money they make from streaming companies'?
But Amazon Music revenues were $5B in 2023, and growing rapidly. Small compared to AWS, but still quite significant.
I would think, however, that the portion of that revenue attributable to Bluesound users is very, very, very small. Same for other dedicated streaming devices. The vast majority of their customers use smartphones, tablets, personal computers, etc...not dedicated streamers.
0 -
Thankfully my Wiim devices, and those of my acquaintances, are not being affected. Working just fine with Amazon Music. In fact, last night I pulled the Node out of my main system and replaced it with the Wiim Pro Plus from my workshop system. It's nice to have access to my music again.
And of course even if the issue does spread to my Wiim devices, I can simply use Amazon Connect and run them that way. Unfortunately, this is not an option with my Node.
EDIT: THE LINK PROVIDED BY SEPPI IS DATED NOVEMBER 22, SO IS NOT PERTINENT. THERE IS ABSOLUTELY NO INDICATION THAT WIIM USERS ARE HAVING THE SAME TROUBLE AS NODE.USERS.
EDIT AGAIN: MY MISTAKE. THREAD IS INDEED CURRENT. ODD THAT THE ONLY MENTION OF IT IS BURIED IN A THREAD ABOUT A RECENT UPDATE.
0 -
On the contrary, the link provided by Seppi includes a post by WiiM support admin, dated yesterday, confirming that they are currently having issues with Amazon Music.
1 -
I am suspicious that this might have something to do with the individual ID (profiles) that they forced upon users recently as this now wants to know who is listening on the account but I don't think this is a feature via the blusound app? I only thought about this because it's something that had suddenly popped up on my Amazon music app. ???
0 -
All of the posts in the WiiM thread, across all three pages, were made in the last week.
0 -
Hello All
Just to let you know we are still monitoring the situation with Amazon Music and third-party devices with deep integration. In speaking with Amazon, they continue to monitor the situation and hope to resolve the matter as quickly as possible.
We do however ask you all to maintain the subject matter here to updates on Amazon restoring service. Thank you for your patience and understanding.
If unsure, please feel free to review here; Bluesound Community Terms0 -
FWIW, I received and set up my Node one month ago. Amazon Music has not asked us about who is listening. The identities of persons in my listening room is none of their business. Amazon knows when its music is streaming on a device, and will not allow streaming on two devices.
0 -
Amazon allows 5 profiles per account, this is what I mean for example on the android app it shows the profiles in a list and which one is using it, if this is a new requirement in not sure that the blusound app allows for it
0 -
I guess the only thing to do is put the Node back in its box for now and check back here once in a while to see if the problem has been fixed. I could find nowhere on the Amazon site to track the status of the issue.
Glad I have an alternative in the meanwhile. Good luck everybody!
-1 -
Interesting to note that a user comment on the WIIM forum states that since WIIM reported to previous firmware it has fixed the problem, so is it the latest Bluesound firmware update which I only installed recently on my node N130 that is the cause of the problem ?
0 -
My last post should say that since WIIM reinstated the previous firmware it has fixed the problem.
0 -
My Node was first set up one month ago, including the 'latest' software. Does my Node automatically, quietly, update its software periodically?
0 -
I have been looking through the WIIM forum and haven’t seen a comment indicating WIIM are having exactly the same problem with Amazon music that us Bluesound/NAD users are having.
0
Please sign in to leave a comment.
Comments
108 comments