Authentication deprecated issues

In my home-assistant-log file i find these:

2019-05-06 22:24:32 WARNING (MainThread) [homeassistant.components.http.auth] api_password is going to deprecate. You need to use a bearer token to access /api/ios/identify from x.x.x.x
2019-05-07 08:13:13 WARNING (MainThread) [homeassistant.components.http.auth] api_password is going to deprecate. You need to use a bearer token to access /api/config from x.x.x.x
2019-05-07 08:13:14 WARNING (MainThread) [homeassistant.components.http.auth] api_password is going to deprecate. You need to use a bearer token to access /manifest.json from x.x.x.x
2019-05-07 08:13:14 WARNING (MainThread) [homeassistant.components.http.auth] api_password is going to deprecate. You need to use a bearer token to access /api/states from x.x.x.x
2019-05-07 16:28:09 WARNING (MainThread) [homeassistant.components.http.auth] api_password is going to deprecate. You need to use a bearer token to access /api/services/device_tracker/see from x.x.x.x

How can I find out which components they come from, and how can I fix them?
I thought I could fix the iOS ones by removing and re-adding the iOS integration, but that didn’t work.
And the others seem quite anonymous to me.
Is it possible to log some more info on the sources of the errors? Or better, fix them?
hassio 0.92.2 on Intel NUC Debian 9.

I have this error as well. Feeling like I’m a sitting duck for a big problem when support for api_password is removed. (I do not have api_password defined in configuration.yaml).

Any suggestions for how to track this down?

Having the exact same error… I wonder what happens!

The IP address should give you a hint, as will the path.

In your case, I’d guess the first is probably an outdated iOS app.

The simplest approach here is to perform the scream test. Pick a suitable time, disable the api_password, and see what breaks.

Anyone using HADashboard and camera streams. That’s one area that will cause issues. Don’t think camera streams will accept long term tokens as of yet.