Hi, from time to time since a few weeks I receive this error:
Logger: homeassistant.components.alexa.state_report
Source: components/alexa/state_report.py:179
Integration: Amazon Alexa (documentation, issues)
First occurred: 6. Mai 2022, 21:28:20 (3 occurrences)
Last logged: 6. Mai 2022, 21:28:20
Error when sending ChangeReport for light.wohnzimmer to Alexa: THROTTLING_EXCEPTION: Request could not be processed due to throttling.
Everything works fine. At least I cannot notice any strange behavior.
Can somebody explain what that is?
but the automation get never triggered when alexa get no answer from me.
here is the automation for the question
service: script.activate_alexa_actionable_notification
data_template:
text: Hallo, Soll ich die Shield ausschalten?
event_id: actionable_notification_firetv_kueche_switch_off
alexa_device: media_player.echo_show_kueche
and in the script is everything correct, the ResponseYes works well.
Amazon has set very specific limits on bitrate and length so you need to make sure your file is properly formatted and isn’t too long. One of the best resources on this topic is Mark Watt’s video: Play a local mp3 file on Alexa Echo dot - #33 by MarkWattTech
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.
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.
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.
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.
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: