#Alexa connected devices

1 messages · Page 1 of 1 (latest)

exotic ingot
#

I have looked through the posts and can see that everyone else is having issues whoever I can't see if this is something that can or will be fixed? Have Amazon now completely closed it off so it will never be repaired? I have a few Alexa plugs and an Air Quality monitor that I use, I dont really want to have to replace them.

sly bane
#

You mean the offical "Alexa Devices" integration? It stopped working for me 4 days ago. No idea how I can fix it...

hollow veldt
#

amazon seems to have shut down part of their API which provided access to echo connected devices. this broke both Alexa Devices and Alexa Media Player (AMP). AMP was "fixed" by no longer accessing that particular API, which makes them work for announcements and such, but "devices connected via echo" do not work

#

i also have a couple of AQMs and at this point i'm just going to get something else that's locally accessible. i doubt those APIs will be back (just IMO)

#

@sly bane Alexa Media Player (which can be downloaded via HACS) does work for announcements and playing media on your echo devices

north breach
#

Amazon has confirmed that all Alexa skills are unavailable for thousands of users right now. Myself included. 😦 And here I thought I broke my HA/Alexa integration!

nocturne pewter
lavish hare
#

Just to clarify, AMP is not part of HACs. It's a custom integration. HACs is a downloader for custom integrations and they can all be installed without using HACs.

hollow veldt
#

fixed my statement

wraith bison
#

Hello @hollow veldt could you give some source of your statement about Amazon shutting down their API?

I am currently facing the issue everyone is facing on adding the Alexa devices integration:

2025-07-11 15:06:52.580 ERROR (MainThread) [homeassistant.components.alexa_devices] Unexpected error fetching REDACTED EMAIL data
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 382, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/alexa_devices/coordinator.py", line 54, in _async_update_data
    return await self.api.get_devices_data()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aioamazondevices/api.py", line 809, in get_devices_data
    entity_ids_list = await self._get_devices_ids()
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aioamazondevices/api.py", line 580, in _get_devices_ids
    _, raw_resp = await self._session_request(
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<3 lines>...
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/aioamazondevices/api.py", line 407, in _session_request
    f"Request failed: {HTTPStatus(resp.status).phrase}"
                       ~~~~~~~~~~^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/enum.py", line 726, in __call__
    return cls.__new__(cls, value)
           ~~~~~~~~~~~^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/enum.py", line 1201, in __new__
    raise ve_exc
ValueError: 299 is not a valid HTTPStatus

This goes on an endless loop and I keep getting secondary OTP codes from Amazon via SMS, which tells me the integration keeps trying to log in.

I just got a new Echo Dot so I would like to know if I should just send it back right away, as it will be useless for me unless this integration is working.

viral jetty
#

@wraith bison this is a well know issue since 1 week because Amazon shutted down one endpoint that we use. New library has a fix already

wraith bison
#

Oh, thank you for confirming this. Anything I can do other than patiently waiting? :)

viral jetty
#

You can manually upgrade if you know how to proceed, or wait for .2

wraith bison
#

I don't know, but I could

#

I will look into it

#

I don't think I can in HAOS, can I

hollow veldt
wraith bison
#

Home assistant

stiff finch
#

2025.07.2 of HA. The monthly releases (i .e. 2025.07) usually are available the first Wednesday of the month, the patches (i.e 2025.07.1, 2025.07.2, etc.) usually are available subsequent Fridays. .2 is a little late.

Edit: you might already know this, but added for anyone who doesn’t.

tender cave
#

Having same issue... any idea when 0.2 will be released?

tender cave
wraith bison
#

I can confirm that it now works on .2

image.png
#

closing the issue on github

wraith bison
#

I am not getting temperature or illuminance sensors, but everything else works

#

@viral jetty should it work? My Echo Dot has got both of them

viral jetty
#

Log says there is a permanent warning and sensors are skipped. Right ?

wraith bison
#

2025-07-14 20:25:38.672 WARNING (MainThread) [aioamazondevices] Sensors data not available [/api/phoenix error 'Miscellaneous Persistent Warning'], skipping

#

Yes

hollow veldt
#

yea phoenix api was shut down

wraith bison
#

It included all other controls too right?

#

Or just sensors?

#

If it weren't useful I'd send back this Echo knowing this, now I need a new sensor for my bedroom

#

:(

hollow veldt
#

it looks like the folks working on AMP have figured out an alternative way to get the connected devices data, going by what's on their github

#

so i wouldn't chuck them just yet

viral jetty
#

We already have a draft for the new queries, we got them from inspecting Alexa Mobile App new endpoints

#

We are polishing the last things to make them reliable and then we will update the library

#

I say we as James (jameson_uk) joined me on the effort to get a feature complete and stable library

stiff finch
#

Thanks for all the work to both. The announce and speak notifiers work well. I created scripts to prompt for a message and then send it to the target device(s). I think I can promote myself from “new to HA” to “knows enough to be dangerous.” 😁

Now if I could just get my Amazon thermostat in HA (without using homebridge).

viral jetty
#

Getting devices linked to Alexa in HA is currently low priority

#

We are actively working on:

  • stabilize integration for all countries
  • re-introduce sensors via graphQL
#

After that we will add 2 new set of features (hopefully):

  • timers/schedules/alarms
  • real time websocket updates for media player
viral jetty
wraith bison
#

I appreciate all the work chemelli

#

OK, I read that sensor data is from graphQL

#

I REALLY appreciate the work now

#

considering how absurdly annoying working with graphQL is

viral jetty
#

We need to switch both calls ( phoenix and phoenix/state ) to graphQL

wraith bison
#

Thank you, I will wait patiently

#

I don't want to mess with my HA instance

#

I worked too many hours on it and I'm scared of it now

ivory yoke
viral jetty
#

Australia seems hard to fix, all the tests we did didn't worked fully

#

Maybe I can add you to a group here on discord and you can help testing a few variants

ivory yoke
#

Yeah sure, happy to help if I can

dark cedar
dense magnet
#

Hey Chemelli74, I have my Discord access now. Dabbler68 on Github, and just posted an update on #148777. Thanks for the effort you put into this.

native plank
#

Hey @viral jetty all of the Sensors are Unavailable, Temperature for example, should this already work?
Or is this part of "re-introduce sensors via graphQL" in the future?

digital field
#

Hi @viral jetty I’m having the same issue. Amazon.com.au

API countryOfResidence:
API marketPlaceDomainName:
API marketPlaceLocale:
are all Australia

viral jetty
#

Can I add you to a group where we are discussing how to proceed ?

sharp jay
viral jetty
#

Hi, can I add you to a group here with other users ?

viral jetty
sharp jay
sharp jay
viral jetty
#

I’m sorry but as far as I know the API works only if all is aligned

sharp jay
#

Hm, surprising that the kindle location would influence that, but I understand

#

I did manage to make it work through the Alexa-media-player extension installed through hacs, but I know they rely on more hacky way to deal with things

viral jetty
#

We can try to find a more “relaxed” way but should be reliable for all users.
Which url did you use in Alexa media player ?

sharp jay
#

Hm I don't remember it asking for a url/domain, but looking at the (obfuscated) config files for the integration I see amazon.com

#

I recently moved my HA from core to a container and hacs is a bit of a mess at the moment so I can't be more precise until I fix that, sorry

viral jetty
#

We can make a raw try but not now as I don’t have my pc with me at the beach 🏖️

sharp jay
# viral jetty We can make a raw try but not now as I don’t have my pc with me at the beach 🏖️

I spent part of my day yesterday trying to figure out why my hacs integrations were not working. Looks like my "HA installed as container on Termux on an android tablet via a method that emulates the concept of a docker installation with proot and other trickery (now packaged as one easy method with https://github.com/George-Seven/Termux-Udocker)" works much better than my previous fighting with core and dependencies..... but apparently pip dependencies in those conditions are messed up and end up being symlinks to temporary locations that are not accessible....

All this to say I thought about digging around in the alexa integration files to see if i can force and bypass my way in, but I have my dose of fixing it up for this weekend 😛

timid star
#

I'm also trying to configure it in Node Red, but without success.

viral jetty
#

Spain works for a lot of users so I would check your account settings

#

Did you read all troubleshooting in the docs ?

timid star
#

i'll re-read them again

sharp jay
#

@viral jetty So I modified quickly the api.py to force the market to amazon.com despite putting FR as country code, and it actually matched the return check, and gave me a list of entities 😄

Then that's not enough because the entities are all borked. So clearly something else needs to be adjusted. Not sure why it would return the list but not their properties, though. Have to debug that properly later.

image.png
#

…ok market is used only for the check, not for further calls, so all I did was bypassing the check. Ah well

viral jetty
#

The check is there because without it you pass login but then speak and announce won’t work 😉

sharp jay
#

@viral jetty Ok so I logged in again on my previous instance with alexa_media_player, using amazon.com, and it worked. No other setting was involved.

So I went back to this integration and set it up with USA, and this time it worked. The weird thing is that I did try it earlier with USA, and always got unknown error. But everytime I tried was not the first attempt after reboot, so maybe there is something in that? The configuration wizard does seem to behave weirdly after an error, though I did not try too hard to reproduce that.

So it seems to be working, at least from trying to notify the "speak" entities here and there.

So it raises the question, isn't the marketPlaceDomainName the "one true domain", in this case? Because my account is still associated to FR, yet it seems to work perfectly this way. Or is it yet another edge case?

image.png
viral jetty
#

{CC} ?

#

Country code ?

#

If you take a look at const.py there are some documented cases where it’s not “linear” but for the majority of the countries it is

sharp jay
#

ah indeed, I see that. Guess "pl" is probably going to be another "AMAZON_DE_OVERRIDE". After all the first storefront for Poland was the DE with a language option, so it would make sense.
I don't actually have a proper pl account to check that, though 😅

jade portal
viral jetty
#

Ho @jade portal are you from Portugal ?

#

If so can you edit library files ? I want you to set some values in const.py to test

jade portal
viral jetty
#

I’m on the beach with only my phone

jade portal
#

No problem, when u are available tell me what files to edit

viral jetty
#

Add a section for “pt” using alla Spain settings

#

Show it here and once ok restart and report back

#

Thx for your time testing

jade portal
#

this is the file, right?

image.png
viral jetty
#

Nope

#

Is from the library, you are looking from integration and not the right one anyway

#

“pip show aioamazondevices”

#

Will show you the path

jade portal
#

Got it, I'll test it

viral jetty
#

Yes exactly

jade portal
#

ok but there are no definitions of Spain

#

i config PT inside "DOMAIN_BY_ISO3166_COUNTRY" or outside?

viral jetty
#

Sorry for the late answer but for some reason I don’t get notifications anymore

#

You should add “pt” node and specify all settings as if it was Spain:

  • domain
  • openid.assoc_handle
  • market
jade portal
#

I add PT like this

image.png
#

when I try login, said "Invalid authentication"

#

all login parameters are correct

#

File "/usr/src/homeassistant/homeassistant/components/alexa_devices/config_flow.py", line 34, in async_step_user
data = await client.login_mode_interactive(user_input[CONF_CODE])
File "/usr/local/lib/python3.13/site-packages/aioamazondevices/api.py", line 741, in login_mode_interactive
login_method, login_url = self._get_request_from_soup(login_soup)
~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aioamazondevices/api.py", line 287, in _get_request_from_soup
raise TypeError("Unable to extract form data from response")

viral jetty
#

With only a extract of the debug log is not easy to get the exact error and place

jade portal
#

Sorry but I am very newbie

#

Can you please explain how to tshoot?

#

I am available for a call

viral jetty
#

I’m at the beach so will be in 1 week

jade portal
#

No problem

honest knoll
#

As of 2025.8.0 I no longer have the ‘Everywhere’ speaker group in my Alexa Devices. Has this been removed?
I was having a problem in that HA seemed to be doing everything right but announcements weren’t coming out the Alexa devices. I removed the integration, did the update to 2025.8, reboot, then re added the integration which correctly added all my echo dot and FireTV devices, but ‘Everywhere’ never reappeared.
Any ideas where it’s gone, anyone?

viral jetty
#

How is everywhere created ? From Alexa mobile app ? From echo dots or other like Sonos devices ?

honest knoll
#

I honestly don’t know. It was there previously, I didn’t have to create it, so I don’t know what is responsible for it. I was hoping to get some insight from other users more knowledgeable than me.
Your work on this integration, @viral jetty has been phenomenal and it has made my HA experience so much better, I’m not sure if this is a bug or just a different situation from previous installs.
I’ll keep exploring and see if I can figure out what’s changed. In the meantime I’ve worked around by modifying my automations to notify each echo dot individually instead of the everywhere group.

viral jetty
#

Create a group via Alexa mobile app, restart the integration and you will have a e tity to notify the group 😉

honest knoll
#

Continuing to be an absolute rockstar, thanks for that. (I hoped to never have to use the Alexa app again, it is terrible; but needs must as the devil drives!)

ocean fog
#

In assuming everyone else is having the issue of entities missing? Came back a few days ago and now disappeared again?

image0.jpg
viral jetty
#

It depends on country and how many requests Amazon receives

#

We have a new method to get them but still under testing

#

Please be patient

ocean fog
wraith bison
abstract bough
#

Hey! I'm in Australia and have the same issue as all the other Aussies. I'm keen to help in whatever way I can!

viral jetty
#

It’s hard for AU as we have half of the users working and half not

#

Which error do you get ?

sharp jay
native plank
viral jetty
#

Unfortunately we have a limit of 10 people per group 😭

#

Need to create a channel in a server instead

jade portal
viral jetty
jade portal
viral jetty
dense magnet
#

Another similarly titled thread? I clicked but it says invalid or expired.

viral jetty
#

Made a dedicated server to bypass 10 members group limit

#

I invited you

wraith bison
#

Simone, puoi invitarmi ancora? @viral jetty

#

Continuo a distrarmi e perdo l'invito