Sorry for the delay, things cleared up shortly after I posted and with life and things working properly I promptly forgot about the issue.
That is until today. I went and installed the Mini Media Player this morning played around with it a bit and restarted HA as one of my Snapcast clients wasn’t detected. After the restart I tried to access my Media tab in HA but it wouldn’t load. The only thing I’ve added to that page today was the Mini Media Player. I think it is the only page with anything related to HACs on it.
I checked the logs and noticed that HACs was again rate limited.
I logged into Github and checked the Authorized OAuth Apps and I can see this:
HACS
Last used within the last week · Owned by hacs
I went to: ‘https://api.github.com/rate_limit’
and here are the results: {"resources": {"core":"limit":60,"remaining":59,"reset":1623251777,"used":1,"resource":"core"}, "graphql":"limit":0,"remaining":0,"reset":1623251785,"used":0,"resource":"graphql"}, "integration_manifest":"limit":5000,"remaining":5000,"reset":1623251785,"used":0,"resource":"integration_manifest"}, "search":"limit":10,"remaining":10,"reset":1623248245,"used":0,"resource":"search"}}, "rate":{"limit":60,"remaining":59,"reset":1623251777,"used":1,"resource":"core"}}
You mentioned getting information from the Info Page. Where do I find the Info Page?
I have the same issue. Just installed hacs for the first time yesterday. Seemed to install fine per the guide. Went to install the circadian lighting repo and it just spun.
For hours.
Overnight
Next morning it isn’t installed and I am rate limited. It has been 9 hours now and the rate limit has not gone away
This is a new install fully patched with Debian also fully patched underneath it
I’ve had problems with HACS ratelimiting every now and then from the very beginning but it’s only gotten worse even though it’s been a known problem for a long time. The extreme spikes in Github calls from HACS that happens all the time is annoying at best but maybe I wouldn’t really care if it actually recovered, but it doesn’t. My HACS tells me it will recover within 1 hour. It has currently shown that message for over a week.
Maybe, just maybe, it makes sense to poll all those thousands of repos upon the initial installation (although that seems like asking for trouble). But thousands and thousands of calls every day even though I’m not even interacting with HACS in any way? I really don’t get it. Many people have asked about this but I’ve not seen any clear answer. All I see is “fixes” that tries to avoid Github’s limit by lowering the calls slightly, but no attempt to fix the root cause.
Every HA restart is a lottery, sometimes HACS will initialize but most often it never does and mostly never recovers. There is nothing special about my installation and the Github account is dedicated to HACS. Reverting to a legacy YAML config, as some people recommend as a fix, seems kind of backwards and the documentation seems to not recommend this.
I could provide more detailed information but from what I can see many people have already provided that many times before to no avail so I don’t think it would help. As long as this is considered a feature rather than a bug or design flaw, I don’t see any reason to spend time debugging it.
Please do something with the rate limit issues, i trying to set up HACS for like 6 hours and always gets rate limited. Clone to a different server or something like.
I have the same issue today after downloading Node-Red custom_components, then I found that HACS and Node-Red use the same floder(custom_components)
So I try to delete the Node-Red custom_components/init.py , then restart HA.
It works , now working fine.
I am not sure if it was the solution to this problem, but can try.
Good luck.
Exact same issue. Fresh install on Home Assistant Blue. Tried to install Vivint custom config and got hit with the error telling me it will recover in an hour. Still says the same thing the next morning.
