What is the line in the log about serving the /api/

My HASSIO running on RPi 3B+ is very slow. Restarting is takes 5 minutes at least. Even stepping away and reloading a page of the UI requires a very slow reconnect. I have been removing components and automatons to try to isolate the bottleneck. In looking at the log I have nothing but a media center updated, the sun sensor and THIS:

2018-07-12 11:38:54 INFO (MainThread) [homeassistant.components.http.view] Serving /api/ to (auth: True)

I don’t recognize that IP address, and can’t find any information about it. Does anybody know anything about it? FYI when I saw it, I closed down port forwarding on my router as well.

Could it be DuckDNS? If so, why can’t I find any confirmation of that researching the IP addy?

you probably have @ludeeus 's custom component installed?

which shows which authenticated connections are made to your Hassio install.

see this thread for more info on being hacked (or not)

Did you intended to include a link to a thread about being hacked?

I don’t know if I have that installed because I’m running HASSIO which seems, much to my chigrin to hide a lot of details.

What’s even stranger, is the the HASSIO iPanel button has disappeared.

yes, because thats where the author of the CC posted about his component…
btw those 172. ip addresses are so-called internal ip addresses on your network

if you’re running it, you should have a sensor.last_succesful_authentication:

if you’re not you must have the logger.yaml set to info on homeassistant.components.http.view, otherwise it wouldn’t show up in the log.

Yes my config includes what was in the default set up:
default: info
Thanks for pointing me in the right direction.

Plus I figured out the iframe Hass.io link is only available if Discovery is in use.

that might also explain the long setup times, … error seems a better default value, only go lower if needed:

# https://home-assistant.io/components/logger/
# Possible log severities: critical, fatal, error, warning, warn, info, debug, notset

only learned recently myself:

if you have


explicitly in configuration.yaml, and don’t rely on discovery to find hassio, many hassio related issues are solved. Including Hassio always being in the sidebar. (ive had it disappear without any clear hint as to why, only got the config-error notification)

not any longer…such a relief.

How do I get rid of the info logs for that custom component?

I’ve tried setting the following in my logger section but it doesn’t work:

  default: warn 
    urllib3.connectionpool: error 
    homeassistant.components.http.view: warn
    custom_components.media_player.alexa: debug

I still get flooded with tghose logs ever second or two.