fix: reduce repeater web panel pressure and improve mqtt diagnostics

This commit is contained in:
Jared Dohrman
2026-04-13 09:42:32 +10:00
parent 9e0cff9e70
commit de071cbb79
7 changed files with 188 additions and 156 deletions
+1 -1
View File
@@ -93,7 +93,7 @@ It is the traditional way to configure a repeater after flashing, including:
- flood max
- some advanced repeater settings
As of `v1.2.1`, the local repeater web panel also includes the same common repeater settings, so many users can continue day-to-day configuration there after initial setup.
As of `v1.2.1`, the local repeater web panel also includes the same common repeater settings, so users can complete initial setup there and return for occasional troubleshooting or configuration changes. On MQTT repeaters that need maximum headroom, it is still best to disable the panel again when you are finished.
### Console
+30
View File
@@ -17,6 +17,12 @@ It gives you:
- editable MQTT settings
- a stats dashboard with Wi-Fi, core, radio, memory, and packet views
Operational guidance:
- use it for initial setup, occasional configuration changes, and troubleshooting
- when you are finished, prefer `set web off` on MQTT repeaters that need maximum headroom
- this leaves more internal heap available for MQTT/WSS activity, especially on dual-broker setups
## Screenshot Overview
The layout below reflects the current panel structure for the repeater web UI.
@@ -62,6 +68,18 @@ Example:
This is intended for local admin use on a trusted network, not for open internet exposure.
## Performance Notes
The panel is designed to load more gently than earlier versions. On login it now fetches sections in sequence instead of requesting one large bootstrap payload up front.
Even with that change, the panel still uses HTTPS and internal heap. On boards running one or two WSS MQTT brokers, opening the panel reduces MQTT headroom while the session is active.
Recommended practice for repeater deployments:
- enable the panel for initial configuration
- use it again for occasional checks or troubleshooting
- disable it with `set web off` when finished so MQTT has the most headroom available
## Actions
The Actions panel gives you the most common operational controls:
@@ -210,6 +228,18 @@ Check:
Use the repeater admin password, not the guest password.
### MQTT becomes unstable when I log in
The web panel now loads settings section-by-section to reduce startup pressure, but HTTPS still consumes internal heap.
Check:
- whether one or two MQTT brokers are enabled
- `memory` before and after login
- whether stability improves after `set web off`
For fixed installations where MQTT uptime matters more than browser access, use the panel briefly and then disable it again.
### A command says it is not allowlisted
The panel intentionally limits what can be run from the browser. Use the serial CLI for commands outside the web allowlist. `clock` is included, but most maintenance and debug commands are still serial-only.