Need help to understand device tracking configuration / documentation

Configuration
1

I have some trouble to understanding the documentation, maybe because I missed some release notes when things changed, so sorry for these maybe obvious questions.

Regarding asuswrt presense detection. Now when asuswrt is its own component, do I still need to have it configured as device tracker in configuration.yaml, like below - or is that redundant?

asuswrt:
  host: 192.168.x.x
  username: xxxx
  password: !secret xxxx

device_tracker:
  - platform: asuswrt

Kind of same question regarding Owntracks (and GPS logger), I had it setup as a platform under device_tracker some year back…then I had some issues with it but did not have time to tinker and make it work. Now I am trying to make this stuff work again and noticed there are possibilities to configure both Owntracks (and GPS logger) in the web UI under Configurations / Integrations. Is this the only configuration needed, or do I also need to have them manually configured by editing configuration.yaml, like below - or is that redundant?

device_tracker:
  - platform: asuswrt
  - platform: owntracks
2

I am trying to get owntracks running. As I read the documentation of owntracks (and there is also a good video) you have to do both: In the WebUI and in the configuration.yaml.
And some stuff in the App on your phone.

3

It’s not just you. the documentation for the new component is horrible.

technically, all you should have to put in your configuration.yaml is the following and it will enable the device_tracker component by default:

asuswrt:
  host: 192.168.1.1
  username: !secret asus_username
  password: !secret asus_pwd

but if you need more config you can put other stuff in like this:

device_tracker:
  - platform: asuswrt
    interval_seconds: 10
    consider_home: 180
    new_device_defaults:
      track_new_devices: False
      hide_if_away: False
4

@finity Thanks, then I understand the configuration for asuswrt better.

@gilbert-grape Right, I watched the video and now noticed a possible third way to configure Owntracks on HA:

A) Using in the WebUI Configuration / Integrations.

B) Adding it as a platform under device_tracker in configuration.yaml

device_tracker:
  - platform: owntracks

C) Adding it as its own section/component in configuration.yaml.

owntracks:
  max_gps_accuracy: 100
  waypoints: true

So, maybe it like this…great if someone can confirm:
A) is a handy way to get the info for client configuration, no doubt about that.
C) seems to be the way to add “advanced configuration” to owntracks (and not needed if you don’t need to go advanced…)
B) might be the “old way” and not needed any longer (as it is not mentioned in the documentation)?