WLAN Commander runs on your phone. Live Wi-Fi scanning and packet capture need an external radio, a sensor, but several tools work with the phone alone.
How to start with only your phone
- Install the beta. On iPhone or iPad, follow the TestFlight guide. On Android, follow the Firebase guide. Invitation links are on Downloads.
- Open the app and allow the permissions it asks for. Location access is needed for anything that reads Wi-Fi or position.
- Try the tools that need no sensor:
- Files samples (iPhone and iPad): open Files › On This Device for a bundled sample beacon scan and packet capture. They use synthetic identifiers. More about the samples.
- Location: where the phone thinks it is, how it is moving, and how high.
- Survey preparation: add floor plans and walk a route. Without a sensor a walk records positions only. Survey & map.
- The phone's own Wi-Fi: on iPhone, the Wi-Fi tab shows the current connection, with live signal through a Shortcut. On Android, More › Phone WiFi monitors the phone's connection and More › WiFi RTT runs 802.11mc/az distance ranging.
- Ruckus One and assistants: see Integrations.
How to set up your first sensor
- Pick a board. Compare sensors by job, radio and storage. If you already own hardware, check compatibility.
- Flash it. For a NanoPi Zero2, Raspberry Pi 4 or 5, or WLANPi Pro or Go, follow the unified sensor image guide. Download the factory image, verify its digest and flash the intended storage. Flashing erases it. OTA is only for an existing unified installation.
- First boot. Use stable power, and Ethernet where you have it; the Go uses USB. Allow several
minutes for first setup. Complete the one-time claim and set your password. Direct USB fills
the code automatically; otherwise use the code in
WC-SETUP.TXTon the CONFIGFS volume. - Connect. Make the sensor reachable, open Devices and connect as
wlanpiwith your password. Connecting sensors. - First scan. Select the sensor and radio, then scan the channel of an AP you know. Widen coverage once that works. Scan & discover.
Then try a focused capture or survey, and save or export what you find.
Other hardware
| Your hardware | Setup route |
|---|---|
| ESP32-C5 | Choose a board, flash its firmware and connect by Bluetooth |
| GL.iNet Mudi 7 | Keep the GL.iNet firmware and install capture support |
| Existing Linux sensor, AP or analyzer | Check the exact model |
Use the sensor without the app
A claimed unified sensor has its own website at https://DEVICE_ADDRESS/, or https://198.18.42.1/
over direct USB with one sensor connected. It runs speed tests, radio tools and health checks with no
app invitation. Device website tour.
If discovery or a scan fails
Finding an address is not the same as a signed-in connection. Check power, cable, reachability, credentials, the selected radio and its legal channels. A connected sensor stays idle until you start a scan. Troubleshooting.