Since update 2023.1.5 I am getting many warnings for state updates going wrong

[smarthomefamilyverrips]

The problem

Since latest HA update I get several status updates from all different kind of elements and integrations

Logger: homeassistant.components.hassio.handler Source: components/hassio/handler.py:48 Integration: Home Assistant Supervisor (documentation, issues) First occurred: 15:00:51 (9 occurrences) Last logged: 15:00:51

Timeout on /addons/6a3d001f_assistant_relay/stats request Timeout on /addons/a0d7b954_spotify/stats request Timeout on /addons/5c53de3b_esphome/stats request Timeout on /addons/cebe7a76_hassio_google_drive_backup/stats request Timeout on /addons/core_samba/stats request

Logger: homeassistant.components.hassio Source: components/hassio/init.py:843 Integration: Home Assistant Supervisor (documentation, issues) First occurred: 15:00:51 (9 occurrences) Last logged: 15:00:51

Could not fetch stats for 6a3d001f_assistant_relay: Could not fetch stats for a0d7b954_spotify: Could not fetch stats for 5c53de3b_esphome: Could not fetch stats for cebe7a76_hassio_google_drive_backup: Could not fetch stats for core_samba:

2023-01-18 08:30:30.117 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10 2023-01-18 08:30:30.122 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10 2023-01-18 08:30:30.124 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.tv_bedroom is taking over 10 seconds 2023-01-18 08:30:30.125 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.living_room_tv is taking over 10 seconds

Logger: homeassistant.helpers.entity Source: helpers/entity.py:556 First occurred: 16:54:32 (1 occurrences) Last logged: 16:54:32

Updating state for sensor.xt12_5_ghz_upload_speed (<class 'custom_components.asusrouter.sensor.ARSensor'>) took 0.847 seconds. Please report it to the custom integration author.

What version of Home Assistant Core has the issue?

2023.1.5

What was the last working version of Home Assistant Core?

2023.1.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Home Assistant Core

Link to integration documentation on our website

https://github.com/home-assistant

Diagnostics information

N/A

Example YAML snippet

N/A

Anything in the logs that might be useful for us?

Logger: homeassistant.components.hassio.handler
Source: components/hassio/handler.py:48
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 15:00:51 (9 occurrences)
Last logged: 15:00:51

Timeout on /addons/6a3d001f_assistant_relay/stats request
Timeout on /addons/a0d7b954_spotify/stats request
Timeout on /addons/5c53de3b_esphome/stats request
Timeout on /addons/cebe7a76_hassio_google_drive_backup/stats request
Timeout on /addons/core_samba/stats request

Logger: homeassistant.components.hassio
Source: components/hassio/init.py:843
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 15:00:51 (9 occurrences)
Last logged: 15:00:51

Could not fetch stats for 6a3d001f_assistant_relay:
Could not fetch stats for a0d7b954_spotify:
Could not fetch stats for 5c53de3b_esphome:
Could not fetch stats for cebe7a76_hassio_google_drive_backup:
Could not fetch stats for core_samba:

2023-01-18 08:30:30.117 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-01-18 08:30:30.122 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2023-01-18 08:30:30.124 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.tv_bedroom is taking over 10 seconds
2023-01-18 08:30:30.125 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.living_room_tv is taking over 10 seconds

Logger: homeassistant.helpers.entity
Source: helpers/entity.py:556
First occurred: 16:54:32 (1 occurrences)
Last logged: 16:54:32

Updating state for sensor.xt12_5_ghz_upload_speed (<class 'custom_components.asusrouter.sensor.ARSensor'>) took 0.847 seconds. Please report it to the custom integration author.

Additional information

N/A

[smarthomefamilyverrips]

And a other one

Logger: homeassistant.helpers.entity Source: helpers/entity.py:804 First occurred: 18:56:16 (1 occurrences) Last logged: 18:56:16

Updating state for light.light_office_space_local (<class 'homeassistant.components.zha.light.Light'>) took 0.590 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+zha%22

[smarthomefamilyverrips]

Other time out warning:

Logger: aioesphomeapi.reconnect_logic Source: runner.py:120 First occurred: 19:38:46 (1 occurrences) Last logged: 19:38:46

Can't connect to ESPHome API for bed-sensor @ 192.168.0.79: Timeout while connecting to ('192.168.0.79', 6053)

[smarthomefamilyverrips]

I not know what is changed but i not had this at all before 2023.1.5

[issue-triage-workflows[bot]]

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.

[smarthomefamilyverrips]

Issue still persist

[issue-triage-workflows[bot]]

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.

[smarthomefamilyverrips]

Still same problem

[issue-triage-workflows[bot]]

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.

[smarthomefamilyverrips]

Still same, there is no activity atnallnon this to solve it

[home-assistant[bot]]

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

Code owner commands

Code owners of hassio 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 hassio Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

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

[issue-triage-workflows[bot]]

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.

[smarthomefamilyverrips]

Still not solved a year later

[issue-triage-workflows[bot]]

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.

[smarthomefamilyverrips]

Not solved

[agners]

The errors/delays are all over the place (various integrations). It seems that something is using all CPU power or blocking the event loop.

Can you restart in safe mode and see if that helps (System > Power symbol on the top right > Advanced options > Restart Home Assistant in safe mode.

[smarthomefamilyverrips]

Ok will try this tomorrow, is after midnight here now.

[bdraco]

If safe mode fixes the issue, you may be able to find the source by turning on asyncio debug mode

https://www.home-assistant.io/integrations/profiler/#service-profilerset_asyncio_debug

[bdraco]

Its likely you have an integration blocking the event loop

1. Install profiler integration https://my.home-assistant.io/redirect/config_flow_start/?domain=profiler
2. Enable asyncio debug service as soon as possible after startup https://www.home-assistant.io/integrations/profiler/#service-profilerset_asyncio_debug
3. Watch logs for RuntimeError: Non-thread-safe operation and long asyncio delays
4. Download and post logs with full trace

For 2024.5.x and later Home Assistant debug mode can also be enabled in configuration.yaml

homeassistant:
  debug: true

[issue-triage-workflows[bot]]

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.