Build log · Software & apps

WiFi Monitor

Software & appsdone3 versionsESP32WiFiScannerC

reflection not written yet · every fact below is generated from this project’s own spec and files

What it is

ESP32 WiFi scanner - signal graphs, device tracking.

Version history

Straight from the project’s own card data — what each version added.

V1

Serial only.

V2

MAC tracking.

V3

Full dashboard.

By the numbers

Measured from the real working folder ~/Documents/projects/network-tools/wifi-monitor — not a claim, a count.

137
files
105
lines of code
1
file types used
2026-08-04
oldest file
2026-08-04
last touched

Mostly: C++ ×1

What broke, and what I’d change

Not written yet. This is the part only I can write — what actually went wrong, and what I’d do differently. It lives in builds/reflections/wifi-monitor.md (see _TEMPLATE.md); as soon as that file has words in it, this section fills in on the next build.

Everything else on this page — the spec, the version history, the file counts — is generated from the project’s own build notes and files, so nothing here is guesswork.

Build spec

The project’s own build notes, rendered. Open the raw .md ↗

Show the spec

WiFi Monitor

Category: Software & Apps · Status: Done

ESP32 WiFi scanner - signal graphs, device tracking.

Stack / Tools: ESP32, WiFi, Scanner, C

Build path:

  • V1 — Serial only.
  • V2 — MAC tracking.
  • V3 — Full dashboard.

Location: ~/projects/wifi-monitor/

Full spec already in this prompt file (ESP32-C3 AP-mode WiFi scanner with web dashboard).

Where it lives

  • Source folder: ~/Documents/projects/network-tools/wifi-monitor
  • Artefacts on the site: 2 files · 105 lines of text · 5 KB

Stack

  • .ini ×1 · C++ ×1 · PlatformIO

What's in the code

  • src/main.cpp — 105 lines (C++)

_Spec generated from the project's own files on 2026-10-22 (gen-project-specs.py). Everything above was read from the listed files — file counts, line counts, names, routes, headings and script comments. No description was invented._