I must say that is seriously off-topic. Maybe it’s time to quit Facebook 
Anyway, I absolutely hate “Something went wrong” error messages. What are you supposed to do with that? Good luck fighting the automated systems. 
Looks like there is something that causes hacs startup tasks to hang for some users.
1 Like
Thanks for the links, that helps! 
I’ll open an issue at HACS.
EDIT:
Here we go, please add a thumbs up to this issue, if you have it as well! Thanks!
I already got an answer on th issue, Ludeeus thinks, it’s an IPv6 issue…
If that’s the case, I’m out and will have to live with this error. I have done so much work with these f*** IPv6 settings - I’m done with it!
I can’t disable IPv6 in HA, Proxmox isn’t helpful in any way, so for me it’s filtering the message in the log and that’s it.
EDIT:
#config/configuration.yaml
logger:
default: WARNING
filters:
homeassistant.core:
- "Something is blocking Home Assistant from wrapping up"
Same error here since 2024.5. In my case, the cause is “edata” integration.
I have already opened an issue for this integration. I will follow this topic in case somebody finds a solution.
I believe that’s the new Frontend for HACS, also known as HACS 2.0.
You could switch back & forth between versions by toggling the Enable Experimental Features checkbox in the Integration Settings page in the past. Not sure if the new version has become the default now though.
Remember to restart HA after toggling the ‘enable experimental features’
1 Like
Aha, you were right. But I can’t remember why I ticked off the experimental features in the first place ? There must have been a reason why I did that…
Anyway - thanks for helping.
1 Like
I noticed today that every update sensor provided by the HACS integration is now unavailable. I can’t help thinking that this is a direct result of the “Something is blocking HA wrap up” error.
Anyone else seeing the same ?
Thanks for the pics, I already used that design.
In my case disabling IPv6 in my router did the trick. I couldn’t disable IPv6 in HA-OS, so I choose the “nuclear option” and disabled it completly. This is not a solution per se, but for now, I can live with it, until I find the time to properly solve that.
Maybe you should check that as well, I can imagine how a not working IPv6 could impact HACS in a more general way.
I can’t see how this problem in any way can be related to IPv6 ?!?
I have never had IPv6 enabled anywhere. Not in my router, nor in my NAS or any of my clients which all use NAT’ed IPv4 adresses.
Yet still I have this error after updating HA to 2024.5.x
Having the following Warning
Logger: homeassistant.core
Source: core.py:563
First occurred: 19:41:53 (1 occurrences)
Last logged: 19:41:53
Something is blocking Home Assistant from wrapping up the start up phase. We’re going to continue anyway. Please report the following info at https://github.com/home-assistant/core/issues: switch, diagnostics, upnp.binary_sensor, matter.lock, network, tapo_control.select, wyoming.switch, google.calendar, homeassistant_green, analytics, energy.sensor, tplink.light, logbook, valve, hacs.switch, go2rtc, homeassistant_hardware, siren, hassio.binary_sensor, tplink.select, google_assistant, cloud.binary_sensor, mqtt.select, zone, assist_pipeline, config, script, my, mobile_app.sensor, mqtt.binary_sensor, api, matter.switch, input_number, ifttt, matter.cover, sonos.binary_sensor, matter.number, onboarding, update, tts, number, tapo_control.switch, tapo_control.sensor, sensor, system_health, recorder, nest, wyoming.assist_satellite, ssdp, energy, cloud.tts, counter, matter.fan, usb, cast.media_player, met.weather, cloud, sonos.media_player, auth, input_datetime, hassio.update, tapo_control.binary_sensor, input_boolean, mobile_app.binary_sensor, light, tplink.switch, matter.sensor, tplink.button, stt, google_assistant_sdk.notify, nest.event, search, webhook, mqtt.switch, hassio, ffmpeg, schedule, climate, radio_browser, matter.select, input_button, upnp, google_assistant_sdk, dhcp, sonos, system_log, default_config, calendar, intent, mobile_app.device_tracker, nest.climate, persistent_notification, github, cast, file_upload, frontend, person, media_source, websocket_api, ipp.sensor, sun.sensor, application_credentials, conversation, homeassistant_sky_connect, nest.sensor, media_player, sonos.sensor, google, mobile_app, tapo_control.button, repairs, assist_satellite, sonos.switch, scene, weather, todo, logger, github.sensor, mqtt.button, systemmonitor.sensor, tapo_control.siren, cloud.stt, matter.binary_sensor, cover, matter.event, shopping_list, select, tplink.climate, tapo_control.light, timer, tplink.number, homeassistant, mqtt, hacs, tapo_control.number, camera, tplink.binary_sensor, wake_word, shopping_list.todo, blueprint, trace, onvif, wyoming.select, button, lovelace, fan, ipp, matter.valve, homeassistant_alerts, input_select, systemmonitor, history, mobile_app.notify, hacs.update, notify, matter.update, systemmonitor.binary_sensor, device_automation, automation, matter.button, binary_sensor, tapo_control, matter.vacuum, hardware, matter.climate, vacuum, hassio.sensor, bluetooth, met, nest.camera, zeroconf, homeassistant.scene, backup, device_tracker, sun, tplink, event, mqtt.sensor, upnp.sensor, tag, input_text, wyoming.number, wyoming, http, tplink.sensor, lock, wyoming.binary_sensor, matter, tapo_control.camera, stream, tplink.fan, sonos.number, matter.light, image_upload, tapo_control.update, tplink.siren The system is waiting for tasks: {<Task pending name=‘Task-608’ coro=<AbstractConfig.async_initialize..sync_google() running at /usr/src/homeassistant/homeassistant/components/google_assistant/helpers.py:114> wait_for=<_GatheringFuture pending cb=[Task.task_wakeup()]> cb=[set.remove()]>}
New to HA and new to coding. Any help would be appreciated.
Its google_assistant from the looks of it. Please open a GitHub issue report.
I just noticed the same error today as @MikelTuam2024 and the last line also points to google_assistant.