Alexa API / Too many requests

[nephrotranz]

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

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. 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

[1800Zeta]

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

[serlinGi]

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.

[evilmumi]

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

[Pirol62]

Hi,

enclose my log entries from different days.
There is no recognizable frequency that leads to a certain automation causing this error:

2024-01-28 22:38:47.309 ERROR (MainThread) [alexapy.alexaapi] Giving up _static_request(...) after 5 tries (alexapy.errors.AlexapyTooManyRequestsError: Too Many Requests)
2024-01-28 22:38:47.311 ERROR (MainThread) [custom_components.alexa_media] Error fetching alexa_media data: Error communicating with API: Too Many Requests
2024-01-28 23:09:16.992 ERROR (MainThread) [alexapy.alexaapi] Giving up _static_request(...) after 5 tries (alexapy.errors.AlexapyTooManyRequestsError: Too Many Requests)
2024-01-28 23:09:16.993 ERROR (MainThread) [custom_components.alexa_media] Error fetching alexa_media data: Error communicating with API: Too Many Requests
2024-01-29 02:26:09.265 ERROR (MainThread) [alexapy.alexaapi] Giving up _static_request(...) after 5 tries (alexapy.errors.AlexapyTooManyRequestsError: Too Many Requests)
2024-01-29 02:26:09.267 ERROR (MainThread) [custom_components.alexa_media] Error fetching alexa_media data: Error communicating with API: Too Many Requests
2024-01-29 03:06:41.212 ERROR (MainThread) [alexapy.alexaapi] Giving up _static_request(...) after 5 tries (alexapy.errors.AlexapyTooManyRequestsError: Too Many Requests)
2024-01-29 03:06:41.213 ERROR (MainThread) [custom_components.alexa_media] Error fetching alexa_media data: Error communicating with API: Too Many Requests
2024-01-29 09:33:14.224 ERROR (MainThread) [alexapy.alexaapi] Giving up _static_request(...) after 5 tries (alexapy.errors.AlexapyTooManyRequestsError: Too Many Requests)
2024-01-29 09:33:14.224 ERROR (MainThread) [custom_components.alexa_media] Error fetching alexa_media data: Error communicating with API: Too Many Requests
2024-01-30 00:43:23.971 ERROR (MainThread) [alexapy.alexaapi] Giving up _static_request(...) after 5 tries (alexapy.errors.AlexapyTooManyRequestsError: Too Many Requests)
2024-01-30 00:43:23.972 ERROR (MainThread) [custom_components.alexa_media] Error fetching alexa_media data: Error communicating with API: Too Many Requests
2024-01-30 07:38:28.368 ERROR (MainThread) [alexapy.alexaapi] Giving up _static_request(...) after 5 tries (alexapy.errors.AlexapyTooManyRequestsError: Too Many Requests)
2024-01-30 07:38:28.369 ERROR (MainThread) [custom_components.alexa_media] Error fetching alexa_media data: Error communicating with API: Too Many Requests

[nephrotranz]

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.

[enkama]

Yup. Its getting pretty annoying. Thought I was the only one. To a state where I cant stop my audio player radio over voice command.

alexaapi.get_customer_history_records((<alexapy.alexalogin.AlexaLogin object at 0x7fe0e26befd0>,), {'max_record_size': 10}): An error occurred accessing AlexaAPI: An exception of type AlexapyTooManyRequestsError occurred. Arguments: ('Too Many Requests',)
alexaapi.get_last_device_serial((<alexapy.alexalogin.AlexaLogin object at 0x7fe0e26befd0>,), {}): An error occurred accessing AlexaAPI: An exception of type AlexapyTooManyRequestsError occurred. Arguments: ('Too Many Requests',)
alexaapi.get_customer_history_records((<alexapy.alexalogin.AlexaLogin object at 0x7fe0e26befd0>,), {'max_record_size': 10}): Timeout error occurred accessing AlexaAPI: An exception of type CancelledError occurred. Arguments: ()

Giving up _static_request(...) after 5 tries (alexapy.errors.AlexapyTooManyRequestsError: Too Many Requests)

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

[micium]

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

[driagi]

Same problem

[DeCysos]

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

[micium]

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

Did you need to reconfigure alexa_media or just reloaded the integration?

[DeCysos]

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

Did you need to reconfigure alexa_media or just reload the integration?

The integration was automatically reloaded after I pressed CTRL + F5. Nothing more had to be done. But as I said, so far the message hasn't come back, but I'll know tomorrow between 8 and 11 a.m., because it was usually during this time that problems occurred.

[enkama]

Did not fix it for me. Deleted it, restarted and again got this.

alexaapi.get_customer_history_records((<alexapy.alexalogin.AlexaLogin object at 0x7fc1f7edf800>,), {'max_record_size': 10}): Timeout error occurred accessing AlexaAPI: An exception of type CancelledError occurred. Arguments: ()

[micium]

Did not fix for me. I suppose depend of responsive of AWS cloud.

[jonathan-schmieg]

Didn't work for me either

[DeCysos]

Unfortunately, it didn't last for me.
It started again this morning at around 1am and then at around 8am.

Logger: alexapy.alexaapi
Source: custom_components/alexa_media/init.py:756
Integration: Alexa Media Player (documentation, issues)
First occurred: 01:30:58 (2 occurrences)
Last logged: 08:41:51
Giving up _static_request(...) after 5 tries (alexapy.errors.AlexapyTooManyRequestsError: Too Many Requests) Giving up _static_request(...) after 5 tries (alexapy.errors.AlexapyTooManyRequestsError)

--

Logger: custom_components.alexa_media
Source: helpers/update_coordinator.py:332
Integration: Alexa Media Player (documentation, issues)
First occurred: 01:30:58 (2 occurrences)
Last logged: 08:41:51
Error fetching alexa_media data: Error communicating with API: Too Many Requests Error fetching alexa_media data: Error communicating with API:

--

Logger: aiohttp.server
Source: /usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py:421
First occurred: 02:10:54 (2 occurrences)
Last logged: 08:58:11
Error handling request

Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 350, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 557, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message:
Invalid method encountered:

b'\x03'
  ^

--

Logger: alexapy.helpers
Source: custom_components/alexa_media/init.py:756
Integration: Alexa Media Player (documentation, issues)
First occurred: 01:30:58 (9 occurrences)
Last logged: 10:40:42

alexaapi.get_customer_history_records((<alexapy.alexalogin.AlexaLogin object at 0x7f1b1d522e90>,), {'max_record_size': 10}): An error occurred accessing AlexaAPI: An exception of type AlexapyTooManyRequestsError occurred. Arguments: ('Too Many Requests',)
alexaapi.get_last_device_serial((<alexapy.alexalogin.AlexaLogin object at 0x7f1b1d522e90>,), {}): An error occurred accessing AlexaAPI: An exception of type AlexapyTooManyRequestsError occurred. Arguments: ('Too Many Requests',)
alexaapi.get_customer_history_records((<alexapy.alexalogin.AlexaLogin object at 0x7f1b1d522e90>,), {'max_record_size': 10}): Timeout error occurred accessing AlexaAPI: An exception of type CancelledError occurred. Arguments: ()
alexaapi.get_customer_history_records((<alexapy.alexalogin.AlexaLogin object at 0x7f1b1d522e90>,), {'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 0x7f1b1d522e90>,), {}): An error occurred accessing AlexaAPI: An exception of type AlexapyTooManyRequestsError occurred. Arguments: ('',)

[Joo01]

Same issues in the log.
But to be honest, I don't see any limitations in functionality, at least none that I noticed.
What impact do you have as a result of the error?

2024-02-03 06:16:08.325 ERROR (MainThread) [custom_components.alexa_media] Error fetching alexa_media data: Error communicating with API: Too Many Requests
2024-02-03 06:26:19.769 ERROR (MainThread) [alexapy.alexaapi] Giving up _static_request(...) after 5 tries (alexapy.errors.AlexapyTooManyRequestsError: Too Many Requests)
2024-02-03 06:26:19.769 WARNING (MainThread) [alexapy.helpers] alexaapi.get_customer_history_records((<alexapy.alexalogin.AlexaLogin object at 0x7ff11c835fd0>,), {'max_record_size': 10}): An error occurred accessing AlexaAPI: An exception of type AlexapyTooManyRequestsError occurred. Arguments:
('Too Many Requests',)
2024-02-03 06:26:19.769 WARNING (MainThread) [alexapy.helpers] alexaapi.get_last_device_serial((<alexapy.alexalogin.AlexaLogin object at 0x7ff11c835fd0>,), {}): An error occurred accessing AlexaAPI: An exception of type AlexapyTooManyRequestsError occurred. Arguments:
('Too Many Requests',)

[micium]

sometimes the Echo are unavailable, the related service not available and repair required

[nephrotranz]

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.

[Moxser]

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

[DeCysos]

What impact do you have as a result of the error?

I don't actually have any problems that I would notice.
But as the others here have just reported, it is also the case with me that various Alexa devices (in my case Echo) sometimes seem to lose the connection or recording.
This happens at the times when the error message appears.

This happens more often with an Echo in the kitchen than with other devices and the recording time is then interrupted for about 10 minutes. Unfortunately, I can only see this in the temperature recording.

Logger: alexapy.helpers
Source: custom_components/alexa_media/init.py:756
Integration: Alexa Media Player (documentation, issues)
First occurred: 04:57:40 (6 occurrences)
Last logged: 09:56:47

alexaapi.get_customer_history_records((<alexapy.alexalogin.AlexaLogin object at 0x7fb8f2194490>,), {'max_record_size': 10}): Timeout error occurred accessing AlexaAPI: An exception of type CancelledError occurred. Arguments: ()
In this case, however, it is only a warning, not an error message.

The other Echo devices in the apartment (living room, 2x bedroom) only have two interruptions, while the one in the kitchen has 6 interruptions.

It is a pity that certain error messages / warnings cannot simply be suppressed. :)
The warning/error messages only appeared with the updates this year, I didn't have such messages before. It's either due to HA or Amazon itself.

Regarding the voice output of the Echo devices caused by HA, I don't notice anything. Because the voice output only comes as soon as windows are opened or closed in connection with the heating. And so far everything has worked without any problems.

Perhaps this will also change in the future so that the extension (Alexa Media Player) will soon no longer work at all and you will have to do it via the Nabu Casa service.

[AnonBit]

Same problem

[M4v3r1cK87]

Same problem too

[enkama]

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.

[micium]

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.

with reference to point 2. of your note, I am not finding in the core.config_entries file or other HA file any reference to the object reported in the error log (e.g. object at 0x7f4f5e6090 ), where am I going wrong?

[serlinGi]

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.

with reference to point 2. of your note, I am not finding in the core.config_entries file or other HA file any reference to the object reported in the error log (e.g. object at 0x7f4f5e6090 ), where am I going wrong?

I @micium,
I think that "0x7f4f5e6090" is the object string in my log; you search this? if yes, you need to look for the string that appears in your log.

[micium]

with reference to point 2. of your note, I am not finding in the core.config_entries file or other HA file any reference to the object reported in the error log (e.g. object at 0x7f4f5e6090 ), where am I going wrong?

I @micium, I think that "0x7f4f5e6090" is the object string in my log; you search this? if yes, you need to look for the string that appears in your log.

No, the 0x7f4f5e6090 is the object in my log but i did not find it in my HA files

[serlinGi]

with reference to point 2. of your note, I am not finding in the core.config_entries file or other HA file any reference to the object reported in the error log (e.g. object at 0x7f4f5e6090 ), where am I going wrong?

I @micium, I think that "0x7f4f5e6090" is the object string in my log; you search this? if yes, you need to look for the string that appears in your log.

No, the 0x7f4f5e6090 is the object in my log but i did not find it in my HA files

I' m sorry, I don't know.
In this time I can't find it in my file either; maybe it really was a coincidence

[alandtse]

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.

[ultimo678]

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?

[Cippo2019]

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!

hi
if you mean configuration.yaml related to HA (the main one) i dont have that entry
or you mean that file located elsewhere ?

wbr

[Gheben]

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!

hi if you mean configuration.yaml related to HA (the main one) i dont have that entry or you mean that file located elsewhere ?

wbr

Yes, the configuration.yaml in the main folder.
Read the documentation here, in the section Alexa Smart Home Integration Configuration https://www.home-assistant.io/integrations/alexa.smart_home/

[micium]

I confirm that by commenting "API:" statement in the configuration.yaml file the messages have disappeared

[Pirol62]

Sorry but I never had these entries in configuration.yaml and even faced these messages.
We should follow what alandtse wrote. It's an issue on amazons side.
By the way: since two weeks, the number of appearences of these messages decreased significantly.
And after the update to 2024.2.3 yesterday noon I had none.

[wildfire305]

For me this issue has resolved itself. It appears that I get updates from the API whenever they update from the device. The only thing I have done was power cycle everything.

[Cippo2019]

Sorry but I never had these entries in configuration.yaml and even faced these messages. We should follow what alandtse wrote. It's an issue on amazons side. By the way: since two weeks, the number of appearences of these messages decreased significantly. And after the update to 2024.2.3 yesterday noon I had none.

me too, i dont have this part into conf.yaml...... the link is for official integration but here we are on custom integration :-(
but for me nothing change in last 2 weeks... always every 10 minutes more or less...
also after 2024.2.3
also after restarting everything @wildfire305

so... it is different

[nephrotranz]

Also no errors for me since the update to 2024 2.3 (I also had problems with the FritzBox Integration, which are also gone now).

[ultimo678]

I updated to the latest 2024.2.3... I restarted all the Amazon devices (3 echoes and an air quality monitor) but nothing has changed, in fact I continue to have device disconnections (the frequency of disconnections varies depending on the day).
Honestly, if I had known that Amazon's air quality monitor had given me all these difficulties I probably wouldn't bought it (since I was looking for it exclusively to connect to the HA).
Is there a way to apply the solution posted in the forum also to those who use Alan's custom component?

[ziolelle]

Same here, even upgraded to 2024.2.4 today, 5 Echo devices restarted, HA restarted. Nothing changed.
No entries regarding "media_player" in config files.
I agree to the idea that it is a Amazon issue: rarely the stuff works and I would say randomly.

[Cippo2019]

Problem disappear now for me..... nothing done... :-)

[paolo-rendano]

Same for me.. disappeared. This was an amazon issue

[zSprawl]

And here I am coming here because I've been seeing these errors in the logs for the last few days. I suppose it's my turn!

[ziolelle]

The issue concerning errors are gone, changing volume using "media_player.volume_set" works, but reading the volume level back using the attribute "volume_level" of entity "media_player.xxxx" gives wrong values

[Moxser]

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

[Cippo2019]

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 :-(

[Kipmo]

Just got this error for the first time yesterday (March 4th)

[jocamane]

in my HA the errors don't stop.

[zSprawl]

Yeah seems to happen every day, a dozen times per day. Most of the time, everything recovers and no one notices, but occasionally it will happen right as I'm trying to toggle a light, and of course, it fails.

[Zingrock]

I hadn't used Alexa or the integration with HA for ages. Went to use it the other day to pair with my ATOM Echo and saw that none of my Alexa devices were showing. I reinstalled it and none of my 16 Echo/Alexa devices are being found or appearing in the list. The logs have a lot of "Too many requests" in the various lines.
I've also had issues with the Alexa app, devices being found and automations and stuff in there dissappearing so wouldn't surprise me if it was an issue on Amazons side

[maauso]

Hi all,

I think that I fixed it by unchecking "include devices connected through Echo" on the Alexa integration configuration.

This suggests that the problem might stem from the number of calls the integration is making to poll the devices and their statuses from the Alexa API.

[jocamane]

Hi all,

I think that I fixed it by unchecking "include devices connected through Echo" on the Alexa integration configuration.

This suggests that the problem might stem from the number of calls the integration is making to poll the devices and their statuses from the Alexa API.

No. Mine always had this option turned off and it gives errors

[antisane]

No. Mine always had this option turned off and it gives errors

Ditto.

[Loic691]

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

[lexiismadd]

Having this problem too.
Is there anything we can do to help this along and get it sorted? The integration is very unstable because of this issue and its becoming quite unreliable..
Is there any way that the integration can be changed so we need our own amazon dev account or something like that?

[Jugom]

I've had the too many requests issue in my logs for a long time, but since it never affected the actual usability, I never paid much attention to it... until a couple weeks ago.
the 'update last called' service stopped working because of this and it bricks half of my alexa based automations.
anyone else having this problem?
has anyone found a way to at least improve the situation even if just a bit?

[user514]

has anyone found a way to at least improve the situation even if just a bit?

I can tell you what I did yesterday:

-My Alexa was unavailable on my HA.
-This is the last line in the error entry in the log about alexa:
"An error occurred accessing AlexaAPI: An exception of type AlexapyTooManyRequestsError occurred. Arguments: ('Too Many Requests',)"

I unplug my alexa from power for about 30 seconds and reconnect. Let it do his thing, and get connected to it's wifi with her final blue flashes.

Went to my HA UI, --> dev-tools --> Check config and Restart HA..

After restart, with my recently rebooted Alexa Echo this time... my alexa entities became available upon restart.
Since yesterday, my alexa is working and giving me all the TextToSpeech messages I have configured on her.

Don't now if it will last, but at least, I know when someone is knocking at the door for the last 24 hours. Hope it helps.

(note: I must add that I still see 'tooManyRequests' messages in the log. They are still there, but at least my Echo is available and working)

[lexiismadd]

I'm pretty confident that it's not a localised thing to individual configurations, but that there is too many people probably using the add on now globally and that's what is causing it to hit a limit.. of course, I can't be sure either.. But I do notice it happens more often around the same time of the day when it does happen.
I tried probing through some of alandtse's code to see if I could spot anything that might indicate my theory and any way I might be able to suggest an alternative or offer some help but it's a pretty complex add on and I'm not a powerful python coder (yet) so I stopped when I realised it was way over my head..

[bschollnick]

Having an issue here, too.