tstock wrote

If the client has no hostname or is an android device, there isn't any difference between the clients, except the mac-address. So an alias name for a client would be wonderful.

No, the EAP controller doesn't support aliases for clients. The right place to set a client's hostname is either the client system itself or the DHCP server handing out IPs and (optionally) hostnames. As for the hostname there is no guarantee that a client requests it, but if it does it will get its name via DHCP.

tstock wrote

So is there hope, that this feature will be implemented in newer versions?

Only TP-Link can answer (I am not representing TP-Link, I'm a user just like you). But IMHO this feature isn't needed, since a) the hostname is displayed already if set correctly and b) the Controller is a management tool for hundreds of EAPs for deployment of hotspot systems with thousands of users. It doesn't make much sense to assign names to devices of anonymous users. In a small setup with only a limited number of users it could make sense, but then just set the hostname of those devices to see them in the controller's clients statistics.

hdmuzzillo wrote

Missing feature no doubt for me... seems no plans to update either...:(

 

As I wrote, the correct place to set hostnames is either the device itself (if you have control over it) or the DNS/DHCP service running on the router or a server (if you don't have control over the device).

 

For stationary devices it is no problem to add hostnames there - I'm doing this all the time. For non-stationary clients on a public hotspot it makes no sense to add hostnames since those devices might appear only once at all and probably will be never seen again.