diff --git a/doc/ct2mhs01-wifi-standby.png b/doc/ct2mhs01-wifi-standby.png
new file mode 100644
index 0000000..70c961d
Binary files /dev/null and b/doc/ct2mhs01-wifi-standby.png differ
diff --git a/doc/faq.md b/doc/faq.md
index 74157ca..8281597 100644
--- a/doc/faq.md
+++ b/doc/faq.md
@@ -22,6 +22,12 @@ Please note that this file may contain sensitive information such as your IMSI a
 
 If you want to use a non-Verizon SIM card you will probably need an unlocked device. But it's not clear which devices are locked nor how to unlock them, we welcome any experimentation and information regarding the use of unlocked devices. So far most verizon branded orbic devices we have encountered are actually unlocked.
 
+### I can't reach my Rayhunter's web UI after leaving it alone for a while
+
+Some hotspots (notably the T-Mobile TMOHS1 and Wingtech CT2MHS01) shut down their Wi-Fi access point after about 10 minutes with no connected clients to save battery. Rayhunter is still recording in the background, but you won't be able to reach the web UI until you power cycle the device or reconnect a client while Wi-Fi is still up.
+
+To avoid this, set Wi-Fi Standby to "Always on" in the hotspot's native admin UI. See [TMOHS1](./tmobile-tmohs1.md#wi-fi-auto-shutdown) or [CT2MHS01](./wingtech-ct2mhs01.md#wi-fi-auto-shutdown) for step-by-step instructions.
+
 ### How do I re-enable USB tethering after installing Rayhunter?
 
 If you have installed with `./installer orbic-usb`, you might find that USB
diff --git a/doc/tmobile-tmohs1.md b/doc/tmobile-tmohs1.md
index 664e9f2..b027e9d 100644
--- a/doc/tmobile-tmohs1.md
+++ b/doc/tmobile-tmohs1.md
@@ -59,6 +59,21 @@ Then run the installer:
 | Paused           | WiFi LED blinks white.         |
 | Warning Detected | Signal LED slowly blinks red.  |
 
+## Wi-Fi auto-shutdown
+
+By default the TMOHS1 turns off its Wi-Fi access point after 10 minutes with no connected clients. Rayhunter keeps recording on the device in the background, but once the access point is down you can't reach the web UI, download captures, or see new warnings until you power cycle the hotspot.
+
+The TMOHS1's native admin UI lets you change this:
+
+1. Connect to the TMOHS1's Wi-Fi (or USB tether).
+2. In a browser open `http://192.168.0.1/` and log in with the admin password.
+3. Go to **Settings** → **Sleep** → **Wi-Fi Standby** and pick **Always on**.
+4. Click **Apply**.
+
+![TMOHS1 Wi-Fi Standby setting](./tmohs1-wifi-standby.png)
+
+Keeping Wi-Fi always on uses more battery. If you only monitor Rayhunter through the device's LEDs and don't need remote access, the default 10-minute timer is fine.
+
 ## Obtaining a shell
 Even when rayhunter is running, for security reasons the TMOHS1 will not have telnet or adb enabled during normal operation.
 
diff --git a/doc/tmohs1-wifi-standby.png b/doc/tmohs1-wifi-standby.png
new file mode 100644
index 0000000..d384e28
Binary files /dev/null and b/doc/tmohs1-wifi-standby.png differ
diff --git a/doc/wingtech-ct2mhs01.md b/doc/wingtech-ct2mhs01.md
index 8c631f2..b37cf0c 100644
--- a/doc/wingtech-ct2mhs01.md
+++ b/doc/wingtech-ct2mhs01.md
@@ -54,6 +54,21 @@ telnet 192.168.1.1
 adb shell
 ```
 
+## Wi-Fi auto-shutdown
+
+By default the CT2MHS01 turns off its Wi-Fi access point after the configured sleep timer (default 10 minutes) with no connected clients. Rayhunter keeps recording on the device in the background, but once the access point is down you can't reach the web UI, download captures, or see new warnings until you power cycle the hotspot.
+
+The CT2MHS01's native admin UI lets you change this:
+
+1. Connect to the Wingtech's Wi-Fi (or USB tether).
+2. In a browser open `http://192.168.1.1/` and log in with the admin password.
+3. Go to **Settings** → **Sleep** → **Wi-Fi Standby** and pick **Always on**.
+4. Click **Save**.
+
+![CT2MHS01 Wi-Fi Standby setting](./ct2mhs01-wifi-standby.png)
+
+Keeping Wi-Fi always on uses more battery. If you primarily monitor Rayhunter through the device's screen and don't need remote access, leave the timer at its default.
+
 ## Developing
 The device has a framebuffer-driven screen at /dev/fb0 that behaves
 similarly to the Orbic RC400L, although the userspace program
diff --git a/installer/src/tmobile.rs b/installer/src/tmobile.rs
index f378780..2891f3f 100644
--- a/installer/src/tmobile.rs
+++ b/installer/src/tmobile.rs
@@ -94,5 +94,11 @@ async fn run_install(admin_ip: String, admin_password: String) -> Result<()> {
 
     reboot_device(addr, "reboot", &admin_ip).await;
 
+    println!();
+    println!("Note: by default the TMOHS1 shuts off Wi-Fi after 10 minutes with no clients,");
+    println!("which blocks remote access to Rayhunter until you power cycle. To keep");
+    println!("Wi-Fi always on, open http://{admin_ip}/ -> Settings -> Sleep and set");
+    println!("Wi-Fi Standby to \"Always on\". See doc/tmobile-tmohs1.md for steps.");
+
     Ok(())
 }
diff --git a/installer/src/wingtech.rs b/installer/src/wingtech.rs
index ff2a87e..2a1725e 100644
--- a/installer/src/wingtech.rs
+++ b/installer/src/wingtech.rs
@@ -144,6 +144,12 @@ async fn wingtech_run_install(admin_ip: String, admin_password: String) -> Resul
 
     reboot_device(addr, "shutdown -r -t 1 now", &admin_ip).await;
 
+    println!();
+    println!("Note: by default the CT2MHS01 shuts off Wi-Fi after ~10 minutes with no clients,");
+    println!("which blocks remote access to Rayhunter until you power cycle. To keep");
+    println!("Wi-Fi always on, open http://{admin_ip}/ -> Settings -> Sleep and set");
+    println!("Wi-Fi Standby to \"Always on\". See doc/wingtech-ct2mhs01.md for steps.");
+
     Ok(())
 }