I get this error every once in as while, but im an admin on the system
Logger: homeassistant.components.hassio
Source: components/hassio/init .py:557
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 7:04:50 PM (1 occurrences)
Last logged: 7:04:50 PM
Can’t read Supervisor data:
3 Likes
jesse_s
(Jesse)
December 12, 2021, 5:15pm
2
I am seeing this same issue. Did you ever figure out more about it? Right now I am noticing it on startup, but it may be other times as well.
Not sure what I did but I don’t see it any more. I made so many chances recently that I couldn’t tell you what I changed to make it go away…
1 Like
fraintt
November 24, 2022, 12:58pm
4
I have sometimes the same issue.
Sometimes HASS works fine without issues for Weeks, and then suddenly sometimes, it seems like hass-core cannot connect to supervisor. Reloading supervisor does not help, only a restart of hass works. And this, you have to do from the commandline as the restart from developer-tools does not work.
This issue was mentioned by more users, but nobody found a fix for it, all the issues went stale…
opened 05:55AM - 31 Mar 22 UTC
closed 09:06PM - 29 Sep 22 UTC
stale
### The problem
After some random amount of uptime my HA Core looses the abil… ity to connect with the supervisor.
Until I restart core via de HA CLI.
### What version of Home Assistant Core has the issue?
core-2022.3.7
### 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
_No response_
### Link to integration documentation on our website
_No response_
### Diagnostics information
This is the System Health after a restart, because the information won't load when it happens.
## System Health
version | core-2022.3.7
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.9.9
os_name | Linux
os_version | 5.10.103
arch | x86_64
timezone | Europe/Amsterdam
<details><summary>Home Assistant Community Store</summary>
GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
GitHub API Calls Remaining | 4853
Installed Version | 1.23.0
Stage | running
Available Repositories | 1018
Downloaded Repositories | 21
</details>
<details><summary>Home Assistant Cloud</summary>
logged_in | false
-- | --
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok
</details>
<details><summary>Home Assistant Supervisor</summary>
host_os | Home Assistant OS 7.5
-- | --
update_channel | stable
supervisor_version | supervisor-2022.03.5
docker_version | 20.10.9
disk_total | 30.8 GB
disk_used | 15.0 GB
healthy | true
supported | true
board | ova
supervisor_api | ok
version_api | ok
installed_addons | Samba share (9.5.1), Terminal & SSH (9.3.0), Vaultwarden (Bitwarden) (0.15.0), AdGuard Home (4.4.5), MariaDB (2.4.0), UniFi Network Application (1.1.4), WireGuard (0.6.0), ESPHome (2022.2.6), deCONZ (6.12.0), Spotify Connect (0.11.0), Duck DNS (1.14.0), Nginx Proxy Manager (0.11.0), Mosquitto broker (6.0.1), Node-RED (11.1.0), Studio Code Server (4.2.0)
</details>
<details><summary>Lovelace</summary>
dashboards | 5
-- | --
resources | 8
views | 16
mode | storage
</details>
<details><summary>Spotify</summary>
api_endpoint_reachable | ok
-- | --
</details>
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
```txt
2022-03-31 04:53:54 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_vscode/stats request
2022-03-31 04:53:54 WARNING (MainThread) [homeassistant.components.hassio] Can't read Supervisor data:
2022-03-31 04:59:09 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_nodered/stats request
2022-03-31 04:59:09 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_spotify/stats request
2022-03-31 04:59:09 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/core_mosquitto/stats request
2022-03-31 04:59:09 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_nginxproxymanager/stats request
2022-03-31 04:59:09 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/core_duckdns/stats request
2022-03-31 04:59:09 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/core_deconz/stats request
2022-03-31 04:59:09 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_wireguard/stats request
2022-03-31 04:59:09 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/5c53de3b_esphome/stats request
2022-03-31 04:59:09 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_unifi/stats request
2022-03-31 04:59:09 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_vscode/stats request
```
### Additional information
The :8123/hassio-page shows the Troubleshooting-tips
#### Troubleshooting
1. If you just started, make sure you have given the Supervisor enough time to start.
2. Check the Observer
3. Try a reboot of the host
4. Check System Health
5. Ask for help
The link for the observer points me to:
http://homeassistant.local:4357/
But that's not the correct name, with the right name it shows:
Home Assistant observer
Supervisor: | Connected
Supported: | Supported
Healthy: | Healthy
:8123/config/info
doesn't load the 'Health'-segment
This makes I can't load i.e. deCONZ via the sidepanel.
Unable to load the panel source: /api/hassio/app/entrypoint.js.
I created an notification for when the deCONZ CPU usages goes stale (for 30mins), which is indicative of the error occurring.
My zigbee lights also start failing, but weirdly enough not right away.
Today I received the notification at 5:18 AM and around 20 minutes later the lights could still be turned on.
Now, an hour, or maybe two later, nothing responds.
deCONZ is just an example and the most annoying case, but i.e. VS Code Server add-on has the same issue.
I though for a while it was related to the purge at night, but I disabled auto_purge and rescheduled it to some other time of day, but no effect.
I had this problem on a Pi3 and it's still present after I migrated to a NUC i3 using proxmox.
Suspected a flaky sdcard to be the issue, but that's not the case.
opened 07:19AM - 23 Dec 21 UTC
closed 08:34AM - 07 Jan 22 UTC
### The problem
Logger: homeassistant.components.hassio
Source: components/has… sio/__init__.py:559
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 04:44:57 (3 occurrences)
Last logged: 05:20:53
Can't read Supervisor data:
### What version of Home Assistant Core has the issue?
2021.12.3
### 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
_No response_
### Link to integration documentation on our website
_No response_
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
```txt
Logger: homeassistant.components.hassio.handler
Source: components/hassio/handler.py:237
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 04:44:57 (24 occurrences)
Last logged: 05:20:54
Timeout on /addons/core_mariadb/stats request
Timeout on /addons/core_mosquitto/stats request
Timeout on /addons/core_samba/stats request
Timeout on /addons/core_configurator/stats request
Timeout on /addons/45df7312_zigbee2mqtt/stats request
===============
And
===============
Logger: aiohttp.server
Source: /usr/local/lib/python3.9/site-packages/aiohttp/web_protocol.py:405
First occurred: 00:08:55 (3 occurrences)
Last logged: 07:55:57
Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/aiohttp/web_protocol.py", line 334, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Invalid method encountered'"
```
### Additional information
I have this error frequently. Also on previous versions. Results in not showing the Supervisor page in previous versions. Solution was a turning off Raspberry Pi and turn it on again. (I still can access the supervisor page in the December versions).
opened 11:29AM - 13 Nov 21 UTC
closed 10:03PM - 21 Mar 22 UTC
bug
stale
### Describe the issue you are experiencing
After a session of updating and add… ing new add-ons the Supervisor integration appears to have failed altogether or has become unusable. I am currently unable to access the Supervisor tab in the main UI, nor access any add-ons although it appears that previous installed, configured and started add-ons are still active in the background.
The response is intermittent in the sense that attempting to access to Supervisor tab will at times either:
-and predominately display a blank screen; or
-infrequently display a "Could not load the Supervisor panel!" banner and 'Troubleshooting' menu; and
-on one occasion displayed the Supervisor panel 'dashboard', 'add-ons' and 'system' tabs but the content is unresponsive.
A small portion of the main Home Assistant log lists the following warning and error reports:
```
2021-11-13 19:14:37 WARNING (MainThread) [homeassistant.components.hassio] Can't read Supervisor data:
2021-11-13 19:15:27 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /core/stats request
2021-11-13 19:15:27 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /core/stats -
2021-11-13 19:15:27 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /supervisor/stats request
2021-11-13 19:15:27 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /supervisor/stats -
2021-11-13 19:17:36 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /backups/reload request
2021-11-13 19:17:36 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /backups/reload -
2021-11-13 19:19:11 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /addons/a0d7b954_vscode/install - 'AddonManager.install' blocked from execution, no host internet connection
2021-11-13 19:19:36 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /addons/a0d7b954_vscode/install - 'AddonManager.install' blocked from execution, no host internet connection
2021-11-13 19:19:49 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_appdaemon/stats request
2021-11-13 19:19:49 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_grocy/stats request
2021-11-13 19:19:49 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/7be23ff5_dropbox_sync/stats request
2021-11-13 19:19:49 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_grafana/stats request
2021-11-13 19:19:49 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_ssh/stats request
2021-11-13 19:19:49 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/core_samba/stats request
2021-11-13 19:19:49 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_esphome/stats request
2021-11-13 19:19:49 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_influxdb/stats request
2021-11-13 19:19:49 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_nodered/stats request
2021-11-13 19:19:49 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_chrony/stats request
2021-11-13 19:19:49 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_nginxproxymanager/stats request
2021-11-13 19:19:49 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/core_configurator/stats request
2021-11-13 19:19:49 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_logviewer/stats request
2021-11-13 19:19:49 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_phpmyadmin/stats request
2021-11-13 19:19:49 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/core_mariadb/stats request
2021-11-13 19:19:49 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/core_mosquitto/stats request
2021-11-13 19:19:49 WARNING (MainThread) [homeassistant.components.hassio] Can't read Supervisor data:
2021-11-13 19:20:17 ERROR (MainThread) [homeassistant.components.hassio.http] Client timeout error on API request supervisor/logs
2021-11-13 19:20:17 ERROR (MainThread) [homeassistant.components.hassio.http] Client timeout error on API request supervisor/logs
2021-11-13 19:20:27 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /core/stats request
2021-11-13 19:20:27 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /core/stats -
2021-11-13 19:20:27 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /supervisor/stats request
2021-11-13 19:20:27 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /supervisor/stats -
```
A fuller log can be found here: [https://pastebin.com/5vN8PPeq](url)
### What is the used version of the Supervisor?
supervisor-2021.10.8
### What type of installation are you running?
Home Assistant OS
### Which operating system are you running on?
Home Assistant Operating System
### What is the version of your installed operating system?
6.6
### What version of Home Assistant Core is installed?
core-2021.11.3
### Steps to reproduce the issue
1. Its permanent at the moment.
2. Followed the steps in the trouble shooting menu:
Result of `Home Assistant Observer
Supervisor: Connected
Supported: Unsupported
Healthy: Unhealthy`
3. Was forced to pull the power connection out to effect a reboot.
4. No change following reboot.
...
### Anything in the Supervisor logs that might be useful for us?
```txt
Am unable to access the Supervisor log. The error reported is:
Failed to get supervisor logs, 502: Bad Gateway
```
### Additional information
_No response_
Hello,
i dont know what happend, i came back home and want to check something in my Smarthome and the complete settings area is dead, or all what has to do with the supervisor.
when i click on addons for example i get a error message and i should check the observer
HomeAssistant Observer is working
Home Assistant observer
Supervisor: Connected
Supported: Supported
Healthy: Healthy
any ideas what i can to to repair my Homeassistant?
Logger: homeassistant.components.hassio
Source: components…
opened 05:55AM - 31 Mar 22 UTC
closed 09:06PM - 29 Sep 22 UTC
stale
### The problem
After some random amount of uptime my HA Core looses the abil… ity to connect with the supervisor.
Until I restart core via de HA CLI.
### What version of Home Assistant Core has the issue?
core-2022.3.7
### 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
_No response_
### Link to integration documentation on our website
_No response_
### Diagnostics information
This is the System Health after a restart, because the information won't load when it happens.
## System Health
version | core-2022.3.7
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.9.9
os_name | Linux
os_version | 5.10.103
arch | x86_64
timezone | Europe/Amsterdam
<details><summary>Home Assistant Community Store</summary>
GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
GitHub API Calls Remaining | 4853
Installed Version | 1.23.0
Stage | running
Available Repositories | 1018
Downloaded Repositories | 21
</details>
<details><summary>Home Assistant Cloud</summary>
logged_in | false
-- | --
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok
</details>
<details><summary>Home Assistant Supervisor</summary>
host_os | Home Assistant OS 7.5
-- | --
update_channel | stable
supervisor_version | supervisor-2022.03.5
docker_version | 20.10.9
disk_total | 30.8 GB
disk_used | 15.0 GB
healthy | true
supported | true
board | ova
supervisor_api | ok
version_api | ok
installed_addons | Samba share (9.5.1), Terminal & SSH (9.3.0), Vaultwarden (Bitwarden) (0.15.0), AdGuard Home (4.4.5), MariaDB (2.4.0), UniFi Network Application (1.1.4), WireGuard (0.6.0), ESPHome (2022.2.6), deCONZ (6.12.0), Spotify Connect (0.11.0), Duck DNS (1.14.0), Nginx Proxy Manager (0.11.0), Mosquitto broker (6.0.1), Node-RED (11.1.0), Studio Code Server (4.2.0)
</details>
<details><summary>Lovelace</summary>
dashboards | 5
-- | --
resources | 8
views | 16
mode | storage
</details>
<details><summary>Spotify</summary>
api_endpoint_reachable | ok
-- | --
</details>
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
```txt
2022-03-31 04:53:54 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_vscode/stats request
2022-03-31 04:53:54 WARNING (MainThread) [homeassistant.components.hassio] Can't read Supervisor data:
2022-03-31 04:59:09 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_nodered/stats request
2022-03-31 04:59:09 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_spotify/stats request
2022-03-31 04:59:09 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/core_mosquitto/stats request
2022-03-31 04:59:09 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_nginxproxymanager/stats request
2022-03-31 04:59:09 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/core_duckdns/stats request
2022-03-31 04:59:09 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/core_deconz/stats request
2022-03-31 04:59:09 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_wireguard/stats request
2022-03-31 04:59:09 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/5c53de3b_esphome/stats request
2022-03-31 04:59:09 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_unifi/stats request
2022-03-31 04:59:09 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_vscode/stats request
```
### Additional information
The :8123/hassio-page shows the Troubleshooting-tips
#### Troubleshooting
1. If you just started, make sure you have given the Supervisor enough time to start.
2. Check the Observer
3. Try a reboot of the host
4. Check System Health
5. Ask for help
The link for the observer points me to:
http://homeassistant.local:4357/
But that's not the correct name, with the right name it shows:
Home Assistant observer
Supervisor: | Connected
Supported: | Supported
Healthy: | Healthy
:8123/config/info
doesn't load the 'Health'-segment
This makes I can't load i.e. deCONZ via the sidepanel.
Unable to load the panel source: /api/hassio/app/entrypoint.js.
I created an notification for when the deCONZ CPU usages goes stale (for 30mins), which is indicative of the error occurring.
My zigbee lights also start failing, but weirdly enough not right away.
Today I received the notification at 5:18 AM and around 20 minutes later the lights could still be turned on.
Now, an hour, or maybe two later, nothing responds.
deCONZ is just an example and the most annoying case, but i.e. VS Code Server add-on has the same issue.
I though for a while it was related to the purge at night, but I disabled auto_purge and rescheduled it to some other time of day, but no effect.
I had this problem on a Pi3 and it's still present after I migrated to a NUC i3 using proxmox.
Suspected a flaky sdcard to be the issue, but that's not the case.