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
71.07k stars 29.73k forks source link

Can't read add-on info #110935

Closed pickonedev closed 3 months ago

pickonedev commented 6 months ago

The problem

I get this in the logs

Logger: homeassistant.components.hassio.discovery
Source: components/hassio/discovery.py:103
Integration: Home Assistant Supervisor ([documentation](https://www.home-assistant.io/integrations/hassio), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+hassio%22))
First occurred: 12:13:38 (5 occurrences)
Last logged: 12:13:38
Can't read add-on info:

And this

Logger: homeassistant.components.hassio.handler
Source: components/hassio/handler.py:596
Integration: Home Assistant Supervisor ([documentation](https://www.home-assistant.io/integrations/hassio), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+hassio%22))
First occurred: 12:13:38 (5 occurrences)
Last logged: 12:13:38

    Timeout on /addons/a0d7b954_motioneye/info request
    Timeout on /addons/5c53de3b_esphome/info request
    Timeout on /addons/core_whisper/info request
    Timeout on /addons/core_piper/info request
    Timeout on /addons/core_openwakeword/info request

What version of Home Assistant Core has the issue?

core-2024.2.2

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

Home Assistant Supervisor

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 6 months ago

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. - `@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)


hassio documentation hassio source (message by IssueLinks)

shbatm commented 6 months ago

Similar error for me too:

Logger: homeassistant.components.hassio.handler
Source: components/hassio/handler.py:596
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 7:40:21 PM (28 occurrences)
Last logged: 7:48:54 PM

Timeout on /network/info request
Timeout on /resolution/info request
Timeout on /os/info request
Timeout on /addons request
Timeout on /store request
bdraco commented 6 months ago

Is there anything helpful in the supervisor logs?

pickonedev commented 6 months ago

Nothing bad into the supervisor logs, only into the Home Assistant Core Everytime I restart HA, I will get those 2 types errors of 5 occurance each

shbatm commented 6 months ago

Nothing was relevent in the supervisor logs for me either. I've been chasing some 'internal' timeout isuses aside from the is and what I thought was a memory leak as well. FWIW, I have not seen these come back since disabling the Frigate custom integration.

issue-triage-workflows[bot] commented 3 months 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.