check.espkvm.io

Counts the ESP-KVM devices in use. A Cloudflare Worker with a D1 database, sized for the free plan.

With Offer firmware updates on and the project's own manifest address, the console reports POST /v1/seen?id=&board=&ver=&rev= once a day after a working update check (src/state/seen.ts in the console). The id is the device's random installId (NVS, not taken from the hardware, a settings reset makes a new one). rev is the chip revision (3.1), sent by consoles from 0.76.0 on. A value that does not parse is dropped, the device still counts. One row per device per month; no IP address is stored. The device itself never sends anything.

GET /v1/stats[?month=2026-10] with Authorization: Bearer <STATS_TOKEN> returns devices per month (and how many of them are new), boards, versions and revisions for one month (the exact one where it was sent, else 1.x or 3.x by the board's image), growth (new devices by the day each was first seen, and the running total) and daily: a snapshot the cron trigger stores each day just before midnight UTC, of the devices seen in the 30 days up to that day, in all, by board, by version and by revision.

Deploy

npx wrangler login
npx wrangler d1 create espkvm-check      # put the id into wrangler.toml
npx wrangler d1 execute espkvm-check --remote --file schema.sql   # a new database
npx wrangler d1 execute espkvm-check --remote --file migrate-rev.sql   # an existing one, before the deploy that needs it
npx wrangler secret put STATS_TOKEN
npx wrangler deploy                      # also creates the check.espkvm.io custom domain and the cron trigger

Test

npm test runs it against node's own SQLite in place of D1 (Node 22.5 or later).

License

Apache-2.0, see LICENSE.