30.08.2021, 06:02
I guess it's not correct to include it because the load is not in the actual KNX bus / TP
Also I wonder if using telegram counting is the most correct way to establish the load - please correct me if I'm wrong, but it seems like in the case of TP the limitation is the bandwidth rather than the 'telegram rate', and due to different telegram sizes the maximum rate of telegrams/sec could alternate between 20-40 or so. In the Wiser (and I guess LM) UI the rate is used to establish the load, with a assumed maximum of 30 telegrams/sec - which could be wrong.
Seems like it be more accurate to look a the RX/TX/Repeat bytes instead of telegrams, knowing the maximum is 9.6 kbits/s - this way we could establish and display a 100% accurate KNX bus load with no assumptions.
Would be nice for the bytes stats to be exposed in knxlib.getstats()
Also I wonder if using telegram counting is the most correct way to establish the load - please correct me if I'm wrong, but it seems like in the case of TP the limitation is the bandwidth rather than the 'telegram rate', and due to different telegram sizes the maximum rate of telegrams/sec could alternate between 20-40 or so. In the Wiser (and I guess LM) UI the rate is used to establish the load, with a assumed maximum of 30 telegrams/sec - which could be wrong.
Seems like it be more accurate to look a the RX/TX/Repeat bytes instead of telegrams, knowing the maximum is 9.6 kbits/s - this way we could establish and display a 100% accurate KNX bus load with no assumptions.
Would be nice for the bytes stats to be exposed in knxlib.getstats()
Thank you!
Morkov
Morkov