Repository navigation
Scheduled scans
Luke Switzer edited this page Oct 26, 2026
·
1 revision
The node can run a scan at a set time, once or every day, even with the web page closed. It holds up to eight schedules.
- Web UI: set up a scan on the Scan tab, then Schedule this scan.
-
Over mesh:
@AH01 SCHED_ADD:2026-10-07T21:00|86400|/scan|mode=2&secs=600runs a 10-minute target scan every day at 21:00.
| Value | Meaning |
|---|---|
2026-10-07T21:00 |
First start, in the node's local time |
86400 |
Seconds between runs. 0 runs once. Minimum 600 |
/scan |
/scan target scan, /sniffer device discovery, /drone drone detection |
mode=2&secs=600 |
Radio (0 Wi-Fi, 1 Bluetooth, 2 both) and run length |
@AH01 SCHED_LIST lists the schedule, and @AH01 SCHED_DEL:1 deletes entry 1.
A schedule runs on the node's local time. A Headless node runs schedules once its clock is set, from GPS or over the mesh. Without a clock, a scheduled scan does not fire. See First setup.
Confirm the node's clock is set and the time is in the future. The minimum interval for a repeating schedule is 600 seconds. A scan already running at the scheduled time is not interrupted unless you set it to.
Start
Nodes
Find devices
- Target scan
- Device discovery
- Device classifier
- Probe requests
- Randomized MAC tracer
- Drone Remote ID
- Triangulation
Watch an area
Detect attacks
Capture and respond
How-to
Reference
Build