Warning: Updating state for sensor.back_up_load took 0.788 seconds. (GoodWe)

[MarkusMit]

The problem

Warning in Log view:

Logger: homeassistant.helpers.entity Source: helpers/entity.py:1152 First occurred: 18:05:45 (1 occurrences) Last logged: 18:05:45

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

What version of Home Assistant Core has the issue?

core-2024.2.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

GoodWe

Link to integration documentation on our website

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

Diagnostics information

home-assistant_goodwe_2024-02-10T20-01-06.664Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

GoodWe Inverter GW10K-ET Firmware: 04029-11-S11 / 02041-27-S00

[home-assistant[bot]]

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

Code owner commands

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

---

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

[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

[TNTLarsn]

Logger: asyncio
Quelle: runner.py:190
Erstmals aufgetreten: 18:48:04 (3 Vorkommnisse)
Zuletzt protokolliert: 18:48:24

Executing <Task finished name='GoodWe - GoodWe - refresh' coro=<DataUpdateCoordinator._handle_refresh_interval() done, defined at /usr/src/homeassistant/homeassistant/helpers/update_coordinator.py:255> result=None created at /usr/src/homeassistant/homeassistant/util/async_.py:40> took 0.112 seconds
Executing <Task finished name='GoodWe - GoodWe - refresh' coro=<DataUpdateCoordinator._handle_refresh_interval() done, defined at /usr/src/homeassistant/homeassistant/helpers/update_coordinator.py:255> result=None created at /usr/src/homeassistant/homeassistant/util/async_.py:40> took 0.119 seconds
Executing <Task finished name='GoodWe - GoodWe - refresh' coro=<DataUpdateCoordinator._handle_refresh_interval() done, defined at /usr/src/homeassistant/homeassistant/helpers/update_coordinator.py:255> result=None created at /usr/src/homeassistant/homeassistant/util/async_.py:40> took 0.117 seconds

[bdraco]

It looks like there have been a lot of fixes in the upstream library https://github.com/marcelblijleven/goodwe/releases?page=1 but HA is still using an older versions

[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.