Omada software controller does not correctly count client traffic on a full Omada supported network. These numbers are inflated massively to the point of ridiculousness. See attached from 5.14.30.7, but the same behaviour has existed from 5.13.

.

Using the last release 5.13.x controller software, as well as the latest 5.14.x beta, the software controller shows ridiculous numbers for client traffic. This is a relatively new setup (2-3 months) and has never shown correct traffic. I can see many threads around the interwebs mentioning similar issues. Any progress with this issue? Seems ridiculous such a simple feature can be so broken, completely removing the ability to see which client has downloaded in bulk.

The top machines are all linux based and from SSH the interfaces report normal traffic, i.e. a few GB at most. Also the switches are reporting normal sized traffic via Omada controller, again nothing like these client stats.

Here is my topology: