Amazon Music authentication issues?

Beantwortet

Kommentare

74 Kommentare

  • Dan H

    Lee, It actually did NOT happen to me when I left my first post yesterday; I was just adding to the conversation as I happened to be reading email when I got notified of the new posts.  You raise an excellent point about the Bluesound logs.  

    ==> Bluesound Company Folks  -- can someone please let us know you're still reading, and that if a bunch of us send logs, you'll commit resources to looking through them to get some clarity on this issue?

    Lee, Don, Mark, others in our boat -- can we commit to at least commenting here with date, time, & time zone of when it happens to us? At the very least we can be gathering evidence on our own to draw our own conclusions, regardless of whether Bluesound is still listening (pun intended :-).

    0
  • Lee Knoll

    5/21/22 11:21AM PDT Authentication Error

    Another one at 14:03 PDT

     

    0
  • Todd Wathey

    The sign out - sign in did help when I tried. I'll see if it happens again. Interestingly for me, I could not search amazon, but was still able to play top albums or songs from the "charts" section. I'm play via the app on android connected to a NAD M10. It seems like all hell has broken loose since the last update.

    0
  • Tim Strempfer

    Happened to me for the second time today at approximately 2pm PST.

    0
  • mark wales

    I had the issue at 11'ish and 2'ish too. And was further annoyed as after i rebooted the node it wasn't being detected by either of my bluos controller apps, in the end had to delete one app and it was finally detected. Bluesound support have close my issue saying it is resolved but get this - they also say it's unresolved but they don't want to leave tickets open while they investigate. Umm smacks of managing the case numbers rather than actively working on the issue. I hope i'm wrong but.....

     

    And for the record this morning the sign out sign in did not work. This afternoon I even tried the reboot while sign out but that was when it would not be found. It's finally working now.

    0
  • mark wales

    OK 3rd time today - about 4:20 pst the music stopped - same error.

    logged out of amazon music and alexa and it still gave the error but i did get it to work so a bit confusing

     

    0
  • Lee Knoll

    same error for me. 4:20PM PDT.

    Weekends seem to be the worst. More users on?

    0
  • mark wales

    OK will raise another ticket and ask them to use the common occurrence across uses - if they are not testing when whatever happens they will not replicate.

     

    0
  • André

    The same is happening here, in Brazil.

    0
  • mark wales

    OK raised a ticket and asked support to look at the log to get the specific times. If it's happening in Brazil then it suggests it's not a local west coast issue which was suggested before. BTW they are on holiday till Tuesday so nobody is in support until then. It may need everyone to raise support requests to elevate the priority in support or the development teams.

    0
  • Michael Persiano

    I have had this ongoing problem for at least a week or more.  I am having it occur using both my NAD M33 and BlueSound Powernode 2i.  I am able to play Radio Paradise, Sirius, and Spotify with no disruptions. If this is persistent with Amazon, I am considering dropping Amazon and implementing Tidal. Is anyone considering taking the same path? 

    0
  • Michael Persiano

    I did the reboot as described by BluSound...the message has not disappeared.  My tolerance is waning quickly.  Soon...Tidal.

    0
  • mark wales

    If i moved to tidal then the node 2i goes away - the only reason was for amazon so an expensive streamer with a poor dac and poor integration with amazon.

     

    0
  • Lee Knoll

    Mark. I bought 2 node 2i's specifically for Amazon Hi Res.

    I think it is Bluesound's responsibility to work with Amazon to get this fixed.

    I use the Node 2i coax digital output, so it uses my Marantz 8805 DAC, instead of the node 2i.

    If I end up going to Tidal or something else, I will use the Node 2is for a simultaneous stream to 2 rooms.

    Today, instead of using Bluesound, I am using Denon/Marantz HEOS to stream Amazon Music, to see if I get the same error.

    0
  • mark wales

    I just came in the from garden and noticed the music had stopped 2pm pst - not sure when but same error and was able to restart so i assume time had helped. I'm running my node 2i to an audio note dac while i search for a long term dac and the audio note will go back with my transport for cd's. I'm thinking MDHT tube dac. Tried the Topping D70st but not musical enough. I'm using coax too.

    0
  • Dan H

    Thanks, folks, for continuing the conversation.  Haven't heard anything here from any Bluesound reps in a number of days; I hope with the new week that changes.

    Lee - I agree with you that it's Bluesound's responsibility (and, frankly, in their best interest as a company) to work this out with Amazon.  Certainly they must have more contacts better positioned to solve it than we do.   At the very least, they could (a) have a more accurate error message; and (b) use the magic of buffering to download 2-3 songs at a time, and recover silently from minor connection issues (probably, some of (b) is already happening).

    I was not home much this weekend, but I experienced 2 outages:

    --2022-05-21, 11:29 AM pacific (looks like Lee, you did too).
    --2022-05-22, sometime between 7:30 and 08:31 AM pacific

    0
  • mark wales

    OK support have closed all my tickets again as resolved but unresolved saying tough - wait for development and they'll update us through the community. Whatever that is supposed to mean. I get the distinct impression this is of no interest to them to find a solution. And I see the problem still occurring but it does right itself if left for sufficient time. I hope enough people read the amazon review i left and check out this thread.

    0
  • Dan H

    @mark - how long do you have to wait for it to come back after you get the error message?  Do you click "No" to the message?

    All -- I had another outage yesterday:  

    2022-05-26, 03:46 PM Pacific

    Anyone else get that?

    0
  • Lee Knoll

    Dan

    I also had an outage around the same time. 

    0
  • mark wales

    Dan - I have no clue when the outages were - I've been busy on projects and in the house and yard so just using the music to burn in new cables. After clicking a couple of times either yes or no and coming out, then selecting Amazon music it seemed to work. On the times it has happened it's taken me probably at least 5 mins to get in trying various options including logging out and refreshing music in Amazon.

    0
  • Lee Knoll

    Another outage today 5/27/22 at 1:36PM PDT.

    I wait 5 minutes and launch the BLUOS, click NO and immediately select a song from my play queue and it starts streaming again. This procedure almost always works 

    0
  • Dan H

    Thanks, Lee & Mark.

    Similar for me: outage 2022-05-27, 01:31 PM Pacific.

    This time instead of rebooting, I did similar to you, Lee:

    1. click No to the dialog (shown at the top of this thread)

    2. Wait 5-10 minutes

    3. Select Amazon Music and play.

    ---

    Seems like there's some blip in the music stream from Amazon.  Not sure how to fix it. I just hope BlueSound and Amazon can work together to fix it (I dislike getting caught in the middle).

    0
  • Lee Knoll

    I phoned Bluesound today and received a callback from a Bluesound rep. She said it is an Amazon problem and they are trying to get ahold of someone at Amazon. Can you believe this? I reminded her that this has been going on for a month.

    I told her that since they have a contract with Amazon, they should have a direct point of contact. She said she would pass this along to the Product Manager. What a way to run a company.

    I also told her they should be informing users as to what is being done, and not leaving them in the dark. She said she would also pass this along to the Product Manager.

     

    0
  • mark wales

    Thanks Lee - I have a strong suspicion that that is a stock answer as people have only reported it on the bluos app and it's bluos error handling that not working, and as you said support have been investigating for a month now and handed it off to development. I'm sure support is fed up with us and would tell us if they'd actually found the issue and reported it back to Amazon. Thanks again for chasing Bluesound.

    0
  • Jonathan

    I installed a Node for a customer and they keep say it cuts out as well...everything else seems to be relatively stable thru BluOS so I don't thinks it is the Node.  As a side note I have a Node 2i at my home and use Deezer and its been flawless...definitely appears to be an Amazon issue....I'm in Alberta as an FYI...so I do fall into the western continental thing...,.

    0
  • mark wales

    Someone on audiogon had the same issue but hasn't seen it recently - they mistakenly thought it was streaming from more than one device but i explained we all see it at the same time and I can confirm the error is different if you try to stream from more than 1 device. On Monday an Audiolab 6000N arrives and I'll be transitioning and once I'm happy the Node 2i will be gone

    0
  • Tim Strempfer

    I'm thinking more and more this is an Amazon Music issue. I've been trying to stream Amazon Music to my Sonos instead to see what happens. Getting music stopping on Sonos as well. Only with the Amazon service.

    0
  • mark wales

    Thanks Tim - but Bluesound have the relationship with Amazon and should be able to replicate and work with Amazon to resolve or at least better adjust their error handling. Basically we have little pull with Amazon individually and they have the contract. If they can tell us the problem we can escalate with Amazon but really tough with an intermittent issue like this. What the error with sonos?

    0
  • Tim Strempfer

    The error was something along the lines of there being a problem with my Amazon subscription. And I needed to correct it.

    0
  • mark wales

    Thanks - previously we'd seen others using other devices with no issues. 

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.