Short drop of WiFi connections can't be detected in Omada Controller if the disconnect state lasts under 5 minutes. WiFi associations/disassociations of clients are not logged in Omada Controller at all except for the current connection state visible in the controller's web UI.

To check for short disconnects over a test period you could set up the collectd statistics collector on a server and use the ping plug-in to check for connectivity of the clients. This software then produces a graph of the client's connection state.

Tip: OpenWRT-based routers can run collectd, setup is as easy as installing this software package on the router and configuring the ping plug-in. Such an OpenWRT router could also be used as a tiny, stand-alone Linux server. So, if you have an old WiFi router lying around somewhere, it could be abused as a monitoring device for the connection states of your client devices.

Admin_JOD wrote

Thanks for the info.

 

5 minutes seems like a long time to not keep track of information for troubleshooting purposes, really wish this limitation wasn't present on a business class device. 

Seems so, but if you have 500 APs with thousands of clients managed by the same controller, shorter connectivity check intervals would lead to much higher traffic. What's more, if the interval is too short, you will see more false positives in case of only short disconnects of the clients due to temporary interferences.

IMHO, best compromise would be to let the user choose the connectivity check interval/time-out for the detection of connection losses, so one could decrease this interval during tests and later restore the default value for regular use.