# Get started

> Start with only your phone, then set up your first sensor when you need live radio work.

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

1. Install the beta. On iPhone or iPad, follow the [TestFlight guide](/app/ios/). On Android,
   follow the [Firebase guide](/app/android/). Invitation links are on [Downloads](/downloads/#mobile-apps).
2. Open the app and allow the permissions it asks for. Location access is needed for anything
   that reads Wi-Fi or position.
3. 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](/app/ios/#explore-without-a-sensor).
    - **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](/features/surveys/).
    - **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](/features/integrations/).

## How to set up your first sensor

1. **Pick a board.** [Compare sensors](/sensors/compare/) by job, radio and storage. If you already
   own hardware, check [compatibility](/sensors/compatibility/).
2. **Flash it.** For a NanoPi Zero2, Raspberry Pi 4 or 5, or WLANPi Pro or Go, follow the
   [unified sensor image guide](/guides/unified-sensor-image/). Download the **factory** image,
   verify its digest and flash the intended storage. Flashing erases it. **OTA** is only for an
   existing unified installation.
3. **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.TXT` on the CONFIGFS volume.
4. **Connect.** Make the sensor reachable, open **Devices** and connect as `wlanpi` with your
   password. [Connecting sensors](/guides/connecting-sensors/).
5. **First scan.** Select the sensor and radio, then scan the channel of an AP you know. Widen
   coverage once that works. [Scan & discover](/features/scanning/).

Then try a focused [capture](/features/capture/) or [survey](/features/surveys/), and
[save or export](/guides/files-and-exports/) what you find.

### Other hardware

| Your hardware | Setup route |
| --- | --- |
| ESP32-C5 | [Choose a board](/sensors/esp32-c5/#boards), [flash its firmware](/sensors/esp32-c5/flash/) and connect by Bluetooth |
| GL.iNet Mudi 7 | [Keep the GL.iNet firmware and install capture support](/sensors/mudi-7/) |
| Existing Linux sensor, AP or analyzer | [Check the exact model](/sensors/compatibility/) |

### 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](/features/device-website/).

## 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](/guides/troubleshooting/).