
Sensor HAT
Eniemooo/Sensor-HAT
Open-hardware indoor air sensor (CO2, VOC/NOx, T/RH, light, sound): HAT for Raspberry Pi or standalone with Seeed XIAO + ESPHome. KiCad 10.

Bringing back our favorite pager alarms for those late night callouts
Sar pager is an open-source printed circuit board by KingCountySAR, from the KingCountySAR/iot-beepers repository on GitHub. It is a 2-layer board of 52 × 32 mm with 17 parts on 12 nets, routed with 73 tracks and 8 vias.
It is built around the XIAO ESP32C3, M2.5 and 1N4148W, with the AO3400A, OS102011MA1QN1 and TS-1187A-B-A-B among its other parts. Its parts include 5 resistors, 3 diodes, 2 switches, 1 capacitor and 1 IC. It belongs with the ESP32 and RISC-V boards of this library.
A dedicated, loud pager for SAR callouts. It's a cheap ESP32 box on the member's home Wi-Fi with a buzzer alarm, status and alert LEDs, a button and an arm/quiet switch. The central server forwards pages to it, tracks who received and acknowledged them, monitors device health, and pushes firmware updates.
callout source ──POST /api/ingest/page──┐
web UI "Send page" ─────────────────────┤
▼
┌───────────────────────────────────────┐
│ server (Node, Hono) │
│ • REST API + React web UI │ wss://host/mqtt
│ • embedded MQTT broker (aedes) ──────┼──────────────────────► pagers
│ • Postgres (Drizzle) │◄── status/ack/events ──
│ • firmware store + OTA rollout │
└───────────────────────────────────────┘| Dir | What |
|---|---|
server/ | Hono API, embedded MQTT broker, Drizzle/Postgres. Tests in server/test |
web/ | Vite + React admin and member UI |
firmware/ | ESP-IDF app (firmware/README.md) |
deploy/ | Its app on the KCSARA VM (the vm repo) |
hardware/ | Carrier board for the XIAO ESP32C3 (rev1) |
docs/ | protocol, hardware behaviour, metrics |
SAR-Pager-xxxx Wi-Fi. The setup page opens; if it doesn't, browse to http://192.168.4.1.Pairing happens on the server, never on the device. The pager only holds a random secret, so no member passwords live on it. Channel choices are made from any browser, and a replacement pager is just a re-pair.
dev/<id>/… topics.DATABASE_URL, the server runs Postgres-in-WASM in-process, so there's nothing to install locally. It runs the same SQL and migrations.Requires Node 22+.
npm install
cp server/.env.example server/.env.local # then put your email in SITE_ADMINS
npm run dev # UI :4100 (Vite, proxies /api and /mqtt to the server on :4102), metrics :4101
npm test # server integration tests (PGlite)
TEST_DATABASE_URL=postgres://postgres:pw@localhost:5432/postgres npm test # same, against real PostgresOpen http://localhost:4100 and sign in with your SITE_ADMINS email. In dev, DEV_LOGIN=true lets you type an email instead of going through Google (treated as managed by its address's domain, which must be one of ALLOWED_DOMAINS). Create a channel, then pair a device.
The UI is on :4100 and metrics on :4101 in production too. Dev ports and URLs come from server/dev.env; server/.env overrides them, and server/.env.local (gitignored, for your own settings) overrides both.
Without hardware, simulate a device with the helpers in server/test/harness.ts. They do the same register → MQTT → hello flow as the firmware.
Schema changes: edit server/src/db/schema.ts. Until the first release we don't keep migrations: delete server/drizzle/, run npm run db:generate -w server to regenerate 0000_init, and update existing databases by hand (or delete server/data/ in dev). Migrations run on startup.
Pages by email: mail to <channel slug>@beepers.kingcountysar.org pages that channel, through the KCSARA VM's
mail service (the vm repo's mail/README.md), which checks SPF and DKIM and POSTs it to
/api/ingest/email with INGEST_TOKEN. The subject is the page's title and the text its body, without a signature
after "-- ". An unknown channel bounces. To set it up: a route in the VM's config/mail.env, with INGEST_TOKEN and
who may send, and an MX record for beepers.kingcountysar.org pointing at the mail host:
ROUTE_BEEPERS=beepers.kingcountysar.org http://beepers:4100/api/ingest/email
ROUTE_BEEPERS_TOKEN=<INGEST_TOKEN>
ROUTE_BEEPERS_SENDERS=<who may page: addresses, or @domain>Send a page from another system:
curl -X POST https://host/api/ingest/page \
-H "Authorization: Bearer $INGEST_TOKEN" -H "Content-Type: application/json" \
-d '{"channel":"callout","title":"Callout","body":"Lost hiker near Mt Si trailhead."}'It runs on the KCSARA VM as the app beepers, at https://beepers.kingcountysar.org, deployed by the vm repo
(see "Apps" in its README). The VM's Caddy gives it its certificate and proxies the site, /mqtt included, and it uses
the VM's shared Postgres, cedar and Hydra over the kcsara network. deploy/compose.yaml runs the build on
node:22-alpine: npm run build makes one bundle, server/dist/beepers.mjs, which deploy/app.json sends with the
migrations (server/drizzle) and the web UI (web/dist). Firmware images are in the database.
The first time, from the vm repo:
node deploy.mjs database beepers: its database and user, in apps/beepers/config/database.env on the VM.node hydra.mjs create oauth2-client --name beepers --grant-type client_credentials --scope members.read --format json.apps/beepers/config/app.env from deploy/app.env.example: PUBLIC_URL, the
admins and domains, the Google client (below), the Hydra client, and INGEST_TOKEN.beepers.kingcountysar.org pointed at the VM (or a test name in HOSTS=, in apps/beepers/config/compose.env,
with PUBLIC_URL to match).Then, and for each deploy: npm run build here, and node deploy.mjs app ../beepers from the vm repo.
node deploy.mjs logs beepers shows its log. Pagers reconnect by themselves after a deploy.
The VM's Prometheus collects its metrics (the kcsara.metrics label; see docs/metrics.md), and its
health checks ask for /healthz.
Running the build in Docker on a dev machine, as on the VM: with docker compose up running in ../vm, make its
database once (docker compose exec postgres createdb -U postgres beepers there), then npm run build and
npm run docker -- up -d here (npm run docker -- down stops it). It's on http://localhost:4100, with the settings from
server/dev.env, .env and .env.local, then server/.env.docker.local for what differs in Docker. See
deploy/compose.local.yaml.
Sign-in is Google only, with Google's sign-in button (no redirects), as in rad-portal: anyone whose account is managed by one of the Workspace domains in ALLOWED_DOMAINS can sign in, and admins are the emails in SITE_ADMINS (changes take effect on restart). Which channels a member can join comes from their groups in the member database, mapped to channels on the Access page, plus any direct grants an admin adds there. A daily sync drops subscriptions people no longer qualify for. See docs/members.md. To create the OAuth client:
https://beepers.kingcountysar.org (PUBLIC_URL) and, for dev, http://localhost:4100. It needs no redirect URIs. Put its client ID in GOOGLE_CLIENT_ID; there's no secret to keep.Google only allows plain-HTTP origins on localhost, so in dev sign in at http://localhost:4100, not http://10.1.1.142:4100.
Firmware: run firmware/build.sh <board> and upload the dist/ image on the Firmware page. Members can then flash new pagers from the Flash page in Chrome or Edge, and updates roll out over Wi-Fi per board. See firmware/README.md.
POST /api/ingest/page: a Twilio number could call it./api/device/register.| Qty | Value | Footprint | References |
|---|---|---|---|
| 3 | 100R | R_0603_1608Metric | R2, R4, R5 |
| 3 | M2.5 | MountingHole_2.7mm_M2.5 | H1, H2, H3 |
| 1 | 100k | R_0603_1608Metric | R3 |
| 1 | 10R | R_1206_3216Metric | R1 |
| 1 | 10uF | C_0805_2012Metric | C1 |
| 1 | 12mm passive 5V | Buzzer_12x9.5RM7.6 | BZ1 |
| 1 | 1N4148W | D_SOD-123 | D1 |
| 1 | AO3400A | SOT-23 | Q1 |
| 1 | Green | LED_0805_2012Metric | LED2 |
| 1 | OS102011MA1QN1 | SW_Slide_SPDT_Angled_CK_OS102011MA1Q | SW2 |
| 1 | Red 10mm diffused | LED_D10.0mm | LED1 |
| 1 | TS-1187A-B-A-B | SW_Push_1P1T_XKB_TS-1187A | SW1 |
| 1 | XIAO_ESP32C3 | Seeed_XIAO_ESP32C3 | U1 |

Eniemooo/Sensor-HAT
Open-hardware indoor air sensor (CO2, VOC/NOx, T/RH, light, sound): HAT for Raspberry Pi or standalone with Seeed XIAO + ESPHome. KiCad 10.

NilsEngelbach/air-quality-pcb
Seventh iteration: ESP8266 → ESP32-C3 (native USB, no UART bridge), fixes from the v6 design review, right-angle switches with longer actuators, a STEMMA QT port for optional sensors, and charge-status sensing.

SebastianKristo/pult-forsterker
Ett kort (180 × 100 mm, 2 lag) som erstatter alle modulene, og som i tillegg har USB-delingsswitch, to AUX-innganger som digitaliseres (så alt kan mikses), «smart relé» for strømmen til forsterkerdelen…

semtronik/link-hardware
Open hardware for the Semtronik Link devices: ESP32-S3 base board, interface modules and enclosure. KiCad and Fusion sources, CERN-OHL-S v2.

silentaf/viswa_id1
It is the interface and safety-island board that sits on top of the Raspberry Pi 5 in the chest pod.

draarivpatel-ui/blare-clock
BlareClock: XIAO ESP32-C3 desk alarm clock with 2.25in ST7789 TFT, DS3231 RTC, 85dB piezo buzzer, KiCad 8 PCB, and OpenSCAD enclosure

PaulBichl/vibepcb-smu
VibePCB example: 4-quadrant SMU (+-30 V / +-1 A, USB-C PD, Ethernet) designed with an LLM

Sagaz0501/esp32-drone
PCB ESP32 quadcopter: KiCad hardware + Madgwick IMU firmware + WiFi web UI
It measures 52 × 32 mm and has 2 copper layers, 1.6 mm thick.
17 parts, built around the XIAO ESP32C3, M2.5, 1N4148W and AO3400A. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.
From the KingCountySAR/iot-beepers repository on GitHub, at the commit this page was made from: the board is hardware/rev1/kicad/sar-pager.kicad_pcb. PCBKit opens the board in the browser, with nothing to install.
Its repository states no licence, so its author keeps all rights: ask KingCountySAR before reusing the design.