Something is blocking Home Assistant from wrapping up the start up phase

[poulanker]

The problem

I checked the logs, after installing HA core 2024.11.0 and found the message shown below.

What version of Home Assistant Core has the issue?

core-2024.11.0

What was the last working version of Home Assistant Core?

core-2024.10.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

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: diagnostics, synology_dsm.binary_sensor, home_connect_alt.time, samsungtv, dlna_dmr.media_player, thermal_comfort, nest, ibeacon, kia_uvo.lock, nest.sensor, onkyo.media_player, zha.update, panel_custom, synology_dsm.switch, zha.button, alarmo.alarm_control_panel, group.light, shelly.select, met.weather, hacs.update, shelly.valve, counter, automation, mqtt.button, recorder, spook.event, calendar, zha.climate, zha_toolkit, fan, watchman.sensor, input_datetime, shelly.button, xiaomi_ble.sensor, watchman, dlna_dmr, zaptec.switch, systemmonitor.binary_sensor, go2rtc, spook.select, update, shelly, zaptec.binary_sensor, hacs.switch, spook.sensor, shelly.climate, google_cloud.stt, xiaomi_ble, shelly.text, input_text, system_health, hassio.binary_sensor, powercalc, template.binary_sensor, zone, synology_dsm.sensor, trace, wyoming, switch, mass.media_player, usb, application_credentials, repairs, lovelace, ssdp, time, synology_dsm.camera, group.sensor, alarm_control_panel, siren, google_translate.tts, ipp, nest.camera, wake_word, history, homeassistant_hardware, homeassistant.scene, battery_notes.sensor, samsungtv.remote, cloud, ipp.sensor, synology_dsm.button, webostv.notify, bodymiscale.sensor, frontend, kia_uvo.binary_sensor, file_upload, battery_notes.binary_sensor, home_connect_alt.binary_sensor, synology_dsm, energidataservice, ibeacon.device_tracker, valve, webostv.media_player, weather, zaptec.sensor, bluetooth_adapters, zha.select, spook.switch, esphome.number, input_select, config, remote, home_connect_alt, text, esphome, home_connect_alt.switch, number, group.binary_sensor, wyoming.tts, device_automation, mqtt.sensor, switch_as_x, sql.sensor, derivative.sensor, cloud.binary_sensor, sun, local_calendar, switch_as_x.fan, google_assistant, intent, mobile_app, onboarding, shelly.sensor, esphome.sensor, homeassistant, hassio.sensor, shelly.binary_sensor, zaptec.button, template.sensor, google_cloud, kia_uvo, event, logger, sql, assist_satellite, energidataservice.sensor, default_config, hacs, shelly.update, thread, zha.sensor, mobile_app.sensor, zaptec.lock, bluetooth, schedule, webhook, shelly.event, influxdb, ffmpeg, zha.fan, nest.climate, logbook, zha.number, zha.lock, persistent_notification, zaptec.number, analytics, backup, zha.device_tracker, http, battery_notes.button, climate, kia_uvo.sensor, cloud.stt, light, input_boolean, group.media_player, androidtv_remote.media_player, hassio.update, battery_notes, wyoming.stt, network, notify, image_upload, group, mobile_app.binary_sensor, dhcp, esphome.button, xiaomi_ble.event, kia_uvo.number, home_connect_alt.sensor, spook.number, websocket_api, homeassistant_sky_connect, cast.media_player, systemmonitor.sensor, radio_browser, zaptec, shelly.number, lock, home_connect_alt.button, xiaomi_ble.binary_sensor, conversation, camera, upnp, zha.siren, shelly.cover, synology_dsm.update, media_source, zha.light, system_log, switch_as_x.light, webostv, wyoming.wake_word, ibeacon.sensor, energy, spook.time, assist_pipeline, stt, samsungtv.media_player, input_number, timer, esphome.update, affalddk.sensor, utility_meter, button, bodymiscale, google_cloud.tts, shelly.switch, home_connect_alt.number, cloud.tts, derivative, template, select, systemmonitor, nest.event, media_player, mqtt, mobile_app.device_tracker, alarmo, zha.cover, hassio, stream, hardware, met, google_translate, home_connect_alt.select, homeassistant_alerts, my, auth, cover, spook, tag, input_button, zaptec.update, search, androidtv_remote, spook.binary_sensor, scene, octoprint, zha.alarm_control_panel, affalddk, energy.sensor, kia_uvo.device_tracker, spook.button, local_calendar.calendar, affalddk.calendar, zha.switch, device_tracker, shelly.light, powercalc.sensor, blueprint, manual.alarm_control_panel, person, thermal_comfort.sensor, zeroconf, tts, api, mass, cast, androidtv_remote.remote, zha, script, wake_on_lan, onkyo, mobile_app.notify, hass_agent, zha.binary_sensor, sensor, binary_sensor, sun.sensor The system is waiting for tasks: {<Task pending name='Task-2369' coro=<AbstractConfig.async_initialize.<locals>.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()]>}

Additional information

I actually installed 2024.11.0 yesterday just after having watched the 2024.11 release party on youtube.
That did not go as planned. No zigbee devices were working and the log mentioned that my SkyConnect could not be configured.
I had to restore the 2024.10.4 backup immediately thereafter, otherwise I would get into trouble with my spouse in the morning :-)
Now, 24 hours later it was time to try installing again. Everything seems to work just fine, but I found said message in the log, and filed the issue as requested.

[smarthomefamilyverrips]

Same on 2014.10.3, it is google assistant causing this error, also are a few duplicate issues that are the same.

#130154
#130201

[Anto79-ops]

Hello, I just got this message this morning. If you look at the last few lines of that error message, it'll tell you what's the cause of this. Can somebody please put the Google Assistant label on this issue? This should help with notifying the dev.

This is what is said at the end of my message.

 The system is waiting for tasks: {<Task pending name='Task-4680' coro=<AbstractConfig.async_initialize.<locals>.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()]>}

[home-assistant]

Hey there @home-assistant/cloud, mind taking a look at this issue as it has been labeled with an integration (google_assistant) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of google_assistant can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign google_assistant Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

google_assistant documentation
google_assistant source
_{^{(message by IssueLinks)}}

[ikearvell]

I have 42 Google devices and perhaps the sync is taking too long and is timing out. The issue just started for me with 2024.11.0 and effect is effectively fatal. Scripts to play music have huge delays (around 10 minutes) and yesterday, I asked Google to open the garage door (via a HA script) and nothing happened. Then, my garage door opened 12 minutes after I left the house and stayed open until I returned a few hours later (I'll add safety scripts later). ALL HACS integrations had been previously removed, all config/custom_components folders are deleted. My log message is basically the same ( sync_google() and I also have a Rachio issue which I believe is unrelated to the problem. But also note the log message:

WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 14: Stream refused by server.

I tried deleting my Google Cast integration and then re-added. This normally takes about 20 seconds to find all 42 Google devices but took about 30 minutes to find only 40 of the 42 devices.

My network is Unifi and the health is perfect and my firewall is pfsense and it too is working fine. All direct internet (i.e. YouTube) is working fine.

From my logs:

2024-11-10 13:30:50.474 WARNING (MainThread) [homeassistant.core] 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: schlage.binary_sensor, notify, repairs, select, dhcp, mobile_app.device_tracker, onvif.sensor, schedule, mobile_app.binary_sensor, tplink.button, tag, mqtt.button, search, input_select, system_health, bluetooth_adapters, scene, shelly.select, assist_satellite, tplink.siren, backup, shelly.light, default_config, cloud.binary_sensor, tplink.binary_sensor, homeassistant.scene, fan, script, websocket_api, lovelace, cloud.tts, bond.cover, broadlink.sensor, wyoming, plex.update, stream, local_calendar.calendar, cast, device_automation, rachio, energy.sensor, zeroconf, webhook, logbook, wake_word, counter, update, mqtt.alarm_control_panel, shelly.button, wemo.sensor, bond.fan, lg_thinq, lg_thinq.vacuum, shelly.text, valve, rachio.calendar, wemo.binary_sensor, network, persistent_notification, shelly.valve, cast.media_player, wemo.switch, binary_sensor, switch, onvif.camera, google_assistant, tplink.number, auth, shelly.number, automation, shelly, mqtt.switch, timer, intent, input_datetime, trace, homekit_controller.binary_sensor, file_upload, ssdp, usb, stt, onvif.button, mqtt.sensor, broadlink, tplink.fan, homekit_controller.camera, shelly.cover, hassio.sensor, homekit_controller, schlage.select, input_text, plex, text, input_button, tplink.switch, homekit_controller.button, blueprint, lg_thinq.sensor, homekit_controller.climate, number, thread, tplink, hassio.binary_sensor, sensor, device_tracker, onvif, local_ip.sensor, tplink.climate, system_log, homeassistant_alerts, homekit_controller.fan, bluetooth, lg_thinq.select, shelly.climate, plex.sensor, shelly.update, lg_thinq.fan, mqtt.update, lg_thinq.number, bond, my, mqtt, homeassistant, go2rtc, hassio.update, energy, diagnostics, tplink.sensor, homekit_controller.event, mqtt.binary_sensor, calendar, config, broadlink.remote, plex.media_player, alarm_control_panel, lg_thinq.binary_sensor, lg_thinq.event, homekit_controller.sensor, image_upload, hardware, rachio.switch, history, http, button, vacuum, mqtt.number, cover, bond.switch, bond.button, plex.button, recorder, logger, sun.sensor, application_credentials, lg_thinq.climate, tplink.light, schlage, mobile_app.sensor, camera, tts, mobile_app, hassio, broadlink.switch, mobile_app.notify, api, mqtt.climate, shelly.event, cloud, shelly.sensor, homekit_controller.select, onvif.binary_sensor, remote, radio_browser, person, shelly.binary_sensor, siren, wyoming.tts, group.media_player, cloud.stt, input_number, group, frontend, local_calendar, lock, media_source, media_player, wemo, onvif.switch, assist_pipeline, ffmpeg, tplink.select, bond.light, homekit_controller.switch, onboarding, conversation, light, climate, schlage.switch, input_boolean, mqtt.select, event, sun, shelly.switch, schlage.sensor, zone, lg_thinq.switch, analytics, wake_on_lan, rachio.binary_sensor, local_ip, schlage.lock The system is waiting for tasks: {<Task pending name='Task-2008' 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()]>}
2024-11-10 13:49:21.703 WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 14: Stream refused by server
2024-11-10 14:18:38.230 WARNING (SyncWorker_24) [urllib3.connectionpool] Connection pool is full, discarding connection: api.rach.io. Connection pool size: 10
2024-11-10 14:18:38.235 WARNING (SyncWorker_21) [urllib3.connectionpool] Connection pool is full, discarding connection: api.rach.io. Connection pool size: 10
2024-11-10 14:18:38.236 WARNING (SyncWorker_15) [urllib3.connectionpool] Connection pool is full, discarding connection: api.rach.io. Connection pool size: 10
2024-11-10 14:18:38.237 WARNING (SyncWorker_20) [urllib3.connectionpool] Connection pool is full, discarding connection: api.rach.io. Connection pool size: 10
2024-11-10 14:18:38.249 WARNING (SyncWorker_6) [urllib3.connectionpool] Connection pool is full, discarding connection: api.rach.io. Connection pool size: 10
2024-11-10 14:49:22.138 WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 14: Stream refused by server

[HuismAndre]

Today no errors or warnings during a restart. Nothing changed over here (so it's probably a remote issue with Google)?

[ikearvell]

My messages have gone away as well on their own. Thank you Google.

[HuismAndre]

And the warning is back again. So I guess it's not "Thank you Google" time yet.

[antisane]

I'm getting the same error at startup, but the only Google integration I have installed is Google Calendar.

... 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()]>}

[antisane]

Disabling "Google Assistant" under "Voice Assistants" made the error go away.

[smarthomefamilyverrips]

Disabling "Google Assistant" under "Voice Assistants" made the error go away.

@antisane this also will stop homeassistant from working with Google Home, so I not think this is a really suitable solution for many of us, but thanks for the suggestion.

[thromer]

Some data from my logs below. It looks like google_assistant takes about 48 seconds to initialize, far more than 15 second budget Home Assistant allows before continuing. For my instance I'm not seeing any other messages or problems with the Google Assistant Voice Assistant once its initialization completes.

I'd guess it is the API call to https://homegraph.googleapis.com/v1/devices:requestSync (component source code here), but there isn't enough detail in the logs to say for sure, and I'm not sure how to drill down farther to confirm. I can't imagine why an API call would take so long; I don't have any WiFi or ISP issues. My hunch as to the underlying problem is that Google isn't very invested in the production health of this particular service.

2024-12-07 10:43:27.672 INFO (MainThread) [homeassistant.setup] Setting up google_assistant
...
2024-12-07 10:43:42.677 WARNING (MainThread) [homeassistant.core] Something is blocking Home Assistant from wrapping up the start up phase. We're going to continue anyway. Please report the following info ...  /usr/src/homeassistant/homeassistant/components/google_assistant/helpers.py:114 ...
...
2024-12-07 10:44:11.586 INFO (MainThread) [hass_nabucasa.google_report_state] Connected
2024-12-07 10:44:11.586 DEBUG (MainThread) [hass_nabucasa.google_report_state] Message sender task activated
2024-12-07 10:44:11.589 DEBUG (MainThread) [hass_nabucasa.google_report_state] Publishing message:
{'msgid': '3ebd6687467540f39a64293a32aa842c',
 'payload': {'devices': 
...
2024-12-07 10:44:15.445 DEBUG (MainThread) [hass_nabucasa.iot] Received message:
{'handler': 'google_actions',
 'msgid': 'f2888696-2a21-446f-86bd-e9abb9774e2e',
 'payload': {'inputs': [{'intent': 'action.devices.SYNC'}],
             'requestId': '4400392825331484484'}}
2024-12-07 10:44:15.445 DEBUG (MainThread) [homeassistant.components.cloud.client] Received cloud message 4400392825331484484
2024-12-07 10:44:15.446 DEBUG (MainThread) [homeassistant.components.google_assistant.smart_home] Processing message:
{'inputs': [{'intent': 'action.devices.SYNC'}],
 'requestId': '4400392825331484484'}
2024-12-07 10:44:15.446 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event google_assistant_sync[L]: request_id=4400392825331484484, source=cloud>
2024-12-07 10:44:15.448 DEBUG (Recorder) [homeassistant.components.recorder.core] Processing task: <Event google_assistant_sync[L]: request_id=4400392825331484484, source=cloud>
2024-12-07 10:44:15.449 DEBUG (SyncWorker_6) [homeassistant.helpers.storage] Writing data for cloud to /config/.storage/cloud
2024-12-07 10:44:15.459 DEBUG (MainThread) [homeassistant.components.cloud.google_config] _async_prefs_updated
2024-12-07 10:44:15.459 DEBUG (MainThread) [homeassistant.components.google_assistant.helpers] async_enable_local_sdk
2024-12-07 10:44:15.471 DEBUG (MainThread) [homeassistant.components.google_assistant.smart_home] Response
{'agentUserId': '4999***012d',
 'devices': ...}
2024-12-07 10:44:15.482 DEBUG (MainThread) [hass_nabucasa.iot] Publishing message:
{'msgid': 'f2888696-2a21-446f-86bd-e9abb9774e2e',
 'payload': {'payload': {'agentUserId': 'XXXXXX',
                         'devices': [ ...
...
             'requestId': '4400392825331484484'}}
...
2024-12-07 10:44:55.914 DEBUG (MainThread) [hass_nabucasa.google_report_state] Received message:
{'msgid': '3ebd6687467540f39a64293a32aa842c',
 'payload': {'requestId': '3ebd6687467540f39a64293a32aa842c'}}

Edit: added some more relevant log entries that I'd elided. Notably messages from hass_nabucasa, so I wouldn't rule out issues on the Nabu Casa side instead of, or in addition to, the Google side.

[sayam93]

I am seeing this error in my logs too.

Could this be related to the below?

Local communication unavailable
Google devices will not be able to talk locally with Home Assistant, because you have configured an SSL certificate for your HTTP integration. [Learn more](https://www.nabucasa.com/config/google_assistant/#local-communication)

[gfn256]

Still not fixed in 2025.1.0