issue-triage-workflows[bot]
commented
1 month ago There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
The problem
2024-05-21 16:53:58.427 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: rademacher.light, fritzbox.light, water_heater, todo, fritzbox, map, radio_browser, google_translate.tts, influxdb, min_max, cloud.tts, homeassistant_alerts, input_number, update, automation, met, rademacher, counter, event, upnp.binary_sensor, fritz, shelly.event, frontend, switch, mobile_app.binary_sensor, default_config, vicare.climate, tibber.notify, script, zone, epex_spot, weather, shopping_list.todo, template.binary_sensor, device_automation, recorder, light, fritzbox.sensor, derivative, sensor, rademacher.climate, input_select, input_text, homeassistant, modbus.sensor, ipp, input_datetime, logger, mqtt, upnp, epex_spot.sensor, webostv.notify, rademacher.switch, vacuum, assist_pipeline, lawn_mower, fritz.update, hassio.binary_sensor, hassio, input_boolean, shelly.button, dwains_dashboard.sensor, rademacher.scene, image_upload, ffmpeg, mqtt.sensor, scheduler, rademacher.button, binary_sensor, mobile_app.device_tracker, rest, notify, dhcp, rest.sensor, gardena_smart_system, intent, number, gardena_smart_system.vacuum, sun.sensor, history, bluetooth_adapters, upnp.sensor, homeassistant.scene, stt, vicare.number, config, bthome.sensor, application_credentials, forecast_solar.sensor, stream, device_tracker, cast, ipp.sensor, sun, trace, fritzbox.binary_sensor, rademacher.sensor, websocket_api, min_max.sensor, fritz.switch, api, file_upload, hassio.update, google_translate, http, template.sensor, backup, cast.media_player, media_source, shelly.switch, button, shelly, rademacher.binary_sensor, lovelace, shelly.binary_sensor, dwains_dashboard, rademacher.update, system_health, hardware, onboarding, shelly.cover, wake_word, forecast_solar, gardena_smart_system.sensor, vicare.water_heater, shelly.sensor, mobile_app, derivative.sensor, vicare.button, shopping_list, gardena_smart_system.binary_sensor, fritzbox.button, vicare, fritz.binary_sensor, ssdp, fritz.image, dlna_dmr, schedule, tts, fritz.device_tracker, repairs, webhook, analytics, cloud, dlna_dms, rpi_power.binary_sensor, energy, bthome, met.weather, energy.sensor, mobile_app.sensor, rpi_power, rademacher.number, network, hassio.sensor, bluetooth, cover, input_button, shelly.update, vicare.sensor, media_player, vicare.binary_sensor, system_log, fritzbox.cover, persistent_notification, rademacher.cover, logbook, scheduler.switch, fritzbox.switch, bthome.event, fritz.sensor, climate, hacs, shelly.climate, mobile_app.notify, dlna_dmr.media_player, gardena_smart_system.switch, person, scene, modbus, tibber, diagnostics, my, blueprint, fritz.button, tibber.sensor, hacs.sensor, usb, conversation, webostv, raspberry_pi, zeroconf, bthome.binary_sensor, template, webostv.media_player, shelly.light, image, search, auth, timer, tag, fritzbox.climate The system is waiting for tasks: {<Task pending name='Task-3550' coro=<HacsBase.startup_tasks() running at /config/custom_components/hacs/base.py:695> wait_for=<_GatheringFuture pending cb=[Task.task_wakeup()]> cb=[set.remove()]>} 2024-05-21 16:53:58.476 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error initializing 'Bad-Dauerbetrieb' trigger: In 'numeric_state' condition: unknown entity sensor.vicare_outside_temperature
What version of Home Assistant Core has the issue?
System Information version | core-2024.5.4 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.12.2 os_name | Linux os_version | 6.6.28-haos-raspi arch | aarch64 timezone | Europe/Berlin config_dir | /config
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | failed to load: timeout GitHub Web | ok GitHub API Calls Remaining | 4709 Installed Version | 1.34.0 Stage | running Available Repositories | 1461 Downloaded Repositories | 23Home Assistant Cloud
logged_in | false -- | -- 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 | 468.7 GB disk_used | 44.9 GB healthy | true supported | true board | rpi4-64 supervisor_api | ok version_api | ok installed_addons | File editor (5.8.0), Samba share (12.3.1), Terminal & SSH (9.14.0), Grafana (10.0.0), InfluxDB (5.0.0), Node-RED (17.0.12), Mosquitto broker (6.4.0), MQTT Explorer (browser-1.0.1)Dashboards
dashboards | 9 -- | -- resources | 7 views | 13 mode | storageRecorder
oldest_recorder_run | 5. März 2024 um 16:59 -- | -- current_recorder_run | 21. Mai 2024 um 16:47 estimated_db_size | 10200.91 MiB database_engine | sqlite database_version | 3.44.2What was the last working version of Home Assistant Core?
2024.5.3
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?
Additional information
No response