Unification

Don’t know if it’s possible - but currently there are over 500+ components.
Navigating through them is really complicated.
For example in presence there are around 15 out of 32 components dedicated to different routers. With more and more brands added it…
Most of them work the same through the dnsmasq.leases file. I think it will make more sense to have a single Router component. It doesn’t even need code unification. But than in the config you just state

- router_component
    type: asus (open_wrt e.t.c)

and here goes the config for each. Same for the doc page

1 Like

If you have a better idea to organize the component/platform overview, please open a PR.

Not really but they need to get the data from somewhere. Using

- router_component
  type: asus

instead of

device_tracker:
  - platform: asuswrt

wouldn’t be a huge win from my point of new. Sure, it would divide the device trackers into router-based and the others but a router component would imply something different than presence detection.

a HA website search feature would be nice

2 Likes