You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to propose a lightweight Repeater Stress (Health) Indicator to help identify overloaded or congested mesh nodes without increasing network traffic significantly.
The idea is not to expose many raw statistics, but to provide a single aggregated value that reflects the overall health of a repeater. The score could take existing internal metrics into account, such as:
Packet forwarding activity
Retry/error count
Duty cycle delays (if applicable)
LBT / Activity Detection (int.thresh) delays
The averaging window should be user configurable, for example:
1 hour: Live troubleshooting
24 hours: Daily operation
7 days (default): Network planning and long-term node health
The default 7-day view would highlight repeaters that are consistently under heavy load, while shorter windows would help diagnose temporary congestion.
This feature would make it much easier to identify repeaters that deserve a closer look without requiring users to manually interpret multiple statistics or continuously monitor the network.
I will run some tests.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I would like to propose a lightweight Repeater Stress (Health) Indicator to help identify overloaded or congested mesh nodes without increasing network traffic significantly.
The idea is not to expose many raw statistics, but to provide a single aggregated value that reflects the overall health of a repeater. The score could take existing internal metrics into account, such as:
The averaging window should be user configurable, for example:
The default 7-day view would highlight repeaters that are consistently under heavy load, while shorter windows would help diagnose temporary congestion.
This feature would make it much easier to identify repeaters that deserve a closer look without requiring users to manually interpret multiple statistics or continuously monitor the network.
I will run some tests.
Beta Was this translation helpful? Give feedback.
All reactions