I have this issue where running hassio ha restart
after a configuration change constantly fails. Even when I run hassio ha check
and this returns successful.
I timed it to check how long it takes, and it took 1 minute and 13 seconds.
$ time hassio ha check
Processing... Done.
Command completed successfully.
real 1m13.965s
user 0m0.102s
sys 0m0.173s
However, I ran hassio ha restart
for the configuration changes to take effect. I timed this as well, and it takes incredible long time (11 minutes 4 seconds).
$ time hassio ha restart
Processing... Done.
Error: Unknown Error, see logs
real 11m4.458s
user 0m1.069s
sys 0m1.479s
I checked the error logs, and it says the following:
$ cat home-assistant.log
2020-01-08 10:02:31 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2020-01-08 10:02:44 ERROR (MainThread) [hole] Can not load data from *hole: 192.168.86.45:8089
2020-01-08 10:02:44 ERROR (MainThread) [homeassistant.components.pi_hole] Unable to fetch data from Pi-hole
2020-01-08 10:02:52 ERROR (MainThread) [tibber] Timed out when connecting to Tibber:
To get Hass.io up and running, I restart the computer hassio ho reboot
.
However, the errors in the log are still there, with even more errors, but Hass.io is still running:
$ cat home-assistant.log
2020-01-08 10:18:01 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2020-01-08 10:18:18 ERROR (MainThread) [hole] Can not load data from *hole: 192.168.86.45:8089
2020-01-08 10:18:18 ERROR (MainThread) [homeassistant.components.pi_hole] Unable to fetch data from Pi-hole
2020-01-08 10:18:18 ERROR (MainThread) [homeassistant.components.deconz] Error connecting to deCONZ gateway at 172.30.33.1
2020-01-08 10:18:22 ERROR (MainThread) [tibber] Timed out when connecting to Tibber:
2020-01-08 10:19:59 ERROR (MainThread) [homeassistant.components.bluetooth_tracker.device_tracker] Error looking up Bluetooth device
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/bluetooth/bluez.py", line 31, in discover_devices
lookup_class=lookup_class, device_id=device_id)
_bluetooth.error: (110, 'Operation timed out')
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/bluetooth_tracker/device_tracker.py", line 140, in perform_bluetooth_update
devices = await hass.async_add_executor_job(discover_devices, device_id)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/bluetooth_tracker/device_tracker.py", line 62, in discover_devices
device_id=device_id,
File "/usr/local/lib/python3.7/site-packages/bluetooth/bluez.py", line 34, in discover_devices
raise BluetoothError ("error communicating with local "
bluetooth.btcommon.BluetoothError: error communicating with local bluetooth adapter
2020-01-08 10:31:35 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.1805282736] Client exceeded max pending messages [2]: 512
2020-01-08 10:31:35 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.1805282736] Client exceeded max pending messages [2]: 512
How come a restart never works, but a reboot does, even with the same error messages?