Initial startup

HACS does not ship with any knowledge about the repositories it is supposed to show.

Since there is no central "HACS server", every installation of HACS fetches this information from GitHub, it has to get the information about all default repositories

To get the information that is needed to show a representation of the repository in HACS, HACS uses the GitHub API, this API is rate limited and when you hit that rate limit HACS will pause any communitation to the GitHub API until the rate limit reset (can take up to one hour).


For new installation of HACS with the current amount of default repositories you will hit that rate limit on the initial startup after installing HACS. Because of this HACS will be in a "Starting up" state until it's done fetching the information for all default repositories

Which in return will cause the initial startup of HACS to take over 1 hour to finish.

Last updated on