repeater-mqtt-eastmesh-v1.3.8

docs/api.md

@@ -152,6 +152,7 @@ Notes:
 
 - this summary view is also what the repo's web panel requests first before loading trend series
 - if `web.stats` is disabled, the endpoint returns `503 Service Unavailable`
+- supported boards may also include an optional `sensors` object in the summary payload for current GPS and environmental telemetry
 
 ### `GET /api/stats?series=<name>`
 
@@ -164,6 +165,14 @@ Supported series:
 - `signal`
 - `noise_floor`
 - `packets`
+- `voltage`
+- `sensor_temp`
+- `humidity`
+- `pressure`
+- `pressure_altitude`
+- `mcu_temp`
+- `gps_altitude`
+- `gps_satellites`
 
 Example:
 
@@ -176,6 +185,7 @@ Notes:
 
 - use `?series=battery`, not just `?series`
 - the built-in web panel loads these series sequentially rather than all at once to keep board memory pressure lower
+- environment series are included only when the board reports those readings; if a series has no captured points yet, it returns an empty `points` array and `current:null`
 
 ### `GET /api/stats?view=legacy`
 

docs/custom-cli.md

@@ -69,7 +69,7 @@ Legacy dotted aliases are also accepted:
 
 - `get web`
 - `get web.status`: shows whether the local HTTPS panel is available.
-- `get web.stats.status`: shows whether the dedicated stats page and history subsystem are enabled, whether recent history is active, whether PSRAM-backed history is available, and whether the SD-backed archive is mounted.
+- `get web.stats.status`: shows whether the dedicated stats page and history subsystem are enabled, whether recent history is active, whether PSRAM-backed history is available, and whether the SD-backed archive is mounted. When enabled, the history capture now covers supported environment telemetry too, not just the original battery/radio series.
 - `set web on|off`
 - `set.web on|off`: enables or disables the local HTTPS panel.
 - `set web.stats on|off`

docs/web-panel.md

@@ -191,10 +191,15 @@ The stats page is loaded separately from `/app` and is intended to keep the main
 The `/stats` page currently shows:
 
 - `Services`: MQTT, web, archive, neighbour count, and, when mounted, card and archive capacity
-- `Trends`: battery, heap free, packet activity, signal, and noise floor
+- optional full-width `Environment` summary card on boards that report GPS or environmental telemetry
+- `Trends`: battery, heap free, packet activity, signal, noise floor, and supported environment history such as voltage, temperatures, humidity, barometer, altitude, and, when GPS is enabled, satellites
 - `Neighbours`: current neighbour table with ID, SNR, heard age, and advert age
 - `Events`: current boot/session events
 
+For boards that expose extra telemetry, the optional `Environment` summary card can show current values such as GPS fix state, latitude, longitude, GPS altitude, voltage, sensor temperature, humidity, barometer, pressure-derived altitude, and MCU temperature.
+
+Metrics with no current value are hidden rather than showing placeholder rows, so the cards vary by board and by current sensor state.
+
 The trend graphs load sequentially rather than as one large payload:
 
 1. summary/status
@@ -202,10 +207,11 @@ The trend graphs load sequentially rather than as one large payload:
 3. memory
 4. packet activity
 5. signal
+6. remaining supported environment series
 
 This keeps browser-side and device-side memory use lower than the previous in-page stats view.
 
-If `web.stats` is enabled and an SD archive is mounted, trends can restore archived summary points after reboot. Recent live points are still added from in-memory history.
+If `web.stats` is enabled and an SD archive is mounted, trends can restore archived summary points after reboot. Recent live points are still added from in-memory history. This now includes the supported environment series as well as the original core/radio stats.
 
 ### Stats History Capacity