@cyruspy Easy answer...simply populate the boxed field below with your ideal description

  @cyruspy To do that I think you need to modify the polling routine.  You can change the sysNAME, you'll find it at 

OID .1.3.6.1.2.1.1.5.0

Add a few lines to the poller to query your controller for the hostname and then SET the value.

I know it's a PITA to access the controller and then overwrite the bootup value for the sysName parameter so I would suggest you submit a feature request to have all Omada devices overwrite their firmware derived sysName's with their managed names.

To make things a little easier, you could just overwrite the sysName with the IP address when you are polling (or its MAC address from .1.3.6.1.2.1.2.2.1.6.2), that way you'd only be operating in SNMP, and you'd be checking/fixing the record every time you poll.

  @cyruspy Second last forum in the 'Forums' pulldown.  Just create a new post there with a description of the feature/functionality, and maybe link this thread for more detail.  Then we can upvote it and try to get it on the development shortlist :)

To be clear, RFC3418 states:

   sysName OBJECT-TYPE
       SYNTAX      DisplayString (SIZE (0..255))
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
               "An administratively-assigned name for this managed
               node.  By convention, this is the node's fully-qualified
               domain name.  If the name is unknown, the value is
               the zero-length string."
       ::= { system 5 }

There is no hard and fast rule here that says it must be anything specific, and I do appreciate TPLink not making it "" either.

I'd be happy if they just copied or appended the eth0 MAC address of the device into the sysName field...that's a quick simple code change and far more likely to get done....and it makes it unique and the MAC component would allow you to do things like reverse the IP via ARP or DHCP tables.