deploy: 0e0aa8e014

cli_commands/index.html

@@ -1149,6 +1149,17 @@
     </span>
   </a>
   
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#turn-wifi-esp-now-or-all-24-ghz-services-on-or-off" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        Turn WiFi, ESP-NOW, or all 2.4 GHz services on or off
+      
+    </span>
+  </a>
+  
 </li>
         
           <li class="md-nav__item">
@@ -5520,6 +5531,17 @@
     </span>
   </a>
   
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#turn-wifi-esp-now-or-all-24-ghz-services-on-or-off" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        Turn WiFi, ESP-NOW, or all 2.4 GHz services on or off
+      
+    </span>
+  </a>
+  
 </li>
         
           <li class="md-nav__item">
@@ -8346,6 +8368,73 @@ Station G2/G3 targets default to <code>off</code>.</p>
 <p><strong>Default:</strong> Varies by board</p>
 <p><strong>Note:</strong> Advertised names can use up to 23 bytes when location is included and 31 bytes otherwise. Emoji and Unicode characters may take more than one byte. Names that exceed the available advert space are truncated at a valid UTF-8 code point boundary.</p>
 <hr />
+<h4 id="turn-wifi-esp-now-or-all-24-ghz-services-on-or-off">Turn WiFi, ESP-NOW, or all 2.4 GHz services on or off</h4>
+<pre><code class="language-text">get wifi
+set wifi off
+set wifi on
+get espnow
+set espnow off
+set espnow on
+get 2.4ghz
+set 2.4ghz off
+set 2.4ghz on
+set 2.4ghz on all
+</code></pre>
+<table>
+<thead>
+<tr>
+<th>Control</th>
+<th>Effect</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td><code>wifi</code></td>
+<td>Infrastructure WiFi, setup AP, TCP/WebUI, and WiFi MQTT services. ESP-NOW remains available.</td>
+</tr>
+<tr>
+<td><code>espnow</code></td>
+<td>The ESP-NOW bridge or primary ESP-NOW mesh transport in this build. Infrastructure WiFi remains available.</td>
+</tr>
+<tr>
+<td><code>2.4ghz off</code></td>
+<td>Stop WiFi, Bluetooth, and ESP-NOW; remember which were enabled. LoRa and wired transports remain available.</td>
+</tr>
+<tr>
+<td><code>2.4ghz on</code></td>
+<td>Restore the states saved by the first <code>off</code>. Repeated <code>off</code> preserves that snapshot. With no previous <code>off</code>, keep the current states.</td>
+</tr>
+<tr>
+<td><code>2.4ghz on all</code></td>
+<td>Enable every service available in this build and boot. <code>2.4ghz on force</code> is an alias.</td>
+</tr>
+</tbody>
+</table>
+<p>These commands work in Companion, repeater, and room-server firmware where the
+services are available. Changes last until reboot; saved WiFi credentials,
+Bluetooth preferences, and bridge settings stay intact. <code>get 2.4ghz</code> lists each
+service as <code>on</code>, <code>off</code>, or <code>unavailable</code>. An nRF52 Companion controls its Bluetooth
+and reports WiFi/ESP-NOW as unavailable. Exclusive WiFi/Bluetooth builds retain
+their boot transport restriction; <code>on all</code> cannot reclaim a released Bluetooth stack.</p>
+<p>An <code>off</code> command requires a management connection that will survive it. Bluetooth
+can provide the fallback for <code>wifi off</code>; USB, Ethernet, or a CLI request over LoRa
+can provide it for <code>2.4ghz off</code>. WiFi association, a listening socket, and USB power
+alone do not count. On USB hardware without an observable open-client session,
+send the command through USB itself. To bypass the guard:</p>
+<pre><code class="language-text">set wifi off force
+set espnow off force
+set 2.4ghz off force
+</code></pre>
+<p>Shutdown starts after the reply has had time to drain (normally 250 ms, up to two
+seconds for pending transport I/O). Network services stop before the shared WiFi
+driver. A normal shutdown is cancelled if its fallback connection disappears
+before it starts. The <code>get</code> commands report pending changes and startup/teardown
+failures. After <code>2.4ghz off</code>, use <code>2.4ghz on</code> or <code>on all</code> before enabling an
+individual service. The <code>all</code>/<code>force</code> suffix on <strong>on</strong> applies only to <code>2.4ghz</code>.</p>
+<p>WiFi and ESP-NOW share one hardware channel. A running ESP-NOW bridge pins setup
+and station connections to <code>bridge.channel</code>; starting the bridge alongside an
+existing WiFi connection requires that same channel. A mismatch reports a failed
+start and preserves the WiFi connection.</p>
 <h4 id="turn-bluetooth-on-or-off-companion">Turn Bluetooth on or off (Companion)</h4>
 <pre><code class="language-text">get bluetooth
 set bluetooth off