It seems the NetworkRate as reported by /status.json is very different from /tuner<n>/debug in net: bps=
Shouldn't they be the same?
Quoting Claude:
NetworkRate should be a rate (bytes/sec since last poll, or over a rolling window), not a counter that resets on an internal ~1s tick independent of poll timing.
status.json issues
Re: status.json issues
Just playing with it a bit, the debug number seems to be averaged over a longer period of time while the status.json is closer to instant, so the status one swings around more on channels encoded using variable bitrate.