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

[fft1010]

The problem

HI, line 6 put me here:

2024-05-08 15:07:36.814 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
2024-05-08 15:07:37.144 WARNING (ImportExecutor_0) [homeassistant.helpers.typing] HomeAssistantType was used from dwd_weather, this is a deprecated alias which will be removed in HA Core 2025.5. Use homeassistant.core.HomeAssistant instead, please report it to the author of the 'dwd_weather' custom integration
2024-05-08 15:07:42.744 WARNING (ImportExecutor_0) [homeassistant.helpers.typing] HomeAssistantType was used from dwd_weather, this is a deprecated alias which will be removed in HA Core 2025.5. Use homeassistant.core.HomeAssistant instead, please report it to the author of the 'dwd_weather' custom integration
2024-05-08 15:07:42.750 WARNING (ImportExecutor_0) [homeassistant.helpers.typing] HomeAssistantType was used from dwd_weather, this is a deprecated alias which will be removed in HA Core 2025.5. Use homeassistant.core.HomeAssistant instead, please report it to the author of the 'dwd_weather' custom integration
2024-05-08 15:07:45.865 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.helpers.event. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from event directly at custom_components/hacs/base.py, line 642: self.hass.helpers.event.async_track_time_interval(, please create a bug report at https://github.com/hacs/integration/issues
2024-05-08 15:08:00.865 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: mobile_app.notify, shelly.event, relative_brightness_light_group.light, analytics, search, update, history, sun.sensor, notify, input_boolean, radio_browser, unifi.device_tracker, upnp, espsomfy_rts.binary_sensor, unifi.switch, image, mobile_app.binary_sensor, dwd_weather.sensor, cloud, mobile_app, text, google_translate, mobile_app.sensor, unifi.image, dwd_weather_warnings.sensor, scene, homeassistant.scene, espsomfy_rts.button, dhcp, rest, input_number, unifiprotect.switch, version, espsomfy_rts.cover, logger, shelly.light, bthome.binary_sensor, input_select, unifiprotect.button, auth, diagnostics, shopping_list.todo, unifiprotect, shelly.binary_sensor, mqtt.binary_sensor, cloud.binary_sensor, energy.sensor, utility_meter, script, hassio, lock, dwd_weather.weather, group.cover, upnp.sensor, fritz.switch, valve, bluetooth_adapters, device_tracker, bthome.event, weather, person, onboarding, input_button, api, espsomfy_rts.sensor, wake_word, timer, shelly, cover, binary_sensor, template.sensor, camera, unifiprotect.camera, network, fritz.device_tracker, climate, unifiprotect.lock, system_log, button, unifiprotect.select, unifiprotect.text, input_datetime, hacs, energy, my, application_credentials, unifi, hassio.binary_sensor, bluetooth, google_translate.tts, hacs.update, webhook, websocket_api, shelly.sensor, shelly.cover, light, ffmpeg, hassio.update, cast, system_health, media_player, sensor, trace, backup, unifiprotect.light, frontend, upnp.binary_sensor, mqtt, dwd_weather_warnings, default_config, event, usb, zone, espsomfy_rts.switch, cloud.stt, blueprint, group, file_upload, tts, squeezebox.media_player, persistent_notification, stt, fritz.sensor, bthome, squeezebox, automation, sun, unifiprotect.sensor, version.binary_sensor, select, shelly.update, intent, config, map, espsomfy_rts, version.sensor, fritz.binary_sensor, kodi, zeroconf, unifiprotect.media_player, shopping_list, repairs, bthome.sensor, logbook, shelly.valve, dwd_weather, homeassistant_alerts, ssdp, conversation, dlna_dms, fritz.button, shelly.climate, espsomfy_rts.update, co2signal.sensor, met.weather, homeassistant, lovelace, switch, http, co2signal, mobile_app.device_tracker, recorder, media_source, shelly.button, number, unifiprotect.number, hassio.sensor, kodi.media_player, utility_meter.sensor, assist_pipeline, tag, shelly.switch, schedule, stream, image_upload, hardware, template, unifi.update, unifiprotect.binary_sensor, cloud.tts, rest.sensor, mqtt.sensor, fritz, todo, dwd_weather.camera, unifi.button, unifi.sensor, cast.media_player, device_automation, counter, met, hacs.sensor, input_text, fritz.image, fritz.update The system is waiting for tasks: {<Task pending name='Task-1995' coro=<async_discover() running at /usr/local/lib/python3.12/site-packages/pysqueezebox/discovery.py:98> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>}
2024-05-08 15:08:03.957 WARNING (MainThread) [homeassistant.components.kodi.media_player] Unable to connect to Kodi via websocket
2024-05-08 15:10:33.339 WARNING (MainThread) [homeassistant.components.utility_meter.sensor] Wasser received an invalid new state from sensor.watermeter_raw : 0004N.3501
2024-05-08 15:15:33.431 WARNING (MainThread) [homeassistant.components.utility_meter.sensor] Wasser received an invalid new state from sensor.watermeter_raw : 0004N.3566

What version of Home Assistant Core has the issue?

core-2024.5.2

What was the last working version of Home Assistant Core?

core-2024.4.4 (poretty sure) I left our 5.1 and 5.0

What type of installation are you running?

Home Assistant OS

Integration causing the issue

I don't know

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?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @onfreund, mind taking a look at this issue as it has been labeled with an integration (kodi) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `kodi` 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 kodi` 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)}}

---

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

[bdraco]

likely https://github.com/home-assistant/core/issues/47828

[bdraco]

I just tried to replicate the kodi issue and I can't anymore so maybe something else

[fft1010]

Hi, If someone tells me how to have a more detailed logfile, I could try to provide it. The System is not tooooo overcrowded, so there might be a chance. I also wonder why this exists, as I de-activated kodi to try out something different. I just checked my HA configuration and saw that i have a configured kodi device and a de-activated kodi.

(I did de-aktivate kodi, to try out something and I doubt I will use it with HA.) But I assumed, de-activating will also take away all "kodi devices", ..?!? Or what am I doing wrong?

thanks Juergen

[bdraco]

The system is waiting for tasks: {<Task pending name='Task-1995' coro=<async_discover() running at /usr/local/lib/python3.12/site-packages/pysqueezebox/discovery.py:98> wait_for= cb=[set.remove()]>}

I didn't scroll over enough the first time I looked since the line is very long and hidden

It's squeezebox not marking discovery as a background task

[home-assistant[bot]]

Hey there @rajlaud, mind taking a look at this issue as it has been labeled with an integration (squeezebox) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `squeezebox` 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 squeezebox` 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)}}

---

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

[bdraco]

Can be fixed by changing

https://github.com/home-assistant/core/blob/9655db3d558b2d03399ca78f719bafed96f891cd/homeassistant/components/squeezebox/media_player.py#L113

To use async_create_background_task