Airtime
This is modelled airtime, not a measurement of the channel being busy. Over serial, BLE or TCP the bot is a client of a radio: it cannot see whether the channel was clear, only how long a packet of a given size occupies it at the current SF/BW/coding rate. Real occupancy (CAD, LBT) belongs to a radio driver, and a repeater's own occupancy comes from that repeater's API. The two shares are kept apart on purpose: rx is what this node hears — a local observation, not the airtime of the whole channel — and tx is what the bot spends itself.
Right now
enabled = true under
[Channel_Occupancy] in config.ini; nothing is recorded until then.
What is on screen was written while recording was on; the setting is off now.
The age above says how long ago that was.
History
A gap is not a zero: a period with no packet is absent from the result, so the line breaks there rather than dropping to 0. A bucket that was observed and held nothing on air stays a zero — those are two different facts, and a chart that draws the first as the second shows a cliff that reads as an outage. Percentiles are nearest-rank over the stored buckets, which is not the same measurement as the instant windows above.
Senders by airtime
| Sender | Airtime | Packets | Last seen |
|---|
Ranked by airtime, not by packet count: a talker sending many small packets can cost more than one sending a long message. Senders show once a packet is recorded, so this reflects the retention window, not all time.