Error on call

Installation Home Assistant OS
1

I have been searching many topics on this but I cannot find a solution and or no solution was given. But most things talk of node red or docker but I am running on RP4 without node red or docker. My issue seems to cause me to lose connection with HA and I am forced to close and open the app again to be able to connect and then after I finally am able to get to log in I have a authentication error
Login attempt or request with invalid authentication from 192.168.1.189 and then there are many error on call errors in the log.

20-07-05 23:00:38 ERROR (MainThread) [supervisor.homeassistant] Error on call http://172.30.32.1:8123/api/config: 20-07-05 23:01:14 ERROR (MainThread) [supervisor.homeassistant] Error on call http://172.30.32.1:8123/api/config: 20-07-05 23:01:27 ERROR (MainThread) [supervisor.homeassistant] Error on call http://172.30.32.1:8123/api/config: 20-07-05 23:01:50 ERROR (MainThread) [supervisor.homeassistant] Error on call http://172.30.32.1:8123/api/config:

As it stands my install is super unstable and a PITA to use, I believe my issue is the error on call which started to ahppening on version .111 before .111 I had no such error.

2

If you have supervisor, you have docker :slight_smile:

Are you having this issue with the iOS or Android App ? What if you use the browser to connect ?

3

Good to know, I am using the Android App and its also happening with the browser, randomly when opening the app it will refuse to connect and if I wait for like 30 seconds eventually it will load and when checking the logs it will have that error on call error during the time I was unable to connect so it seems like its failing to authenticate my phone right away. As for the browser it randomly looses connection so no live updates with lovelace until I hit refresh, found a work around for that with Fully Kiosk and have it refresh every hour.
Also during those times I’m unable to connect if I have an automation set to run it gets delayed by minutes until everything catches up.

4

OMG finally figured it out after weeks of trial and error, it was Appdaemon trying over and over to access my system. I guess it was improperly setup and after I disabled it the errors stopped!