Amazon problems again
Beantwortet
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.
-
Offizieller Kommentar
UPDATED OFFICIAL COMMENT
Thank you for your patience. We continue to have a dialogue with Amazon about ongoing service interruptions with their deep integration API when accessing Amazon Music from third-party devices.
It appears in testing with our quality assurance team, here at Bluesound's offices in Toronto, that service is starting to be restored. We do hope this is a trend across the board.
No you should not have to log out and back in...
-
Hi Will
Unfortunately, you are not alone. We started receiving a number of reports from consumers here at The Support Crew about repeated service disruptions starting on Sunday August 25th. We have confirmed no changes have been made at the BluOS Development end since the disruption started and resetting your authentication by logging out and logging back in does little if anything to resolve the issue.
We are now speaking directly with Amazon to better understand what has changed to prevent third-party devices such as your BluOS Player from generating this error as we have heard reports of other devices (not just BluOS powered Players) not working either.
The Amazon Music App itself appears to not have this issue so you may want to temporarily consider Apple AirPlay or Bluetooth using the Amazon App from your phone, tablet, or AppleTV (AirPlay only) to prevent audio pauses but may not receive Hi-Res content this way.
Myself or someone else from Bluesound will make updates here as they become available.
We do apologise for the inconvenience.0 -
I submitted service request 429581 on Sunday August 25th. Received feedback today basically saying Bluesound is closing my service request as they can do nothing and are trying to contact Amazon. Says it is a problem with an AWS server Bluesound pulls data from. Duh. AWS has many servers.
I can stream Amazon Music Unlimited on Echo speakers, using Alexa commands. No problem.
I can stream Amazon Music Unlimited through a Roku Ultra to my TV. No problem.
I can use the Amazon Music App on my PCs. No Problem.
Why should people continue to buy your products, if you can't support them? If you can't support your users, your business model is severely flawed, in my opinion.
We went through a similar issue about 2 years ago. Took weeks to a month to resolve.
AMU users buy your products for Hi-res music. At least that is why I did.
I have written software all of my adult life. Retired for 20 years now. This can't be that hard to isolate and fix.
1 -
I appreciate the problem acknowledgement. That said, apparently all we know is that Amazon Music is basically not available to BluOs customers. Amazon Music is my streaming service and I certainly do not want to send music to my system using Bluetooth.
I know I am just whining but i can report something which could be useful. My personally curated Playlists in Amazon Music do not seem to have this problem. Instead, the problem happens when I search/browse. But the search/browse feature is WHY we use streaming services.
In my humble opinion, both Bluesound AND Amazon should be concerned since this could (will) cause exoduses. I hope you will accept my candor in the helpful sense it is offered. Tell Amazon that customers are considering abandoning their service in favor of something that works.
0 -
Tell them Pandora and Spotify are looking much better right now. ;)
0 -
Jim. All of my playlists are personally curated. I never search or browse in the BLUOS. I build all of my playlists in the Amazon Music app for use in BLUOS.
0 -
Thanks Lee. Yup, I just had a problem with an Amazon playlist. Amazon needs to own this.
0 -
This issue has been going on since Friday last week. And it’s getting progressively worse. I work in IT and service delivery, if I ran my service like this with such prolonged outage I will be out of a job! What’s BlueSound doing to address this issue. You really need to be a bit more clear on what’s going on with this issue and update your users on progress. With Repeat issues like these, I’m not convinced BlueOs and associated hw is the right choice for me TBH.
0 -
Spotify moved from AWS to the Google cloud 8 years ago. I wonder why. If Spotify only offered hi-res, I would drop Amazon Music Unlimited in a heartbeat.
I guess Bluesound has no leverage against the Goliath Amazon. Sad.
0 -
I don't do social media but some of you do. I hope someone throws Amazon Music under the bus publicly and sends them the link. If they wanted to, they could fix this problem quickly. A change was made on their end, and they should know this caused the problem.
0 -
Same problem here for past 3 days. I worked in IT for over 40 years before retiring (IBM) and if this is an Amazon server problem I can’t believe that they haven’t fixed it by now, surely they have backup servers they can switch to, it’s unbelievably ridiculous that a multi national company with many millions of customers could be so incompetent. If this goes on much longer Amazon music will be ditched by me.
0 -
Same problems here. Tidal the same price as Amazon hd these days, so I'll be off there very soon. I agree Bluesound should be working with Amazon on this, it's both of their problems surely.?!
1 -
It sounds like Bluesound did its homework and then reached out to Amazon. Amazon has chosen to not respond. Again I think that a social media campaign is what could capture their attention. We shouldn't be having this discussion on Bluesound Forum. We should be having it more publicly.
0 -
Have resorted to streaming to my Bluesound Node via Spotify free service, it plays fine but can certainly notice the drop in quality on a high end HIFI system. Does anyone have any experience of any audio quality improvements using Spotify Premium ? otherwise Tidal is looking likely for me.
0 -
Jim Christensen, You are right think I have been a bit harsh laying equal blame at Bluesound door. As far as I know Bluesound/NAD are the only company licensed for Amazon music and I would imagine that it is not free to them, so they must have a vested interest in getting this fixed with Amazon.
1 -
I don't know where the problem lies, but can report that the Bluesound response to my trouble ticket made two opposing claims;
1. The fault is with Amazon, but
2. Bluesound may consider fixing the problem in a future firmware release (or may not).
Infuriatingly, the response also suggested that I should use Bluetooth to stream Amazon as a work-around. Grrr. I bought a high-res streamer to stream high-res content.
They also suggested that I take a look at Bluesound's great new product lineup! As if I would consider another Node, based on this experience. On a related note, I am having no issues at all with Amazon Music via the Wiim streamers I am using in secondary systems.
By the way, how many of you changed your Amazon password in the past several months. Is the problem limited to those who've done so?
I changed mine 3-4 months ago, and had a few instances of the validation error, but thought the issue was resolved . Then, about 2 weeks ago the Node began stopping - sometimes after playing many songs, sometimes after just a few, sometimes after selecting a song or playlist but before actually starting to play - and giving me the "remote server error - internal server error" message. Now the error pops up much more often...but oddly, I can still sometimes play a song or two before it does.
I've also found that when I go through the log out - reboot - log back in routine, after entering my Amazon credentials in BlueOS I get sent to an Amazon screen asking if I approve authorization of my device. I click on "accept", and then go to either a) a spinning icon that spins forever, or b) a text screen with the message "Error. Oops, no service configuration defined for Amazon Music". This quickly disappears, and is replaced by this screen:
When I click on "Configure Music Services", Amazon is not on the list of available services.
I have no technical expertise in these matters, but to me this suggests a problem at the Bluesound end.
1 -
I called amazon, they said "there is nothing wrong with the amazon music service, nothing has changed, you need to reach out to bluesound" :( you can reach them at 1-888-280-4331
0 -
Steve
I got the same response on my Bluesound service request. I'm seeing the same thing you are.
I first received "internal server error" over a month ago. I logged out of Amazon and then logged back in. When clicking Allow BLUOS, Amazon brought up another window with a spinning circle. It never stopped spinning, so I closed the window and started streaming one of my playlists. It would play for hours and hours with no problem. Now as everyone has said the situation has devolved where it is no longer useable. On Sunday I pointed out in my Bluesound service request that when I clicked on the URL of the Amazon window with the spinning circle, Amazon displayed "OOPS -No Service Configuration Defined for Amazon." Amazon than displayed my Node 2i control panel. Could this have anything to do with the latest BLUOS July update? Seems like an interface Amazon/Bluesound software issue to me.
Just trying to help.
0 -
Lee -
The spinning icon, the "oops, no service configuration defined for Amazon" message and the control panel are not from Amazon. Note that the IP address for each of these pages is your Node's IP address. I would think that this means these links are from the BlueOS.
0 -
Amazon IT and Bluesound IT are pointing fingers at each other. This is standard IT procedure, I notice.
I do appreciate folks raising cane here. Rattling cages.
Something must be done. If they leave it up to us, we will fix the problem with our wallets. This ball is in their court and the clock is ticking.
1 -
If it is an Amazon problem, why aren't all Bluesound users experiencing the issue? I know of at least two other Bluesound Node users who use Amazon Music but are NOT having this problem.
0 -
I contacted Amazon and they told me they would refund my annual music subscription given the bad experience. I am off to Tidal to get up to speed and transfer what I can. Once that is done, I am canceling Amazon Music. Using Tidal also opens the door to other music streamers such as Cambridge Audio that do not integrate with Amazon.
1 -
Okay. Let's help them out. I use an iPhone to control Node. Do Android phones not have this problem?
0 -
Steve. Agree that the IP address is the Node's IP. but the rest of the URL shows code being redirected.
When uses click ALLOW after entering their Amazon credentials, Amazon is verifying the handshake between BLUOS and Amazon.
0 -
Interesting playing music on my echos using Alexa commands today. There have been two long pauses in the last hour. They usually never pause or dropout when I use them.
2 -
I cannot imagine how the device being used for "remote control" would have anything to do with the issue, but for what it's worth, I use an Android phone, a Windows PC and an iPhone at various times. Problem is same regardless.
As for re-direct; again, I have no expertise. But it seems highly unlikely that Amazon would be displaying the Node's Control Panel. In any case, I have no intention of dropping Amazon Music as the solution, since I've built a large number of playlists on their platform and since my Wiim streamers are having no issues. For me, a much betters solution will be to simply replace the Node with a Wiim.
I wonder if Bluesound will start including a notification in the product documentation and on selling sites that the Node may not work with Amazon Music? In the interests of honesty and fairness, it seems like they should do so...regardless of whose fault it is.
1 -
Same problem here. Two tickets, reboots, sign-out-ins, all the tricks and still doesn't work. I really like the node, but these bugs really bug me. BlueOS should take ownership as they advertised that Amazon Music worked with BlueOS. May need to switch to Wiim and sell the node.
1 -
I also changed my password about three weeks ago, it may be related.
I worked with amazon for two hours to troubleshoot, uninstalling, reinstalling, did not work.
On the phone with amazon tech support. They have a ticket opened today (8/28), details below. They are waiting to work with Bluesound on resolution. They claim issue is escalated in Amazon. They expect resolution in 5 to 7 business days (?!?)
Event Title: US: Streaming issues
Ticket ID: V1499635399
Status: Pending
Customer contacts : 89They did credit me for the month (I am on the monthly plan).
1 -
My streamer is a Bluesound node N130 and I can stream from Spotify using Spotify app control, can also airplay to node using Amazon music app as control, to me the problem is looking more like a BluOs app/Amazon interface problem because without using BluOS app as control streaming to the node works. Of cause current Spotify resolution offering isn’t HD audio neither is airplay from Amazon music. I use an external DAC and a recent side issue if there is a short period of not streaming anything the DAC loses it connection to the node, powering off on the DAC reconnects to the node. Suspect this could be related to either the latest firmware update to the node or BluOS app update ?
0 -
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
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
105 Kommentare