ZeroTrace Mobile
Pairing & Auto-detect
Connect a ZeroTrace device over Bluetooth LE and let the app recognise which family it belongs to.
Pairing a device
Every ZeroTrace device connects to the app over Bluetooth LE. There is no pairing PIN, no Wi-Fi setup and no cable required, you scan, you tap, you are connected.
- Power on the device
Give the device power (battery or USB). It starts advertising over Bluetooth LE as soon as it is on, under a short name that hints at its family, see the table below.
- Scan from the hub
Open the app to its device hub and start a scan. The app filters the air for ZeroTrace devices by their advertising signature, so your list stays clean, you see your gear, not every phone and earbud in the room.
- Select your device
Tap the device you want. The app connects over BLE, no PIN or confirmation code to type in.
- Let the app configure itself
On connect, the device reports its own firmware type. The app resolves that to one of four device families and loads exactly the screens that family supports, instantly, with nothing for you to pick by hand.
Your paired devices are remembered, so the next time you open the app they are ready to reconnect without scanning again. You can keep several devices saved in the hub and switch between them freely, each keeps its own connection state, settings and history.
How auto-detect works
The app never asks you what you plugged in. Two things happen automatically:
- The scan recognises a ZeroTrace device. Every device advertises with a manufacturer-data signature and a short name prefix specific to its family, so the app's scan can tell a ZeroTrace device from the rest of the Bluetooth traffic around you before you even connect.
- The connected device reports its firmware type. Once connected, the device tells the app what firmware it's running. The app maps that to a device family and switches its whole UI, tabs, screens, settings, to match.
This is why the app never has a "select your device model" screen: the device tells the app what it is, every time.
Family reference
| Family | Advertised name prefix | What loads in the app |
|---|---|---|
| HID | ZT- | Executor script editor, live mouse, gamepad, files, TraceNet, layouts. See HID in the app. |
| AirLeak | AL- | Live BLE view, Hunt, Drive (wardrive map), Insights, Signals, Capture. See AirLeak in the app. |
| AirLeak Pro | AP- | Live, Hunt, Insights, the Ops suite, Files, GPS Drive map, Capture. See AirLeak Pro in the app. |
| Echo | EC- | Live, Capture, Decode, Brute, Defense, Ops. See Echo in the app. |
| USBLogger | KL- | No dedicated screens, falls back to the HID tab set (see below). |
If a device connects but reports a firmware type the app does not recognise, whether that's a fresh re-flash mid-way through a build, or firmware the app's current version predates, the app falls back to the HID screen set rather than refusing the connection. That keeps a device usable the moment it can talk over Bluetooth, even before the app knows exactly what it is.
A USBLogger advertises with the KL- prefix and the app's scan recognises it as ZeroTrace hardware, but there is no dedicated USBLogger screen set. It connects and appears under the same HID-style fallback view described above. USBLogger's real interface is its own on-device Wi-Fi web page, not this app, see USBLogger Live Mode.
The advertised name is just a starting point. Rename any device in Settings so your hub reads the way you think about your kit, especially useful once you carry more than one of the same family.