@AndreyZh 

 

what controller are you using? If I remember correctly, there was something about this on the forum here earlier, but I can't find it again. but there is a beta version you can test. I use windows controller 5.14.20.9 with this beta version for the router. I see clients. it's in a lab so there are only a few clients but I see them.

 

 

Here you can download the firmware for your router

 

https://community.tp-link.com/en/business/forum/topic/669388

 

Thanks! I'm using 5.14.20.9 as well. I figured out that if I plug out my (non-Omada) switch, at least most of the wired devices (physical) are now visible. The VM is still not. It's a tad funny, because there were no clients connected to that switch at all. Why would it mess up discovery. Seems like a bug to me.

  @AndreyZh hello. I also had similar problems. In my case they told me that the bug was in controller 5.14.20.9 that caused this behavior and that they would fix it in the next version. I leave you the post in case it helps you. 

 

https://community.tp-link.com/en/business/forum/topic/670358?replyId=1370020

 

If this is your case, these would be your possible solutions:

 

-Add switches that are omada to your network

 

-Wait for the next version of the omada controller

 

-roll back to the known stable version of the omada controller (you must have a backup that has been made in said version. Since backups of newer versions are not compatible with older versions)