Closed Paddy0174 closed 4 months ago
Make sure you have read the issue guidelines and that you filled out the entire template.
If you have an issue identical to this, do not add comments like "same here", "i have this too", instead add a :+1: reaction to the issue description. Thanks! :+1:
Looks like you are having some network issues. Try disabling IPv6 and reboot the host.
That's unfortunate, because i can't disable (supervisor won't let me) IPv6. Seems like I'll have to live with it.
Thanks for taking a look! :)
Thi is not an IPv6 related issue. I run HA Core in a container on a NAS and IPv6 is completely disabled. Still I have the same issue.
If it's not IPv6, then it is something other network-related. Or you have something blocking too much, >60s for a single file download is not normal. Also, from the lineshifts here, it more look like HACS is a side effect not the cause (like with google assistant, but as that is core and this is not it was only considered there). When you fix/remove what is blocking/limiting/hindering your network requests, this will most likely be resolved everywhere.
On the off chance it continues once that is fixed, recreate this issue with updated (unfiltered) logs from the entire startup, and the system health details.
Maybe this can be of any help; I noticed that a following error has resulted in almost all integrations update entities are now unavailable:
System Health details
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 5000 Installed Version | 1.34.0 Stage | running Available Repositories | 1409 Downloaded Repositories | 38 HACS Data | okAccuWeather
can_reach_server | ok -- | -- remaining_requests | 23Home Assistant Cloud
logged_in | true -- | -- subscription_expiration | 4. Juni 2024 um 02:00 relayer_connected | true relayer_region | eu-central-1 remote_enabled | false remote_connected | false alexa_enabled | false google_enabled | false remote_server | eu-central-1-9.ui.nabu.casa certificate_status | ready instance_id | 40xxxxxxxxxxxxxxxxf71 can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 12.3 -- | -- update_channel | stable supervisor_version | supervisor-2024.05.1 agent_version | 1.6.0 docker_version | 25.0.5 disk_total | 30.8 GB disk_used | 19.0 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | Samba share (12.3.1), Mosquitto broker (6.4.0), ESPHome (2024.4.2), MariaDB (2.7.1), Grocy (0.21.0), Zigbee2MQTT (1.37.1-1), Home Assistant Google Drive Backup (0.112.1), Terminal & SSH (9.14.0), Piper (1.5.0), Whisper (2.0.0), File editor (5.8.0), openWakeWord (1.10.0)Dashboards
dashboards | 7 -- | -- resources | 20 views | 34 mode | yamlRecorder
oldest_recorder_run | 13. Mai 2024 um 02:58 -- | -- current_recorder_run | 15. Mai 2024 um 02:26 estimated_db_size | 602.25 MiB database_engine | mysql database_version | 10.11.6Checklist
Describe the issue
After a restart of HA, something's blocking the start up with the error shown in the logs, specifically
The system is waiting for tasks: {<Task pending name='Task-2116' coro=<HacsBase.startup_tasks() running at /config/custom_components/hacs/base.py:687> wait_for=<_GatheringFuture pending cb=[Task.task_wakeup()]> cb=[set.remove()]>}
. The line number changes from user to user, but is in the same +/- 10 lines.A little investigation shows, that the majority of users with this error have a warning line regarding HACS. There are some people, where the warning reads with specific integrations and it could be fixed by the authors of these integrations.
@bdraco already fixed one of these errors, for other integrations there are issues opened, see here:
Fixed error: https://github.com/home-assistant/core/pull/117331 Open issue 1: https://github.com/home-assistant/core/issues/117256 Open issue 2: https://github.com/home-assistant/core/issues/117194
Reproduction steps
Debug logs
Diagnostics dump
No response