Unable to Successfully Integrate HACS into Latest version of HAC and Home Assistant

[rmschaller]

System Health details

I followed the link above, but I can't find where to copy and paste the system info. I mentioned all the version numbers of software that I could find.

Checklist

• I'm running the newest version of HACS https://github.com/hacs/integration/releases/latest
• I have enabled debug logging for my installation.
• I have filled out the issue template to the best of my ability.
• I have read https://hacs.xyz/docs/help/issues/
• This issue is related to the backend (integration part) of HACS.
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
• This is a bug and not a feature request.
• This issue is not a duplicate issue of currently open or issues pending release.

Describe the issue

After updating Home Assistant Core and OS, Here are the versions I'm running.
Core: 2026.4.2
Supervisor: 2026.04.0
Operating system: 17.2
Frontend: 20260325.7
HACS: 1.27.2

HACS was failing to properly initialize. I deleted the HACS integration and reinstalled it with the same result. I enabled debugging and reloaded HACS and Got the following Log error:

Logger: homeassistant.config_entries
Source: config_entries.py:769
First occurred: 9:36:27 PM (3 occurrences)
Last logged: 10:27:16 PM

Error setting up entry for hacs
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 769, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/hacs/init.py", line 220, in async_setup_entry
setup_result = await async_initialize_integration(hass=hass, config_entry=config_entry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/hacs/init.py", line 206, in async_initialize_integration
await async_try_startup()
File "/config/custom_components/hacs/init.py", line 193, in async_try_startup
startup_result = await async_startup()
^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/hacs/init.py", line 162, in async_startup
async_register_frontend(hass, hacs)
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^
File "/config/custom_components/hacs/frontend.py", line 25, in async_register_frontend
hass.http.register_static_path(f"{URL_BASE}/themes", hass.config.path("themes"))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'HomeAssistantHTTP' object has no attribute 'register_static_path'. Did you mean: 'async_register_static_paths'?

Reproduction steps

1.Boot Home Assistant
2.Monitor the start up of HACS and note errors produced
3. Enable error logging for HACS
Please contact me for other supporting debugging info.
Rob

home-assistant_2026-04-17T03-53-43.130Z.log

...

Debug logs

See attached

Diagnostics dump

Cannot locate the "Download diagnostics" from the menu that result from selecting the three dots when the HACS integration was selected

[hacs-bot]

Thank you for opening an issue in the HACS.

Before proceeding, please verify the following:

Select the correct issue template:
HACS provides different templates for different types of bugs. Choosing the right template ensures you're asked the right questions and helps route your bug appropriately.

Complete the ENTIRE issue template:
Make sure you've read the issue guidelines and filled out every single field in the issue template, even if some fields seem unrelated to your specific situation.

Fill out everything, even if it seems unnecessary:
Don't skip fields because they "don't seem relevant" to your bug. The template asks for specific information because:

• Problems often have unexpected causes that surface through "unrelated" details
• What seems unrelated to you might be the key to solving your bug
• Incomplete information requires follow-up questions, delaying resolution
• The template is designed based on years of troubleshooting experience
• Missing information forces those helping to make assumptions, which can lead to wrong solutions

Issues with incomplete templates take significantly longer to resolve or may be closed without resolution.

If you're experiencing a similar bug:
If your bug is identical to an existing one, please:

• Add a 👍 reaction to the original issue description
• Subscribe to notifications on that issue to stay updated
• Do not add comments like "same here", "I have this too", or "+1"

Adding duplicate comments creates noise and makes it harder to track and resolve issues. Reactions help prioritize issues based on how many users are affected.

Getting help:
If you need assistance filling out the template or understanding your issue:

• Issue Guidelines - Detailed instructions for reporting issues
• HACS Discord - Community support and real-time help

What happens next:
Maintainers and community members will review your issue and may:

• Ask for additional information if the template is incomplete
• Provide a solution or workaround
• Label the issue appropriately for tracking
• Link it to related issues or pull requests