alexa_media_player: Alexa API / Too many requests

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

Error fetching alexa_media data: Error communicating with API: Too Many Requests

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).

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.

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)

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

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.

Error fetching alexa_media data: Error communicating with API: Too Many Requests

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.

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 …

also other smarthome tools like FHEM have problems - Amazon changed something

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:

1. I had just gotten the “add connected devices” option to get the temperature sensor of one of my 10 alexa devices. I deactivated and deleted this entity firstly because these error messages started and secondly because it was not very precise and timely in updating; I prefer to keep the other sensors I have integrated. after restoring everything to how it was before the 3 error messages continued to appear.
2. I looked in core.config_entries for that value (object at 0x7f8879d8d690) reported in the 3 occurrences of the warning message relating to the “Logger: alexapy.helpers” and I discovered that it referred to the “radio browser” integration that I had disabled; at this point I re-enabled it but the errors continued; I decided to remove it completely but the result did not change.

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