Exactly, non of the 5000 call has never been used.
So probably some problem has arised with the OAuth authentication.
More likely your error as it works fine and it seems your token (account) is fine as well.
But i’ve installed hacs on a blank HA installation.
I’ve followed the instruction on the screen.
“Click on the link to open github oauth authorization window”. I’ve written the HACS code in github, and clicked on the button to authorize.
After that hacs has finished it’s installation and has always been rate limited since the beginning.
I’ve started digging the problem because i couldn’t install anything in hacs.
My configuration.yaml was almost blank, i didn’t add anything.
So i don’t know where i’ve made an error.
Later i created a github token and have written the token in configuration.yaml, but the rate limit error persisted.
So i’ve deleted the hacs folder in config/.storage, restarted the server, and the problem has disappeared.
THANK YOU! Although I didn’t delete the hacs directory, this worked for me!
Getting then to as of today
Just installed HACS. I was able to view the repos at the beginning but I’m unable at the moment of writing these lines. It’s been more than an hour.
I installed HACS a few days back and I did the Oauth setup. Everything was great until earlier today when I went to remove a integration I had installed via HACS.
I opened the HACS page and here is what I was presented with:
HACS is setting up
HACS is setting up, during this time some information might be missing or incorrectHACS is disabled (Ratelimited)
GitHub API calls are ratelimited, this will clear in less than 1 hour.
Here are the only entries in my log related to HACS
2021-04-30 11:40:44 ERROR (MainThread) [custom_components.hacs] HACS is ratelimited, HACS will resume setup when the limit is cleared (11:49:09)
2021-04-30 11:40:44 ERROR (MainThread) [custom_components.hacs] HACS is disabled - HacsDisabledReason.RATE_LIMIT
2021-04-30 11:40:44 WARNING (MainThread) [homeassistant.config_entries] Config entry ‘’ for hacs integration not ready yet; Retrying in background
2021-04-30 11:40:50 WARNING (MainThread) [homeassistant.components.camera] Setup of camera platform environment_canada is taking over 10 seconds.
I am coming up on nearly 2 hours and it is still rate limited.
I also checked my Github account and there is nothing showing up under OAuth Apps.
I have an older setup of HA running (I’m rebuilding HA) with HACS. This instance uses a Personal access token and it is not rate limited.
How do I fix this? It’s apparently not fixing itself.
1 Like
What does the info page show? It will show api calls. Sounds like you’re not recognised as a user
Hi guys,
First of all, thanks everyone for contributing this feed. I have been trying to solve this issue for the past hours ! Can’t say I have succeed so far even though I tried to understand yours posts.
Same that main of the people here. Just setup my HA today. End up having first issues with the versions of HACS. Finally end up succeeding with the correct one (otherwise I wasn’t allowed to see the “market”).
Downloading 3 “apps” that I wanted to get then …
HACS is setting up
HACS is setting up, during this time some information might be missing or incorrect
HACS is disabled (Ratelimited)
GitHub API calls are ratelimited, this will clear in less than 1 hour.
I have to say that I am a real beginner in all of this … Been trying to go into my configuration.yaml and add what you guys wrote earlier. Didn’t change a thing after a reboot.
First, as the last person mentioned,“rlongfield”, I am unable to see on github my OAuth, yet I can see tha tthe app HACS is allowed. I am unable to retrieve the token (that I had for the set up) in order to reused it, so I created a new one for the line of command you gave (that is now in my configuration.yaml) ( also I have to say, the token given at the beginning was a 6 caracters thing, now I end up having a super long one)
Although I can’t say I have a directory name /config/.storage
bottom line, seems like I don’t know what file to modify or even though where to begin in order to solve this !
If anyone has a idea, feel free!
Thanks !
Hi!
I have the same.
Config entry ‘’ for hacs integration not ready yet: None; Retrying in background
12:21:34 - (WARNINGS) config_entries.py
HACS is disabled - HacsDisabledReason.RATE_LIMIT
12:21:34 - (BUGS) HACS (custom integration)
HACS is ratelimited, HACS will resume setup when the limit is cleared (1:05:17)
12:21:34 - (BUGS) HACS (custom integration)
Did you fix it?
Some how just fixed itself or actually modified something but no clue what !
Sorry 
Wow. I just installed HACS for the first time yesterday morning. I got as far as installing Circadian Lighting and rebooted again. Ever since It still says Ratelimited to this very moment. Graph doesn’t show any traffic, so I think that one hour thing has a bug in it.
I gave up myself. Later when I get the time I will come back and just uninstall everything.
Have you done this? The graph will not show you any traffic, how could it, there is none, because Github doesn’t send you any data…
Yes, only I had done it via a curl command, which is why I think there is a bug somewhere.
Core: “limit”:60,“remaining”:58
Rate: “limit”:60,“remaining”:58
Everything else is untouched 5000 out of 5000, 10 out of 10, etc.
2 Likes
On a fresh install of HACS I’m seeing exactly the same, yet I’m getting rate limit errors in my HA logs and can’t use HACS at all. 
{"resources":{"core":{"limit":60,"remaining":58,"reset":1621698357,"used":2,"resource":"core"},"graphql":{"limit":0,"remaining":0,"reset":1621700641,"used":0,"resource":"graphql"},"integration_manifest":{"limit":5000,"remaining":5000,"reset":1621700641,"used":0,"resource":"integration_manifest"},"search":{"limit":10,"remaining":10,"reset":1621697101,"used":0,"resource":"search"}},"rate":{"limit":60,"remaining":58,"reset":1621698357,"used":2,"resource":"core"}}
This error originated from a custom integration.
Logger: custom_components.hacs
Source: custom_components/hacs/api/hacs_repository.py:108
Integration: HACS (documentation, issues)
First occurred: 16:15:58 (1 occurrences)
Last logged: 16:15:58
GitHub Ratelimit error
I installed HACS yesterday also on a fresh install. But I am stuck (also after reboot and waiting for more than 24 hours) on this screen:
In the API of Github I have still rates remaining:
“rate”:{“limit”:60,“remaining”:60,
{“resources”:{“core”:{“limit”:60,“remaining”:60,“reset”:1622192037,“used”:0,“resource”:“core”}
1 Like
Same situation here … it took ages to get the local tuya keys and now hacs is not working. 40 minutes delay anounced, within 1 hour it should work but after 2 hours no progress. still the same error.
And these are the stats - just 0 used and no progress. I hope I will have to deal with that only once during installation.
{“resources”:{“core”:{“limit”:60,“remaining”:60,“reset”:1622403424,“used”:0,“resource”:“core”},“graphql”:{“limit”:0,“remaining”:0,“reset”:1622403424,“used”:0,“resource”:“graphql”},“integration_manifest”:{“limit”:5000,“remaining”:5000,“reset”:1622403424,“used”:0,“resource”:“integration_manifest”},“search”:{“limit”:10,“remaining”:10,“reset”:1622399884,“used”:0,“resource”:“search”}},“rate”:{“limit”:60,“remaining”:60,“reset”:1622403424,“used”:0,“resource”:“core”}}
After 2:15 hours now the system seems to work and Hacs is connected but no local tuya integration offered … from issue to issue for over a week now.
UPDATE: the resume thing never appeared again so it is just a kind of delayed installation. Hacs install worked on the next day. So it is just like “have a break before you will get your hacs”. Not nice, but would be a lot easier to explain this in the installation procedure and in the videos on yt that do not cover this topic.
As a complete newbie you feel lost if 1 hour is over and nothing has changed. You might think to restart the system after 1 hour but what if the time would start again from 0?
For me it was nerve racking on the long way just to get 4 tuya plugs working offline.
I am new to this and maybe I missed something, but the ratelimit errors went away when I unchecked these options:
1 Like
We call that a coincidence and it’s nothing to do with the problem so far as I know but if you don’t use appdaemon or netdaemon apps then you shouldn’t have them checked…
Worked for me too 