To be honest, I think there is a use case for tracking by hostname / alias (as viewed by the controller) as it’s a little more user friendly than MAC addresses.
I was thinking about this on my way to the office today and the binding could easily be adapted to accept either a MAC address or hostname as the unique identifier. However, this means the config parameter shouldn’t be called
mac anymore as it would accept both MAC addresses and hostnames as valid inputs.
The other option would be to just simply accept hostnames in the MAC address parameter (as a workaround for these edge-cases) and leave it as an undocumented easter egg.
@martinvw can you chime in on this?