Maleko wrote

Updated to 1.2.2 and the AP client percentage can be glitchy:

 

That's a typical floating point rounding error. Percentages should be computed using integers, not floating point numbers.

Why? Because a percentage with a digit behind the decimal point is nonsense – in fact it's per mill (‰), not per cent (%).

 

A percentage is already two digits behind the decimal point. For example, 31.6% is an abbreviation for 0.316. You would write 316‰ then.

 

Let's assume you have 19 users total and 6 users connected to EAP2. It shows 31.6% for EAP2, that's 6.004 users. Is that 6 users and 4 fingers from the 7th user? If it would show 31% instead, it would be correct enough to get the figure.

 

Also, why do the stats always reset after a reboot?

 

It's being reset b/c it's showing the actual number of users and amount of traffic over a certain (unknown) time span with kind of a decay function. After a reboot, the counters are zeroed.

 

Regarding the time-window: it woud be helpful to know the duration over which numbers are accumulated.

For example, when there are actually two clients, it often shows a different number of clients which had been associated recently:

 

 

A minute later it shows three users:

 

 

Three minutes later it shows the correct numbers:

 

 

Same with traffic, except that the time-window is much larger:

 

 

Some minutes later:

 

 

Ten minutes later:

 

Now, alls clients in total are 100.000000000000006%.  

 

Another eight minutes later:

 

 

 

The time window for updating the number of clients should be equal to the time window used by the function which updates the number of clients under »Stations« in the header. Also, the duration of the time window for accounting traffic per EAP should be displayed somewhere (e.g. »traffic over last 24 hours« or »traffic since last reboot« or whatever).