ERROR (MainThread) [hassio.homeassistant] Error on call http://172.30.32.1:8123/api/:

Installation Home Assistant OS
1

hi everyone , i am in need of your help , i am running hassio 0.83.3 on docker over ubuntu , everything was running perfect and smoothly till 0.83.2 after upgrading i started seeing in the system tag logs the following error :

18-12-11 11:57:34 ERROR (MainThread) [hassio.homeassistant] Error on call http://172.30.32.1:8123/api/:
18-12-11 11:57:34 WARNING (MainThread) [hassio.tasks] Watchdog miss API response from Home Assistant

after that hassio restarts i don’t know where to look in order to solve this problem

any help would be greatly appreciated.

2

anyone on this ?
any ideas ?

3

@kegra I’ve also seen these errors after updating to 0.84.1. I’d really like to know why this is happening.

18-12-13 22:34:01 ERROR (MainThread) [hassio.homeassistant] Error on call http://172.30.32.1:8123/api/: 
18-12-13 22:34:12 WARNING (MainThread) [hassio.tasks] Watchdog miss API response from Home Assistant
18-12-13 22:42:36 ERROR (MainThread) [hassio.homeassistant] Error on call http://172.30.32.1:8123/api/: 
18-12-13 22:42:50 ERROR (MainThread) [hassio.tasks] Watchdog found a problem with Home Assistant API!
18-12-13 22:45:14 INFO (SyncWorker_2) [hassio.docker.interface] Stop homeassistant/qemuarm-homeassistant Docker application
18-12-13 22:46:21 INFO (SyncWorker_2) [hassio.docker.interface] Clean homeassistant/qemuarm-homeassistant Docker application
18-12-13 22:46:25 INFO (SyncWorker_1) [hassio.docker.homeassistant] Start homeassistant homeassistant/qemuarm-homeassistant with version 0.84.1
18-12-13 22:48:19 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
18-12-13 22:51:49 ERROR (MainThread) [hassio.homeassistant] Error on call http://172.30.32.1:8123/api/: 
18-12-13 22:51:50 WARNING (MainThread) [hassio.tasks] Watchdog miss API response from Home Assistant
18-12-13 22:58:38 ERROR (MainThread) [hassio.homeassistant] Error on call http://172.30.32.1:8123/api/: 
18-12-13 22:58:38 ERROR (MainThread) [hassio.tasks] Watchdog found a problem with Home Assistant API!
18-12-13 23:00:35 INFO (SyncWorker_2) [hassio.docker.interface] Stop homeassistant/qemuarm-homeassistant Docker application
18-12-13 23:03:13 INFO (SyncWorker_2) [hassio.docker.interface] Clean homeassistant/qemuarm-homeassistant Docker application
18-12-13 23:03:16 INFO (SyncWorker_3) [hassio.docker.homeassistant] Start homeassistant homeassistant/qemuarm-homeassistant with version 0.84.1
18-12-13 23:05:00 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
18-12-13 23:06:19 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
18-12-13 23:41:18 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
18-12-14 00:11:19 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
18-12-14 00:46:21 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
18-12-14 01:02:10 ERROR (MainThread) [hassio.homeassistant] Error on call http://172.30.32.1:8123/api/: 
18-12-14 01:02:10 WARNING (MainThread) [hassio.tasks] Watchdog miss API response from Home Assistant
4

nobody seems to know , what is your setup ?
what was your previous version before updating to 0.84.1?

i started seeing these errors after i updated to 0.83.3 , up to 0.83.2 worked fine for me.

5

I reverted back to 0.83.2 i don’t see the error about the api call, so should be related to 0.83.3

6

I don’t recall the specific version, but it was 0.83.x. I’m running HASSIO install (docker) on a Beaglebone Black using a USB Z-wave controller. How about you?

7

I am on ubuntu 18.04 running on docker.
did you find any solution ? how often does the problem occur to you ?

8

I’m running Debian GNU/Linux 9, BeagleBoard.org Debian Image 2018-08-30. I didn’t mention it earlier, but I’m also running two add-ons: InfluxDB and SSH server. I haven’t found a pattern or trigger to the error messages. I checked my logs today and found it happened again twice already. I’m going to update to 0.84.2 and see if anything changes.

9

ok I found the error on my installation , a custom component was flooding the API with requests so it made the API unresponsive , after removing the custom component the errors eliminated.
the component was the midea control version 0.1.5 in case you use the same. (the developer made changes and 0.1.6 does not do the flooding so everything is fine now on my end).

10

Thanks for the update. I’m not using that component.