My Alexa Media Player stopped working.

[Pinchosct]

My Alexa Media Player stopped working overnight. I don't know if it was due to an update or something, but it was working, and shortly after, I noticed I had failed automations for Alexa Media Player. Despite being installed and recognizing all devices, it told me it didn't recognize Alexa Media Player. I decided to uninstall and reinstall it, and now I'm getting an error in the 2FA code. The process I follow is as follows: I fill in all the information in Alexa Media Player and then go to an incognito browser. I try to log in to Amazon. When it asks for the 2FA code, I close that browser. I copy and paste the code into the data box to log in to Alexa Media Player, but I always get the same error:
Please confirm the information below. For legacy settings, disable the 'Use proxy sign-in method' option.

Invalid Built-In 2FA key

I'm using HA OS and the version is 2025.10.2

Alexa Media Player: I've tested versions 5.7.6, 5.7.7, and 5.7.8.

[danielbrunt57]

The Built-in 2FA key is 52-characters (e.g. 7O7L VKJ2 WE2V 4XAV EJVF OGN2 55SE K5SG HRJM DYOG 3IC4 FLIO TWWA) which AMP uses to generate a 6-digit OTP for logging in with. You cannot enter a different 6-digit OTP into AMP's log in window. After you've processed the AMP log in sequence, AMP then uses the information supplied to actually log into Amazon internally. If the 52-character secret key generated OTP fails, you'll get "Invalid bult-in key". That secret key has to work with Amazon! You can put your AMP secret key into IT - Tools: OTP Code Generator and try and use that generated OTP to log into Amazon with.

If you've not validated the secret key in Amazon, then that key's generated OTP won't work.

[Pinchosct]

Excuse me... but I didn't understand anything. I've linked Google Authenticator to my phone and there I have the 6-digit password that keeps changing, but I don't quite understand what you explained to me. Could you give me a step-by-step guide on how to connect AMP? A manual for dummies. xD

[danielbrunt57]

Refer to AMP's Installation and Configuration Wiki

[Pinchosct]

Ok, ok, I understood and managed to install it, thank you so much for your patience with my clumsiness, now I find that once installed and logged in, the account is recognized without problems, but the Alexa devices do not appear, despite having told it to connect the devices via Echo

[danielbrunt57]

That was 3 hours ago. Have they shown up? If not, you should find errors in the AMP debug logs...

[Pinchosct]

No... they haven't come out, I only get the email with which I'm registered, but even when I click on it, it doesn't display or do anything. I've clicked on refresh/reload integration and nothing... How can I see the debug logs?

[danielbrunt57]

Enable Advanced debugging in the integration configuration/reconfigure settings.

Override HA's default logging level for these AMP components by adding the following to your logger: section in HA configuration and restart HA to implement:

logger:
  logs:
    alexapy: debug
    authcaptureproxy: debug
    custom_components.alexa_media: debug

View HA's logs: Settings > System > Logs.
Select the three dot menu upper right and click Show raw logs.
In there you can filter the logs by entering Alexa in Search logs

[Pinchosct]

This is what I'm observing:
Este error se originó a partir de una integración personalizada.

Registrador: custom_components.alexa_media
Fuente: helpers/update_coordinator.py:424
integración: Alexa Media Player (documentación, problemas)
Ocurrió por primera vez: 07:13:22 (1 ocurrencia)
Última vez registrado: 07:13:22

Error fetching alexa_media data: Error communicating with API: 'NoneType' object has no attribute 'get'

[danielbrunt57]

That message is a result of the API GraphQL query returning the UNOFFICIAL_CLIENT_TOO_MANY_REQUESTS error message as data instead of network details as data which results in the get failing to find the expected attribute in the response.

[Pinchosct]

I'm sorry... my English is very bad and I don't know what you're talking about... could you explain it another way?

[danielbrunt57]

This is the same issue as #3032

[danielbrunt57]

The internal query to Amazon API for network devices via /nexus/vi/graphql initially and repeatedly fails with an error Too many requests but should eventually succeed and your devices should appear. How long a wait? It varies region to region and perhaps even time of day. I can rewrite alexapy to catch and suppress the error, and instead issue a more friendly Warning message but the result will still be the same: Echo devices will be unavailable after restarting HA.

[dmcguire29]

Hi @danielbrunt57 - sorry to ask for help again, you recently help me get logged back in and discover my devices again. Unfortunately I now can’t reconfigure my account. I have Google Authenticator set up and it doesn’t recognize the 6 digit code. I tried setting Microsoft Authenticator using the 52 character you describe above but I still get the same 2FA invalid code error. Is there something basic I am missing? I have tried to research the issue, but can’t get it sorted.

[dmcguire29]

Hi Daniel - that was stupid of me. So using the 52 character I can get a stage further and complete all the log-in in formation also in my browser. But I still can't get in - I have 3 warnings lifted from the logs as follows: (any tips then I promise to leave you alone)

Logger: alexapy.helpers
Source: custom_components/alexa_media/init.py:735
integration: Alexa Media Player (documentation, issues)
First occurred: 14:16:03 (1 occurrence)
Last logged: 14:16:03

alexaapi.get_notifications((<alexapy.alexalogin.AlexaLogin object at 0x7f528fad50>,), {}): An error occurred accessing AlexaAPI: An exception of type AlexapyLoginError occurred. Arguments: ('Login error detected; not contacting API',)

Logger: alexapy.helpers
Source: custom_components/alexa_media/init.py:804
integration: Alexa Media Player (documentation, issues)
First occurred: 14:16:03 (2 occurrences)
Last logged: 14:16:03

alexaapi.get_customer_history_records((<alexapy.alexalogin.AlexaLogin object at 0x7f528fad50>,), {'max_record_size': 10}): An error occurred accessing AlexaAPI: An exception of type AlexapyLoginError occurred. Arguments: ('Login error detected; not contacting API',)
alexaapi.get_last_device_serial((<alexapy.alexalogin.AlexaLogin object at 0x7f528fad50>,), {}): An error occurred accessing AlexaAPI: An exception of type AlexapyLoginError occurred. Arguments: ('Login error detected; not contacting API',)

Logger: custom_components.alexa_media
Source: helpers/update_coordinator.py:403
integration: Alexa Media Player (documentation, issues)
First occurred: November 5, 2025 at 23:57:05 (2 occurrences)
Last logged: 14:16:03

Unexpected error fetching alexa_media data
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 403, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 294, in _async_update_data
return await self.update_method()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/alexa_media/init.py", line 681, in async_update_data
await hass.config_entries.async_forward_entry_setups(
config_entry, ALEXA_COMPONENTS
)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2594, in async_forward_entry_setups
raise OperationNotAllowed(
...<4 lines>...
)
homeassistant.config_entries.OperationNotAllowed: The config entry 'dmcguire29@me.com - amazon.com' (alexa_media) with entry_id '01K8YPDBM083M8MMRGGBDTJ8E1' cannot forward setup for ['media_player'] because it is in state ConfigEntryState.SETUP_ERROR, but needs to be in the ConfigEntryState.LOADED state

[dmcguire29]

I managed to get it running today - Home Assistant upgraded core - so I tried it again and it worked first time. Strange all round. But thank you for all the prompts.

[dmcguire29]

@danielbrunt57 hi Daniel. I updated the core today to latest version (22nd Nov) and I AMP stopped seeing my device again. I uninstalled and reinstalled, I have it all authenticated but it is not finding any devices. I changed the flag to false on line 333 again - but still no luck. Any tips / prompts?

[danielbrunt57]

Probably need to dig through the detailed debug logs (filter by alexa).
Note: There are pending PR's though which should get merged and released this weekend by Alan.
You could try the __init__.py from PR#3149

[dmcguire29]

@danielbrunt57 the update released today fixed the issue…….. again thanks for the prompt that it was coming - very much appreciated.

[Pinchosct]

Since I did the new AMP update, I can no longer log in. I enter all the data, it sends me to an Amazon window, asks me to log in and then the 2-step verification, and I have tried both the SMS I receive and the 52-digit code (which I cannot enter in full because it cuts it off) and I still can't log in again.

[danielbrunt57]

... ,asks me to log in and then the 2-step verification, and I have tried both the SMS I receive and the 52-digit code (which I cannot enter in full because it cuts it off)

That's not how you use the 52-charactrer code nor should be using an SMS response from Amazon with a one time code. The 52-character code has to be entered AMP's in configuration (' ') so it itself can generate and supply the OTP code into Amazon's 2-step verification window. You also need to change your Amazon account security so that Authenticator App is the primary method rather than using an Amazon generated one time code via SMS message.

[propi62]

[kubazap87]

Can someone help?

[rrubin0]

For me, on 2025.11.0, I was able to login after re-configuration until just now, as it failed. As I type this, I retried a couple of times, and it has reauthenticated successfully.

Upon reauthentication, however, I notice that all of my notify.alexa_media_player entities are no longer present.

---

The steps I used to reauthenticate are:

1. Click reconfigure:

2. Accept default values and click submit:

3. Copy the 2FA code to the clipboard, check the box and click submit:

4. Choose "already a customer" and sign in (keep me signed in and don't require 2FA options don't seem to have any effect)

5. Paste the 2FA code and click sign in:

6. Return to Home Assistant and reload the integration:

7. If it worked, you'll see this:

8. If it failed to reauthenticate, repeat from step 1.

[redbullstaff]

not working...

[vrengad]

I have amazon.nl account. my alexa app says amazon.co.uk. and google says all eu region are under amazon.co.uk. so what's expected in first field region domain. amazon.co.uk or amazon.nl?

[danielbrunt57]

In your Amazon account for .nl, are your devices registered there or are they registered in .co.uk?

I can log into either .ca or .com and when I first started with Alexa, my first device was registered in .com as I purchased it from amazon.com as were a couple more after that. Then I moved them to .ca and reconfigured AMP to .ca. I can't recall now if I had to remove and reinstall the Alexa app or not when I did that. My login to both domains was my same email but back then, the passwords for those were different and I had to synchronize them to make it easier for me. I don't think this is still the case now though.

[vrengad]

Hi Daniel, thanks for your message. I am registered in Amazon.nl But read or directed by chatgpt to use co.uk. i couldn't find reference. but configured with co.uk and the integration is working.