It sounds like your management interface isn't configured correclty is all.  You'll have to make sure the uplinked Cisco switchport interface has your management VLAN set as native on the trunk.

Something like:
int Gi1/01
 switchport mode trunk
 switchport trunk native vlan 20 (or whatever your management vlan omada resides in )
 switchport trunk nonegotiate ( need this for non-cisco devices to trunk )

This should allow the switches to grab IPs if they are set to dhcp, or should be reachable statically if they are already set static to that network. They should then be reachable by Omada, assuming Omada is also in that management network.
 
The switch vlan interfaces don't work like Ciscos do.  Took me a bit to work that out.

  @JdubL So i gave the TP Link a static ip on vlan 5 that is used as management, I tried your suggestion still no dice, how would port need to look to be a "trunk"

this is the current settings on the tp link port 16

switchport general allowed vlan 5,10,12,16,24,32,99,1021-1022 tagged
  switchport pvid 5
 

If you also issued the commands i listed for vlan 5 (native and nonegotiate) on the cisco side, the tp-link switch should connect to omada assuming its management settings are correct there too. Here is my port that works just fine:

!

interface GigabitEthernet1/0/47

 description Uplink to SD101-SG2008

 switchport trunk native vlan 2

 switchport mode trunk

 switchport nonegotiate

 !

Vlan 2 is the management vlan where the rest of the network gear sits. You probably also would need your omada controller in that vlan if you want things to be easy from there.