I updated to 2025.5 but when I restarted system HACS no longer start up. I checked logs and it shows this:
Logger: homeassistant.config_entries
Vir: config_entries.py:749
Prva pojavitev: 08:56:32 (2 pojavitvi)
Nazadnje zabeleženo: 08:58:51
Error setting up entry for hacs
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 749, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/hacs/__init__.py", line 246, in async_setup_entry
setup_result = await async_initialize_integration(hass=hass, config_entry=config_entry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/hacs/__init__.py", line 214, in async_initialize_integration
await async_try_startup()
File "/config/custom_components/hacs/__init__.py", line 201, in async_try_startup
startup_result = await async_startup()
^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/hacs/__init__.py", line 170, in async_startup
async_register_frontend(hass, hacs)
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^
File "/config/custom_components/hacs/frontend.py", line 58, in async_register_frontend
hass.components.frontend.async_register_built_in_panel(
^^^^^^^^^^^^^^^
AttributeError: 'HomeAssistant' object has no attribute 'components'
Is there any known solution to this ? If i restore backup to older edition it works normaly.
HAOS is running on intel nuc150.
I had a similar problem. I could go to Developer tools and could get an option to restart HA, but no option to reboot the system. I finally disconnected the ethernet cable (my system is a HA Yellow with POE), and after rebooting the system, everything works like it should.
Finally get it working, after i manage to instal V2. of HACS. Was not a easy task en not very clear how to do it But via the hacs.xyz web site it works on the end. Take at least 5 hours trial and error…
I’d been putting off upgrading HACS to the 2.x release since I had a Lenovo clock that did not like the updated versions of specific packages. Didn’t see anything in breaking changes, but maybe I missed that, so updated HA to 2025.5.1 and then HACS refused to start. Deleting and re-adding HACS just brought me back to a 1.x release. As @PdeRuiter pointed out (but didn’t provide steps), this took a minute to resolve. Steps are below that worked for me, irritating start to the day but my dashboards are all working again at least.
Go to the downloading page on hacs.xyz, click My Link to open HA add-on prompt, install Get-HACS add-on, set add-on to start at boot, restart HA, go to Add-ons → Get HACS → Logs tab and verify that it’s downloading HACS. Once complete, this installed HACS 2.0.5 for me and I saw a long list of HACS packages to update. You can remove the Get-HACS add-on after this.
Thank you. I’m following your steps, but it’s stuck on the “waiting for device activation” page now. I’ve added the activation code to github and got the confirmation that it was correct, but the page in HA just doesn’t change. It’s circling on “waiting for device activation” for a while now. Any idea what to do? Or does this take a while?
I had a similar issue. I am on Starlink which uses a CGNAT (IP is shared with multiple devices). I had to temporarily route my home assistant through a VPN to allow the authentication to work. I would check to see if your service provider uses CGNAT.
one more thing: if you’re like me and removed the old defunct HACS manually before doing the steps described above you will need to add the HACS manually again after the addon completes its job. otherwise the integration won’t show up.
Hi thanks for getting back to me. I found another thread that suggested to wait a while and try again because something somewhere might be getting too many requests. I finally did that after it failed to complete about half a dozen times. Waited an hour or two and then it worked within seconds
Thank you @mclardass. Tried a number of things to upgrade from a 1.x version without success. This worked perfectly. Extra points for providing the stpes and links.