Thank you. I had commented it out and was getting an authentication error, but I couldn’t figure out what was triggering it. Ended up a system reboot and it went away.
And as soon as I typed that, the authentication error popped up again.
I’ll try un-commenting the api password and see if that stops it. Problem is, I don’t know what’s causing it.
Yes, I have several of those.
Please change to use bearer token access /api/
Please change to use bearer token access /api/services
Please change to use bearer token access /api/events
Please change to use bearer token access /api/states
I don’t think so? At least not intentionally.
I have a pretty basic setup and haven’t exposed anything yet, so I’m not using SSL, Encryption, DNS… yet.
It’s Hass.io that I’m running on HassOS (64bit).
I do have MQTT Mosquito setup, but I was using a username/password before switching to the new authentication. So I don’t think MQTT is the issue.
Everything else seems to show up properly in the UI, so I’m not sure what it is.
Nope, no iOS.
And the error popped up again with api_password setup, so I’ll go ahead and comment it out again.
The warning that keeps appearing is:
Login attempt or request with invalid authentication from 172.30.32.2
My internal network is 192.168… so I’m guessing that’s something local on the Hass box.
Its the IP address of your hassio_supervisor I believe. It’s used for DNS IP for hassio I think as well, since supervisor handles that? I think its saying some internal app/add-on/dns query isn’t getting the right authentication?