Amazon Echo name changed to some serial number

Plan

Premium

Country

Hungary

Device

Amazon Echo Dot 3gen

Operating System

Windows 10

 

My Question or Issue

Since yesterday when I request the available devices via API Reference, I receive this:

 

"id": "d0e0c8da-1a4b-4b72-b7ff-4f089fd41d92",
"is_active": true,
"is_private_session": false,
"is_restricted": false,
"name": "d0e0c8da-1a4b-4b72-b7ff-4f089fd41d92",
"type": "Speaker",
"volume_percent": 36

However when I open spotify app on my phone or the windows app on my computer, then the name is correct. (It should be "Echo Dot")

 I have tried to rename and device and deregister the device and reconfigure in the alexa app, but it did not help.

Child Item
Child Item
Child Item

Accepted answers

All comments

Just to let you know that I have the same problem(s) as you with the
incorrect name and non-appearance in Spotify.

Hi.
Sorry for bumping this thread, but we still haven't been able to come up with a solution or even a workaround for this situation.
We'd be really grateful for any kind of update... until very recently, we've been advising all of our clients to trust the Echo Dot/Spotify integration as a reliable option to use along with our product, but unfortunately this hasn't been the case anymore: we've been getting reports about this same behavior from various sources for some time now, which means that maybe this issue has been affecting a lot more people than just the ones that have been posting here.
Once again, thanks in advance.

I have the same problem on a 4th Gen Echo Dot!
While the third gen Echo Dots constantly change name with an ID instead of the real name of the device. From the Spotify app no problem.
It is urgent to solve these problems which in fact do not make echo dots usable.

Sorry for my english ...
any news???

Quick update: the issue seems to persist, and so far, we still haven't been able to find a way around it.

Again, I'm sorry for bumping the thread, but I see we've had a few more users here who are also experiencing the same inconvenience and it's safe to assume that they're also having trouble coming up with a workaround for this. 

 

Also, I think it's worth mentioning that we've recently made attempts to get some responses from Amazon's end, unfortunately to no avail at all. At the moment we are out of options, and we'd be thankful for any follow-up on this. 

Hello again, I thought it would be worth it to share some info we've collected regarding the 4th Generation Echo Dot not being retrieved by the API while trying to work around this issue and, who knows, this might actually help some of you who've been experiencing the same problems: as I've mentioned in a previous thread, this issue seems to stem strictly from the API, as we've noticed that the devices do seem to be available while trying to use Spotify Connect (be it through the web player, the Spotify app or even the desktop client). Thing is, after connecting to an Echo Dot through this method (Spotify Connect), there's a slight interval where it is possible to retrieve these devices through the API call (more specifically, the /v1/me/player/devices endpoint).

Paraphrasing something I've also mentioned in a previous thread: it's almost as if checking the user's available devices through the Spotify Connect sweep results in "enabling" the Echo Dot devices, and from then on (for a short period) they start showing up in the API request.

 

Knowing this, we are left with the problem that arises from the need to constantly "trigger" the Echo Dot devices to make them available. Still, as I've said, this might help with some insight concerning this particular issue.

With that said, we are still waiting for Spotify's input and/or some feedback regarding any temporary fix to this. Again, thanks in advance.

Same problem here. I observed this since months. Should be fixable since the Spotify web player knows the correct names.

I almost get the impression that Spotify doesn't want to solve the problem!

I contacted Spotify customer service about this and got this answer:

It's not a problem from Spotify.

Help for rectification:

Nothing👎

I'm really not sure if I should feel stupid or Spotify itself.

This constant asking for improvement is annoying

 

 

Hi everyone

 

I wanted to circle back and provide an update on this issue.

 

We acknowledge this problem and this is indeed something that needs fixing on our end. Unfortunately the solution is not straight forward, but we are working on it.

 

I'm hoping to return with good news soon. Thank you for your patience. 

Thanks for the update. it's nice to know you are on the case.

first of all I would like to say thank you for this very good news.

I'm already looking forward to everything working properly soon.

 

and I hope that the elimination of the problem does not take as long as the insight took.

 

 

again 4 weeks have passed.
again nothing happened.

will Spotify give us a Christmas present?

Same issue over here. Thought I was going a bit mad until I found this thread. I have fourth gens and they keep disappearing. When I get them to register again they have UUIDs for names.

I asked for a working API from Santa Claus.

Unfortunately, Spotify **bleep** that up.

 

Merry Christmas and thanks for nothing Spotify🙁

I have canceled my premium account on January 15th.

I'm not in the mood to be ripped off by Spotify any longer
And still to pay for it

Unfortunately, it doesn't seem very likely that this will bother them, either. We've also stopped recommending Spotify to our customers because of this and considering that we've gone so long without so much as a rough deadline indicates, at least to us, that they aren't really interested in keeping the few of us (paying) customers that actually make an effort to spot problems on their platforms and to report those to them, and neither are they interested in following through with fixing these problems once they've been reported.

they don't even write here anymore.
absolutely ridiculous 🤐

Same issue here, worked well for some time and fails since updating Home Assistant some time ago (could be a coincidence)

If I open spotify app and play something on the echo and then restart spotify integration in home assistant it works again (for anywhere between 1 and 3 days) and fails again...

Makes spotify unusable for my automations 😞

Are there any workarounds on Home Assistant side that I could implement?

Hi,

I installed Alexa Media Player addon, and you can do with it almost everything you do with Spotify addon.

 If you have any doubt on how to replace some specific command, let me know and I would try to help.

But that doesn't change the fact that Spotify is absolutely useless for home automation.

Hello Everyone,

Is tehre any update on this?

First i thought it was a openhab addon bug but after digging more into the functionality i've found out that the problem is leading to the id as name issue.

I've found out that issue also appears on the Echo Flex

I noticed that if I log out of Spotify everywhere and then log back in to Spotify, then only the echoes of the 4th generation are online.

So exactly the devices that normally go offline.

The Alexa skill is active, but only the 4th generation Echos are displayed in the device list.

If I deactivate the skill and activate it again immediately, all Echo devices are displayed.

Maybe this will help Spotify troubleshoot

It took a long time, but we believe this issue should finally be fixed. Can some help confirm?

I have checked it. To begin with all my echos were showing but the Echo
(4th gen) did not. I opened spotify. I played something through the echo
dot and it shows up correctly in my list of devices with no serial numbers.
So, it looks like you have resolved the issue. Thanks very much for looking
into it. I will keep you posted if anything changes.

the 4th generation echoes still disappear from the device list.

I'll just say that nothing has improved.

absolutely nothing.
not even a little bit

Hello. As far as the 3rd Generation issue with the serial number, it doesn't seem to be happening anymore, but I think it's still early to call.

I Haven't had the chance to run some tests with my 4th Generation, but based on recent comments, I think it's safe to assume that this issue with the 4th Generation Echo Dot suddenly "disappearing" has not been fixed and might be unrelated to our (now allegedly fixed) issue on the 3rd Generation.


I think most (if not all) users here have also faced this problem with the 4 Gen, and expect some kind of feedback on this end as well. I believe I don't speak exclusively for myself when I say that we hope you guys can also check into this issue.

 

Regardless, nice of you guys to keep us posted. Thanks!

I confirm that 4th generation are not yet visible in the device list. While the 3rd generation no longer shows serial numbers, but the real name of the device.

@ohej

 

Unfortunately, I have to address you directly now.

When can users of the Amazon Echos of the 4th. Generation also use their devices with the API interface.???

the topic is almost 1 year old now.

we users paid money for their echoes.
The API middleware was not always free either.

the premium account also costs monthly.

Even if you don't give a damn about your customers, I still care about my customers.

 

 

 

 

This thread is about the serial issue, which looks to be (finally) resolved. The 4th generation Echo issue is separate and relates to the 4th generations "low power mode". I'd prefer if we raise a new post to track it separately. I've initiated conversations internally, meanwhile let's close down this thread and start a new one to focus on the 4th gen issue.

 

Thanks

Child Item
Child Item