Clarify Companion WiFi CLI availability
This commit is contained in:
1 parent
256eb26b17
commit
19c9faab9c
4 files changed
+28
-13
No files matched your search
@@ -175,14 +175,15 @@ maintain the repeater administrator neighbor table.
|
||||
Even in a FULL build, a command can be unavailable when its underlying feature
|
||||
does not exist on that target:
|
||||
|
||||
- WebConfig and the `wifi.ssid`, `wifi.status`, `wifi.powersave`, and `wifi.cli` command
|
||||
- WebConfig and the `wifi.ssid`, `wifi.status`, and `wifi.powersave` command
|
||||
family require an ESP32 WebConfig build. FULL standalone repeater and
|
||||
room-server builds support the corresponding WiFi setters and status
|
||||
commands. ESP32 WiFi Companions with WebConfig expose WiFi credentials,
|
||||
connection status, WebConfig, CLI-tab, and power-save controls from their USB
|
||||
connection status, WebConfig, and power-save controls from their USB
|
||||
text terminal as well as power saving through WebConfig and the binary
|
||||
protocol. Full Companion additionally exposes its complete role-specific
|
||||
text terminal on TCP port 5002.
|
||||
protocol. The browser CLI tab and `wifi.cli` setting are repeater/room-server
|
||||
features. Full Companion instead exposes its complete role-specific text
|
||||
terminal on TCP port 5002.
|
||||
- MQTT commands require an MQTT observer target.
|
||||
- `discover.scopes` requires an MQTT observer with compiled neighbor support;
|
||||
it does not independently require PSRAM or the FULL parser.
|
||||
|
||||
Reference in new issue
Block a user