search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
69.78k stars 28.93k forks source link

Something has blocked startup #118656

Open sandervanzutphen opened 1 month ago

sandervanzutphen commented 1 month ago

The problem

While restarting HomeAssistant this error log appears:

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: backup, humidifier, met.weather, bluetooth, mobile_app.notify, zha.button, mobile_app, reolink.siren, energyzero, sonos.switch, calendar, ssdp, sonos, hue.light, roborock.sensor, reolink.update, roborock.time, default_config, select, time, wallbox.sensor, netatmo.cover, mqtt, tibber, zha, smartthinq_sensors, device_tracker, schedule, tado.climate, hassio, stt, wallbox, weather, hue.binary_sensor, button, hacs.sensor, sun.sensor, mobile_app.binary_sensor, hassio.sensor, solis, hue.event, smartthinq_sensors.binary_sensor, smartthinq_sensors.humidifier, config, netatmo.fan, counter, input_text, homeassistant_yellow, zone, device_automation, homewizard.switch, smartthinq_sensors.water_heater, ffmpeg, input_button, tibber.sensor, unifi.image, netatmo.climate, camera, homewizard, image, input_datetime, roborock.button, assist_pipeline, zha.switch, zha.device_tracker, thread, unifi.device_tracker, solis.sensor, cast.media_player, wallbox.switch, ios.sensor, netatmo.binary_sensor, input_select, number, smartthinq_sensors.switch, netatmo.sensor, mobile_app.sensor, hassio.binary_sensor, mqtt.sensor, zeroconf, binary_sensor, sonos.binary_sensor, reolink.camera, sun, alarm_control_panel, zha.climate, siren, unifi.update, media_player, search, smartthinq_sensors.button, homeassistant_hardware, google_translate.tts, tradfri, cloud.tts, netatmo, lovelace, tradfri.light, hacs, zha.sensor, template.sensor, websocket_api, smartthinq_sensors.sensor, unifi.sensor, reolink.switch, switch, homeassistant_alerts, netatmo.select, input_number, nordpool, tradfri.fan, stream, reolink.button, roborock.vacuum, reolink.binary_sensor, zha.siren, reolink.number, homewizard.number, zha.lock, local_calendar.calendar, tibber.notify, zha.number, input_boolean, zha.fan, roborock, image_upload, wallbox.number, lock, tts, person, map, system_health, homewizard.sensor, vacuum, repairs, unifi.switch, dhcp, media_source, netatmo.switch, energy.sensor, sonos.media_player, recorder, roborock.image, tado, usb, reolink.sensor, auth, tado.device_tracker, unifi.button, trace, application_credentials, homeassistant.scene, template, http, logbook, wallbox.lock, zha.light, tado.binary_sensor, hue, onboarding, reolink, diagnostics, webhook, history, modbus.sensor, homewizard.button, energy, unifi, sonos_cloud, cover, homeassistant, zha.alarm_control_panel, network, climate, nordpool.sensor, local_calendar, logger, persistent_notification, script, ios.notify, light, hue.switch, smartthinq_sensors.light, ios, scene, frontend, hassio.update, conversation, smartthinq_sensors.select, wake_word, my, zha.update, smartthinq_sensors.climate, fan, analytics, energyzero.sensor, tado.sensor, tradfri.sensor, modbus.binary_sensor, file_upload, event, system_log, api, hardware, blueprint, smartthinq_sensors.fan, hue.scene, sonos.number, reolink.select, notify, zha.binary_sensor, reolink.light, cloud, tag, roborock.select, update, roborock.switch, met, netatmo.camera, netatmo.light, tradfri.cover, automation, water_heater, hue.sensor, intent, mobile_app.device_tracker, tradfri.switch, sonos_cloud.media_player, zha.cover, cast, sensor, modbus, timer, zha.select, roborock.number, roborock.binary_sensor, sonos.sensor, tado.water_heater The system is waiting for tasks: {<Task pending name='call_later 0.1' coro=<ModbusRegisterSensor.async_update() running at /usr/src/homeassistant/homeassistant/components/modbus/sensor.py:113> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>, <Task pending name='call_later 0.1' coro=<ModbusRegisterSensor.async_update() running at /usr/src/homeassistant/homeassistant/components/modbus/sensor.py:113> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>, <Task pending name='call_later 0.1' coro=<ModbusRegisterSensor.async_update() running at /usr/src/homeassistant/homeassistant/components/modbus/sensor.py:113> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>, <Task pending name='call_later 0.1' coro=<ModbusRegisterSensor.async_update() running at /usr/src/homeassistant/homeassistant/components/modbus/sensor.py:113> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>, <Task pending name='call_later 0.1' coro=<ModbusRegisterSensor.async_update() running at /usr/src/homeassistant/homeassistant/components/modbus/sensor.py:113> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>, <Task pending name='call_later 0.1' coro=<ModbusRegisterSensor.async_update() running at /usr/src/homeassistant/homeassistant/components/modbus/sensor.py:113> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>}

What version of Home Assistant Core has the issue?

core-2024.5.5

What was the last working version of Home Assistant Core?

core-2024.3.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

modbus

Link to integration documentation on our website

https://www.home-assistant.io/integrations/modbus/

Diagnostics information

No response

Example YAML snippet

- type: tcp
    host: 192.168.2.45
    port: 26
    name: "lg_modbus"
    message_wait_milliseconds: 1000
    # ref: https://gathering.tweakers.net/forum/list_message/72594644#72594644
    # ref: https://gathering.tweakers.net/forum/list_message/74222572#74222572
    sensors: 
       ##input

        ### LG Therma V U44 9kW 
      - name: ODU_operation_cycle
        scan_interval: 10
        address: 1
        slave: 1
        input_type: input

      - name: water_inlet_temp
        scale: 0.1
        precision: 2
        scan_interval: 5
        address: 2
        slave: 1
        unit_of_measurement: °C
        input_type: input

      - name: water_outlet_temp
        scale: 0.1
        precision: 2
        scan_interval: 5
        address: 3
        slave: 1
        unit_of_measurement: °C
        input_type: input

      - name: room_air_temp_circuit1
        scale: 0.1
        precision: 1
        scan_interval: 5
        address: 7
        slave: 1
        unit_of_measurement: °C
        input_type: input

      - name: current_flow_rate
        scale: 0.1
        precision: 2
        scan_interval: 5
        address: 8
        slave: 1
        unit_of_measurement: l/min
        input_type: input

      - name: energy_state_input
        scan_interval: 5
        address: 11
        slave: 1
        input_type: input

      - name: outdoor_air_temp
        scale: 0.1
        precision: 1
        scan_interval: 5
        address: 12
        slave: 1
        unit_of_measurement: °C
        input_type: input

      - name: fan
        scale: 0.1
        precision: 1
        scan_interval: 5
        address: 19
        slave: 1
        unit_of_measurement: RPM
        input_type: input

      - name: inverter
        scale: 1
        precision: 1
        scan_interval: 5
        address: 24
        slave: 1
        unit_of_measurement: Hz
        input_type: input

        ##holding
      - name: operation_mode
        scan_interval: 5
        address: 99
        slave: 1
        input_type: holding

      - name: control_method
        scan_interval: 5
        address: 1
        slave: 1
        input_type: holding

      - name: target_temp_circuit1
        scale: 0.1
        precision: 1
        scan_interval: 5
        address: 2
        slave: 1
        unit_of_measurement: °C
        input_type: holding

      - name: room_air_temp_circuit1_holding
        scale: 0.1
        precision: 1
        scan_interval: 5
        address: 3
        slave: 1
        unit_of_measurement: °C
        input_type: holding

      - name: shift_value_in_auto_mode_circuit1
        scan_interval: 5
        address: 4
        slave: 1
        input_type: holding

      - name: energy_state_input_holding
        scan_interval: 5
        address: 9
        slave: 1
        input_type: holding

    binary_sensors:
        ##coil
      - name: enable_disable_heating/cooling
        scan_interval: 5
        address: 98
        slave: 1

      - name: enable_disable_dhw
        scan_interval: 5
        address: 1
        slave: 1

      - name: silent_mode_set
        scan_interval: 5
        address: 2
        slave: 1

      - name: trigger_desinfection_operation
        scan_interval: 5
        address: 3
        slave: 1

      - name: emergency_stop
        scan_interval: 5
        address: 4
        slave: 1

      - name: trigger_emergency_operation
        scan_interval: 5
        address: 5
        slave: 1

        ## discrete
      - name: water_flow_status   
        scan_interval: 5
        address: 97
        slave: 1
        input_type: discrete_input

      - name: water_pump_status   
        scan_interval: 5
        address: 1
        slave: 1
        input_type: discrete_input

      - name: compressor_status   
        scan_interval: 5
        address: 3
        slave: 1
        input_type: discrete_input

      - name: defrosting_status   
        scan_interval: 5
        address: 4
        slave: 1
        input_type: discrete_input

      - name: silent_mode_status   
        scan_interval: 5
        address: 7
        slave: 1
        input_type: discrete_input

      - name: cooling_status   
        scan_interval: 5
        address: 8
        slave: 1
        input_type: discrete_input

      - name: error_status   
        scan_interval: 5
        address: 13
        slave: 1
        input_type: discrete_input

      - name: emergency_operation_available_space_heating/cooling   
        scan_interval: 5
        address: 14
        slave: 1
        input_type: discrete_input

      - name: mix_pump_status   
        scan_interval: 5
        address: 16
        slave: 1
        input_type: discrete_input

Anything in the logs that might be useful for us?

2024-06-02 21:12:09.446 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration solis which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-02 21:12:09.449 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration nordpool which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-02 21:12:09.451 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration smartthinq_sensors which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-02 21:12:09.453 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-02 21:12:09.454 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration sonos_cloud which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-02 21:12:10.645 ERROR (MainThread) [homeassistant.helpers.entity_registry] 'device_tracker' from integration tado has a non string unique_id '6356374', please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+tado%22
2024-06-02 21:12:10.645 ERROR (MainThread) [homeassistant.helpers.entity_registry] 'device_tracker' from integration tado has a non string unique_id '6862936', please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+tado%22
2024-06-02 21:12:10.646 ERROR (MainThread) [homeassistant.helpers.entity_registry] 'device_tracker' from integration tado has a non string unique_id '7417417', please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+tado%22
2024-06-02 21:12:20.169 WARNING (ImportExecutor_0) [homeassistant.helpers.typing] HomeAssistantType was used from solis, 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 'solis' custom integration
2024-06-02 21:12:20.178 WARNING (ImportExecutor_0) [homeassistant.helpers.typing] ServiceCallType was used from solis, this is a deprecated alias which will be removed in HA Core 2025.5. Use homeassistant.core.ServiceCall instead, please report it to the author of the 'solis' custom integration
2024-06-02 21:12:21.008 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-06-02 21:12:43.318 ERROR (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: lg_modbus: Error: device: 1 address: 0 -> Modbus Error: [Input/Output] ERROR: No response received after 3 retries
2024-06-02 21:17:41.427 WARNING (MainThread) [homeassistant.bootstrap] Setup timed out for bootstrap waiting on {<Task pending name='call_later 0.1' coro=<ModbusRegisterSensor.async_update() running at /usr/src/homeassistant/homeassistant/components/modbus/sensor.py:113> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>, <Task pending name='call_later 0.1' coro=<ModbusRegisterSensor.async_update() running at /usr/src/homeassistant/homeassistant/components/modbus/sensor.py:113> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>, <Task pending name='call_later 0.1' coro=<ModbusRegisterSensor.async_update() running at /usr/src/homeassistant/homeassistant/components/modbus/sensor.py:113> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>, <Task pending name='call_later 0.1' coro=<ModbusRegisterSensor.async_update() running at /usr/src/homeassistant/homeassistant/components/modbus/sensor.py:113> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>, <Task pending name='call_later 0.1' coro=<ModbusRegisterSensor.async_update() running at /usr/src/homeassistant/homeassistant/components/modbus/sensor.py:113> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>, <Task pending name='call_later 0.1' coro=<ModbusRegisterSensor.async_update() running at /usr/src/homeassistant/homeassistant/components/modbus/sensor.py:113> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>, <Task pending name='call_later 0.1' coro=<ModbusRegisterSensor.async_update() running at /usr/src/homeassistant/homeassistant/components/modbus/sensor.py:113> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>} - moving forward
2024-06-02 21:17:41.495 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 630: self.hass.helpers.event.async_track_time_interval(, please create a bug report at https://github.com/hacs/integration/issues
2024-06-02 21:17:56.481 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: backup, humidifier, met.weather, bluetooth, mobile_app.notify, zha.button, mobile_app, reolink.siren, energyzero, sonos.switch, calendar, ssdp, sonos, hue.light, roborock.sensor, reolink.update, roborock.time, default_config, select, time, wallbox.sensor, netatmo.cover, mqtt, tibber, zha, smartthinq_sensors, device_tracker, schedule, tado.climate, hassio, stt, wallbox, weather, hue.binary_sensor, button, hacs.sensor, sun.sensor, mobile_app.binary_sensor, hassio.sensor, solis, hue.event, smartthinq_sensors.binary_sensor, smartthinq_sensors.humidifier, config, netatmo.fan, counter, input_text, homeassistant_yellow, zone, device_automation, homewizard.switch, smartthinq_sensors.water_heater, ffmpeg, input_button, tibber.sensor, unifi.image, netatmo.climate, camera, homewizard, image, input_datetime, roborock.button, assist_pipeline, zha.switch, zha.device_tracker, thread, unifi.device_tracker, solis.sensor, cast.media_player, wallbox.switch, ios.sensor, netatmo.binary_sensor, input_select, number, smartthinq_sensors.switch, netatmo.sensor, mobile_app.sensor, hassio.binary_sensor, mqtt.sensor, zeroconf, binary_sensor, sonos.binary_sensor, reolink.camera, sun, alarm_control_panel, zha.climate, siren, unifi.update, media_player, search, smartthinq_sensors.button, homeassistant_hardware, google_translate.tts, tradfri, cloud.tts, netatmo, lovelace, tradfri.light, hacs, zha.sensor, template.sensor, websocket_api, smartthinq_sensors.sensor, unifi.sensor, reolink.switch, switch, homeassistant_alerts, netatmo.select, input_number, nordpool, tradfri.fan, stream, reolink.button, roborock.vacuum, reolink.binary_sensor, zha.siren, reolink.number, homewizard.number, zha.lock, local_calendar.calendar, tibber.notify, zha.number, input_boolean, zha.fan, roborock, image_upload, wallbox.number, lock, tts, person, map, system_health, homewizard.sensor, vacuum, repairs, unifi.switch, dhcp, media_source, netatmo.switch, energy.sensor, sonos.media_player, recorder, roborock.image, tado, usb, reolink.sensor, auth, tado.device_tracker, unifi.button, trace, application_credentials, homeassistant.scene, template, http, logbook, wallbox.lock, zha.light, tado.binary_sensor, hue, onboarding, reolink, diagnostics, webhook, history, modbus.sensor, homewizard.button, energy, unifi, sonos_cloud, cover, homeassistant, zha.alarm_control_panel, network, climate, nordpool.sensor, local_calendar, logger, persistent_notification, script, ios.notify, light, hue.switch, smartthinq_sensors.light, ios, scene, frontend, hassio.update, conversation, smartthinq_sensors.select, wake_word, my, zha.update, smartthinq_sensors.climate, fan, analytics, energyzero.sensor, tado.sensor, tradfri.sensor, modbus.binary_sensor, file_upload, event, system_log, api, hardware, blueprint, smartthinq_sensors.fan, hue.scene, sonos.number, reolink.select, notify, zha.binary_sensor, reolink.light, cloud, tag, roborock.select, update, roborock.switch, met, netatmo.camera, netatmo.light, tradfri.cover, automation, water_heater, hue.sensor, intent, mobile_app.device_tracker, tradfri.switch, sonos_cloud.media_player, zha.cover, cast, sensor, modbus, timer, zha.select, roborock.number, roborock.binary_sensor, sonos.sensor, tado.water_heater The system is waiting for tasks: {<Task pending name='call_later 0.1' coro=<ModbusRegisterSensor.async_update() running at /usr/src/homeassistant/homeassistant/components/modbus/sensor.py:113> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>, <Task pending name='call_later 0.1' coro=<ModbusRegisterSensor.async_update() running at /usr/src/homeassistant/homeassistant/components/modbus/sensor.py:113> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>, <Task pending name='call_later 0.1' coro=<ModbusRegisterSensor.async_update() running at /usr/src/homeassistant/homeassistant/components/modbus/sensor.py:113> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>, <Task pending name='call_later 0.1' coro=<ModbusRegisterSensor.async_update() running at /usr/src/homeassistant/homeassistant/components/modbus/sensor.py:113> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>, <Task pending name='call_later 0.1' coro=<ModbusRegisterSensor.async_update() running at /usr/src/homeassistant/homeassistant/components/modbus/sensor.py:113> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>, <Task pending name='call_later 0.1' coro=<ModbusRegisterSensor.async_update() running at /usr/src/homeassistant/homeassistant/components/modbus/sensor.py:113> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[set.remove()]>}
2024-06-02 21:24:20.811 ERROR (MainThread) [homeassistant.components.homewizard.coordinator] Error fetching homewizard data: Timeout occurred while connecting to the HomeWizard Energy device
2024-06-02 21:25:01.611 ERROR (MainThread) [homeassistant.components.homewizard.coordinator] Error fetching homewizard data: Timeout occurred while connecting to the HomeWizard Energy device
2024-06-02 21:26:33.612 ERROR (MainThread) [homeassistant.components.homewizard.coordinator] Error fetching homewizard data: Timeout occurred while connecting to the HomeWizard Energy device
2024-06-02 21:27:47.146 ERROR (MainThread) [homeassistant.components.homewizard.coordinator] Error fetching homewizard data: Timeout occurred while connecting to the HomeWizard Energy device

Additional information

No response

home-assistant[bot] commented 1 month ago

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

Code owner commands Code owners of `modbus` 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 modbus` 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)

modbus documentation modbus source (message by IssueLinks)

janiversen commented 1 month ago

Your modbus device do not respond.

janiversen commented 1 month ago

06-02 21:12:43.318 ERROR (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: lg_modbus: Error: device: 1 address: 0 -> Modbus Error: [Input/Output] ERROR: No response received after 3 retries

janiversen commented 1 month ago

And not only modbus have a problem, at least another integration also cannot connect.

sandervanzutphen commented 1 month ago

The modbus device does not seem to be the problem, as the HTTP config pages of modbus device are working without problems and problems started after updating HomeAssistant. I will try connecting with the modbus device using an external modbus test application when i get home to determine if the problem originates within HA (of a dependancy) of the device.

janiversen commented 1 month ago

Also please remove your custom components as requested when opening the issue.

You do not access the web pages via HA, so that is not the same route.

janiversen commented 3 weeks ago

Any progress ? otherwise we will close the issue.