Echo Devices (Alexa) as Media Player - Testers Needed

I’m having setup issues.
I’ve set MFA for the config app as described, however the Amazon MFA page says to click “time based” in the app setup.
I don’t see that on the HA config for the integration.
When I complete the setup and go to the next screen, it tries to log me in to Alexa however the MFA token that is generated looks to be a static one and not time based (this is my assumption) because I am getting this error:

There was a problem
The One Time Password (OTP) you entered is not valid. Please try again.

what can I do to work around this?

Does anybody know where these errors received after the last restart come from:

Logger: homeassistant.components.light
Source: custom_components/alexa_media/light.py:78
Integration: Licht (documentation, issues)
First occurred: 17:15:02 (1 occurrences)
Last logged: 17:15:02

Error while setting up alexa_media platform for light
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
    await asyncio.shield(task)
  File "/config/custom_components/alexa_media/light.py", line 78, in async_setup_platform
    account = config[CONF_EMAIL] if config else discovery_info["config"][CONF_EMAIL]
KeyError: 'email'

Have that for sensor, alarm_control and switch platform as well.
Alexa speech output works

Is this after the latest HACS update to 1.25.1?

I have a nightmare with HACS components since the latest upgrade but nothing (thankfully) with AMP

My errors are with lovelace components and I have a consistent error with HACS

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:96
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 20:15:31 (9 occurrences)
Last logged: 20:15:31

[547876251344] Received invalid command: hacs/subscribe

But after re-downloading the components everything works!!
Still get the above error though which has occurred since updating HACS

@agratam Would you mind outlining how you changed the domain. One the config is set up it does not allow you to alter any settings. Currently there are no entries in the configuration.yaml for it.

It’s not in yaml but though integrations
When you add Alexa media player integration you can pick the region domain. It has to be the same where your echo devices are registered.

Regards

Matteo

Remove and readd the integration to change settings. Everything should stay consistent between installs as long as your Echo serial numbers don’t change for some reason.

Thank you both for your replies. I was expecting I would have to go through that whole process again. I will give it a go.

Thanks

Hi,

After the recent update to Alexa Media integration (Hacs) , I keep getting notification after reboot of my raspberry pi for “Alexa Media Reauthentication required”

I reauthenticate it… until the next reboot everything works fine and after a reboot of raspberry pi the same notification comes.

Kindly guide how to fix this.

Thanks

1 Like

Yes, I am experiencing the same thing. I think it’s maybe something to do with the 2022.6 update. I am on alexa_media_player 4.0.1 and 2022.5.5 with no issue after any restart of HA. No reauthentication required.

After I update to 2022.6 but still on alexa media player 4.0.1, I was getting the reauthentication message after every restart of HA. I’ve updated to 4.0.2, and still getting the same message as well.

I am seeing this error in log.

Logger: alexapy.alexalogin
Source: /usr/local/lib/python3.9/site-packages/alexapy/alexalogin.py:706
First occurred: 4:19:38 PM (1 occurrences)
Last logged: 4:19:38 PM
No access token found; falling back to credential login instead of oauth.

Logger: custom_components.alexa_media
Source: helpers/update_coordinator.py:223
Integration: Alexa Media Player (documentation, issues)
First occurred: 4:19:47 PM (1 occurrences)
Last logged: 4:19:47 PM
Error fetching alexa_media data: Error communicating with API:
1 Like

Exactly the same issue here. After every reboot there is a need to reauth.

1 Like

Same issue

@duceduc @martoq @matteos1

  • Make sure you have removed any old Alexa Media Player configuration data from configuration.yaml.
  • If that doesn’t solve the issue, remove and re-add the integration to make sure alexapy is up to date.
2 Likes

So you are saying we do not need these any longer in configuration.yaml ??

alexa_media:
  accounts:
    - email: !secret amazon_user
      password: !secret amazon_password
      url: amazon.com
      include_devices:
       - Ai.1
       - Ai.2
       - Ai.3
       - Ai.4

Correct, it will cause problems if you leave it in your configuration file.

I pulled mine out and it looks like it resolved the reauth issue.

i dont have it in configuration. yaml and im having this issue

I converted all my “legacy groups” to the new helper groups. I’m having a hard time getting my media_player groups (of echo devices) to work with the alexa notify. Send “hello” to all the downstairs echos. Do helper groups work? Do I need to specify each echo device on the service call?

Thanks.

Just like the Media integration, the helper-based media player groups do not work for Alexa. You can:

  1. list all the echos as targets
  2. use the old-style groups
  3. or create speaker groups in the Alexa app which will appear in HA as their own media player entity ID.


* FYI if you use Alexa-defined speaker groups you must use type: announcetype: tts will not work.

Thank you. I created a group of 1 and it worked…after that it breaks down. I went back to the old-style groups just for my echo’s. Much appreciated.

Can’t find “next_timer” attributes in my alexa device. I’ve just set a timer on the device. In the attached screenshot, you can see my “last_called_summary” as “alexa set a timer for thirty five minutes”. I’m expecting to find a “next_timer” attribute, but it’s not there.

I’m not using “alexa” at all in my /config/configuration.yaml (see screenshot). Any ideas ?