Open NickSee opened 1 month ago
Although no correlation with 03:02 warning I have found that File Editor has been reporting every 0.6-0.9 seconds for quite some time. I have just used it to open a document (successfully with no problems). Here is a chunk of File Editor's log leading up to my first use of it this morning which then temporarily stopped the repetitive log entries: INFO:2024-10-20 07:45:39,935:hass_configurator.configurator:127.0.0.1 - "GET / HTTP/1.1" 200 - INFO:2024-10-20 07:46:30,741:hass_configurator.configurator:127.0.0.1 - "GET / HTTP/1.1" 200 - INFO:2024-10-20 07:47:24,223:hass_configurator.configurator:127.0.0.1 - "GET / HTTP/1.1" 200 - INFO:2024-10-20 07:48:20,057:hass_configurator.configurator:127.0.0.1 - "GET / HTTP/1.1" 200 - INFO:2024-10-20 07:49:27,926:hass_configurator.configurator:127.0.0.1 - "GET / HTTP/1.1" 200 - INFO:2024-10-20 07:50:23,813:hass_configurator.configurator:127.0.0.1 - "GET / HTTP/1.1" 200 - INFO:2024-10-20 07:51:19,380:hass_configurator.configurator:127.0.0.1 - "GET / HTTP/1.1" 200 - INFO:2024-10-20 07:52:01,106:hass_configurator.configurator:127.0.0.1 - "GET / HTTP/1.1" 200 - INFO:2024-10-20 07:52:53,877:hass_configurator.configurator:127.0.0.1 - "GET / HTTP/1.1" 200 - INFO:2024-10-20 07:53:44,680:hass_configurator.configurator:127.0.0.1 - "GET / HTTP/1.1" 200 - INFO:2024-10-20 07:54:40,410:hass_configurator.configurator:127.0.0.1 - "GET / HTTP/1.1" 200 - INFO:2024-10-20 07:55:22,831:hass_configurator.configurator:127.0.0.1 - "GET / HTTP/1.1" 200 - INFO:2024-10-20 07:55:51,007:hass_configurator.configurator:172.30.32.2 - "GET / HTTP/1.1" 200 - INFO:2024-10-20 07:55:52,507:hass_configurator.configurator:172.30.32.2 - "GET /material-icons.fallback.css HTTP/1.1" 200 - INFO:2024-10-20 07:55:52,598:hass_configurator.configurator:172.30.32.2 - "GET /style.css HTTP/1.1" 200 - INFO:2024-10-20 07:55:52,661:hass_configurator.configurator:172.30.32.2 - "GET /jquery-3.6.0.min.js HTTP/1.1" 200 - INFO:2024-10-20 07:55:52,665:hass_configurator.configurator:172.30.32.2 - "GET /materialize.min.js HTTP/1.1" 200 - INFO:2024-10-20 07:55:52,695:hass_configurator.configurator:172.30.32.2 - "GET /js-yaml.min.js HTTP/1.1" 200 - INFO:2024-10-20 07:55:52,921:hass_configurator.configurator:172.30.32.2 - "GET /flUhRq6tzZclQEJ-Vdg-IuiaDsNc.woff2 HTTP/1.1" 200 - INFO:2024-10-20 07:55:53,063:hass_configurator.configurator:172.30.32.2 - "GET /api/file?filename=/homeassistant/configuration.yaml HTTP/1.1" 200 - INFO:2024-10-20 07:55:53,358:hass_configurator.configurator:172.30.32.2 - "GET /api/listdir?path=. HTTP/1.1" 200 - INFO:2024-10-20 07:56:01,671:hass_configurator.configurator:127.0.0.1 - "GET / HTTP/1.1" 200 -
The problem
Brand new homeassistant instance created yesterday on new media reported the following Warning overnight: Updating state for update.home_assistant_supervisor_update (<class 'homeassistant.components.hassio.update.SupervisorSupervisorUpdateEntity'>) took 0.421 seconds. Please create a bug report
What version of Home Assistant Core has the issue?
core-2024.10.3
What was the last working version of Home Assistant Core?
New instance
What type of installation are you running?
Home Assistant OS
Integration causing the issue
supervisor-2024.10.2
Link to integration documentation on our website
No response
Diagnostics information
Logger: homeassistant.helpers.entity Source: helpers/entity.py:1180 First occurred: 03:02:15 (1 occurrences) Last logged: 03:02:15
Updating state for update.home_assistant_supervisor_update (<class 'homeassistant.components.hassio.update.SupervisorSupervisorUpdateEntity'>) took 0.421 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+hassio%22
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
Last night at 23:30 (this is probably unrelated but mentioning in case relevant) I was surprised to see Supervisor log state that "NodeRed was unhealthy" because this is a brand new install on new media and Node Red contains no user injected content, it was a brand new installed add-on. Also was part of the reason to do a new install - as couldn't cure same reports on my mature 10 year old set up). Nothing in NodeRed log this morning beyond 23:52 though so no correlation with above 03:02 error.