Unify device controls and restore the WiFi console

This commit is contained in:
mikecarper committed 2026-09-08 18:36:23 -07:00
1 parent 3746f9d5f4
commit 4c8aad5b16
44 files changed
+3573 -2948

No files matched your search

+3 -2
View File
@@ -16,8 +16,9 @@ Generated/ignored build directories and external repositories were outside that
entries are identified rather than linked to substitute hardware.
- Corrected universal 254-neighbor claims, Full Companion MQTT filename/CLI
assumptions, TLora Full WebConfig availability, and partition/NVS guidance.
- Distinguished infrastructure bare `powersaving on` guards from the separate
`set powersaving on` form; corrected the RS232 baud range and SNMP environment list.
- Documented the power-saving guards present at audit time; current instructions
now use the shared `get powersaving` / `set powersaving on|off` command set.
Corrected the RS232 baud range and SNMP environment list.
- Linked OTAFIX 2.4.6 and its board/storage requirements from operator guides;
aligned the two manual USA OTA quickstarts with 910.525 MHz.
- Marked old provider catalogs and dated hardware results as historical;
+9 -8
View File
@@ -104,14 +104,14 @@ disable power saving first. Use the role's text terminal, or the repeater's
remote admin CLI if USB has already disappeared:
```text
powersaving off
set powersaving off
set usb.logging on
powersaving
get powersaving
get usb.logging
```
The read-back commands should report power saving `off` and USB logging `on`.
For an image without USB logging, use just `powersaving off` and `powersaving`
For an image without USB logging, use just `set powersaving off` and `get powersaving`
to apply/check the sleep workaround. Disabling power saving saves the setting and takes
effect immediately; it does not erase the node or change LoRa RX power
saving (`radio.rxps`). If USB does not reappear after disabling sleep
@@ -120,17 +120,18 @@ usable beyond the two-minute mark. Ordinary reflashing can retain the
saved power-saving setting, so check it during comparisons with another
firmware build too.
On unified Full infrastructure, also run `powersaving off` before enabling
On unified Full infrastructure, also run `set powersaving off` before enabling
USB through `set logging.output usb` or `set logging.output both`. These are
separate commands. Turning logging off does not automatically restore the
saved power-saving setting. nRF52 logging does not need this ESP32 workaround.
**WiFi/MQTT-only logging does not need `powersaving off` while the
**WiFi/MQTT-only logging does not need `set powersaving off` while the
Repeater/Room Server MQTT bridge is running.** The original `26303793` code
already prevents device sleep in that state. Select `set logging.output wifi`
where supported and check `get bridge.running`; `get bridge.enabled` alone
only checks the saved preference. Full Companion MQTT uses WebConfig instead
of infrastructure `logging.output`/`bridge.*` commands.
where supported and check `get mqtt.running`; `get mqtt.enabled` alone
only checks the saved preference. MQTT-capable Full Companion now uses the
same `mqtt.enabled` and `logging.output` commands as infrastructure. Disabling
MQTT preserves broker settings; the MQTT tab exposes the same master switch.
The source correction keeps native USB serviced while a host is enumerated,
including when its terminal is closed. Enabled live USB logging also blocks