alexa_media_player: Alexa API / Too many requests
IMPORTANT: Please search the issues, including closed issues, and the FAQ before opening a new issue. The template is mandatory; failure to use it will result in issue closure.
Describe the bug
I am getting quite a lot of errors saying that there were too many requests and other problems (getting history records). The problem seems to be the Indoor Air Quallity Monitor, at least it is the only Amazon device I use except my Echos. I am using it as temperature and hygrometer device, I think the device is sending updates every 5 minutes.
To Reproduce
- Go to ‘…’
- Click on ‘…’
- Scroll down to ‘…’
- See error
Expected behavior
No problem with getting data, not getting the "too many requests error.
Screenshots
System details
- Home-assistant (version): 2024.1.5 // 2023.12.1
- alexa_media (version from
const.py
or HA startup): 4.9.0 - alexapy (version from
pip show alexapy
or HA startup): Package not found - Amazon 2FA is enabled (y/n). <!—We will not debug login issues if unanswered—>: yes
Logs Please provide logs. 1.) Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: custom_components.alexa_media Source: helpers/update_coordinator.py:332 Integration: Alexa Media Player (documentation, issues) First occurred: 18:12:58 (1 occurrences) Last logged: 18:12:58
Error fetching alexa_media data: Error communicating with API:
2,) Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: alexapy.helpers Source: custom_components/alexa_media/init.py:756 Integration: Alexa Media Player (documentation, issues) First occurred: 18:12:58 (2 occurrences) Last logged: 18:12:58
alexaapi.get_customer_history_records((<alexapy.alexalogin.AlexaLogin object at 0x7f74fc4950>,), {‘max_record_size’: 10}): An error occurred accessing AlexaAPI: An exception of type AlexapyTooManyRequestsError occurred. Arguments: (‘’,) alexaapi.get_last_device_serial((<alexapy.alexalogin.AlexaLogin object at 0x7f74fc4950>,), {}): An error occurred accessing AlexaAPI: An exception of type AlexapyTooManyRequestsError occurred. Arguments: (‘’,)
3.) Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: alexapy.alexaapi Source: custom_components/alexa_media/init.py:756 Integration: Alexa Media Player (documentation, issues) First occurred: 18:12:58 (1 occurrences) Last logged: 18:12:58
Giving up _static_request(…) after 5 tries (alexapy.errors.AlexapyTooManyRequestsError)
Additional context
About this issue
- Original URL
- State: open
- Created 5 months ago
- Reactions: 24
- Comments: 67 (2 by maintainers)
Okay, can we please stop writing me too? Getting an email notification just because someone can’t press thumbs up and instead has to write “same problem” isn’t helping. Thanks.
In case it wasn’t obvious, this is an Amazon issue and there’s nothing we can do about it here. I’ll leave this open for reference.
ok. I understand it’s a problem with Amazon’s servers. But I ask you, is there any solution to limit the frequency of the problem? In other words… Does the problem depend on the number of requests made on single session (so the more devices you have, the more the problem occurs) or on the frequency with which each account connects to the servers to check the status of the devices? Is there a chance that the situation can be resolved somehow or will we have to learn to live with this aspect?
Came here to say I just set this up yesterday for the first time and I’m seeing the exact same issue. I only have the one AQM on my account and no other devices.
I don’t think this happens only to a few users. It’s just not everybody commenting on this issue.
I think that people with a lot of echo devices only might have these issues. If you just have a single speaker, the integration might not send as many requests than with 10+ devices.
Same problem too
For a few days everything seemed to be back to normal. but from this night the problems started again and the entities are no longer available intermittently. Let’s hope they solve it
Same problem
After this error I a having a 5 minute gap in history data for my air quality monitor, in the dashboard it is shown as unavailable for the same time. My Echos are then not capable to execute HA scripts using tts.
sometimes the Echo are unavailable, the related service not available and repair required
Problem disappear now for me… nothing done… 😃
same issue here (5 devices)
Same issue for me too, i have 3 echo devices
Same issue for me too.
I have the same issue. Also I noticed that service to update last called alexa has disappeared. I have many alexa devices (10).
Hi Alan but I wanted to ask why this behavior doesn’t seem to affect everyone? On my side, I haven’t changed anything and it started showing up about 3 weeks ago many others do not have this problem If it were Amazon, shouldn’t it be a widespread problem?
wbr 😃
You’ll have to ask Amazon. We already limit our connections. https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/429 is what they’re telling us. Maybe there’s a PR to see if Amazon sends us actual retry info. Otherwise we already use exponential backoff with jitter which is an AWS recommended practice.
Didn’t work for me either
I had the same problem. I deleted the following file:
/homeassistant/.storage/alexa_media.myemailadress@domain.com.pickle
After the integration was reloaded, the error did not reappear. Let’s see how it goes now…
Same problem
also other smarthome tools like FHEM have problems - Amazon changed something
Same Problem for me My echo device were unavailable all the day since midnight this day… HA restart and Alexa Echo didn’t change anything… A lot error of too many request in my logs. The service is up from few minutes for now… I have no include device by Echo device checked
in my HA the errors don’t stop.
Just got this error for the first time yesterday (March 4th)
and now again also for me after some days without warning / errors 😦
I confirm that by commenting “API:” statement in the configuration.yaml file the messages have disappeared
Guys, It seems that I found a solution (temp solution?) Comment media_player and api in configuration.yaml as in the image below, restart HA and works again!
hello all, the error seems related to poll frequency of devices, if i disable “Enable polling for updates” under system option for the integration the error stop and logs are also clean. In this case as axpected the device status are not more in sync but TSS and device settings for devices work as expected. It seems related to the frequency for getting updates for the various device, furthermore i’ve noticed that the error is present in the log every 10 minutes with polling enabled, for now i’ve disabled the option but is not a solution. leaving all at default after some hours i need to re-authenticate and devices are most of time no reacheble. i don’t know if this can be helpful or not
Same here. I think most users are not aware of the issue. I wouldn’t have noticed it, if I wouldn’t have checked the dashboard in that moment when the temperature sensor of my air quality monitor was not available.
same thing for me too
Same problem here from a couple of weeks ago, no HA configuration changed in the last month. The problem was already succeeded last year, I suppose this is a problem caused by limited resources available in the AWS cloud to the customer without regular subscription, but I could be wrong …
Yes, I also think so. I integrated the air quality sensor in December and the errors started approx. 10 days (?) ago. I cannot be precise here as I noted them by coincidence when I saw my dashboard is not showing values for the sensors every now and then.
Hi 👋, same problem for me; I bring you my experience and the series of facts (coincidences?) that occurred at the same time as the errors appeared:
maybe they are just coincidences but this is it and unfortunately even by removing what seemed to me to be the cause, the errors continue.
I am also seeing similar behaviour:
Error fetching alexa_media data: Error communicating with API: Too Many Requests 6:23:58 AM – (ERROR) Alexa Media Player (custom integration) - message first occurred at January 29, 2024 at 12:50:17 PM and shows up 7 times alexaapi.get_customer_history_records((<alexapy.alexalogin.AlexaLogin object at 0x7fc34466ca10>,), {'max_record_size': 10}): An error occurred accessing AlexaAPI: An exception of type AlexapyTooManyRequestsError occurred. Arguments: ('Too Many Requests',) 6:23:58 AM – (WARNING) Alexa Media Player (custom integration) - message first occurred at January 29, 2024 at 12:50:17 PM and shows up 16 times Giving up _static_request(...) after 5 tries (alexapy.errors.AlexapyTooManyRequestsError: Too Many Requests) 6:23:58 AM – (ERROR) Alexa Media Player (custom integration) - message first occurred at January 29, 2024 at 12:50:17 PM and shows up 7 times