julian
23919164ee
The device pushes button events to the backend via its Input Link URL feature;
the backend decides. No polling — the chosen entry architecture.
packages/devices:
- dingtian driver: configureInputPush() writes the device's input_link_url
config (per-input server/port/path, en=1, active-LOW, plain HTTP) so each
input HTTP-GETs the backend on press/release. Extracted #readConfig/#writeConfig
(with the required command:setconfig injection + post-write reset tolerance).
apps/server:
- routes/devices.ts: public GET/POST
/api/devices/dingtian/:deviceId/input/:n/{on,off} — translates a device push
into an internal device event. Not behind cookie/CSRF (machine call from the
device); trust comes from the signed event log, not this request.
- device-events.ts: internal EventEmitter bus so the entry flow subscribes to
input events without coupling to HTTP. Wired into the server.
Verified on hardware: configured the device, then real presses on all 4 inputs
pushed to the backend (input N on+off, source = device IP). No polling.
wiki: device-input-flow concept (path + trust model for the flat/no-VLAN
network); dingtian-relay updated; index + log.
4.8 KiB
4.8 KiB
type, tags, updated
| type | tags | updated | ||
|---|---|---|---|---|
| overview |
|
2026-06-14 |
Index
Content catalog for the wiki. Start at overview. Maintained on every ingest. Counts: 1 source · 14 entities · 10 concepts · 2 decision records.
Overview & navigation
- overview — the top-level synthesis and entry point.
- index — this catalog.
log.md— chronological record of ingests/queries/lints.
Sources
- parking-system-architecture — design notes: stack, threat model, devices, UHPPOTE, ESP32, readers, BOM, open decisions.
Entities — technology stack
- technology-stack — the full stack table; all MIT/Apache/BSD, chosen to avoid lock-in.
- fastify — Node backend; hosts device-driver plugins + auth; serves the SPA.
- sqlite — local single-writer DB (WAL); limits & why it fits.
- drizzle-orm — ORM; schemas port to PostgreSQL for remote sync.
- turborepo — monorepo tool.
- react-vite-spa — React/Vite frontend served by Fastify.
- local-jwt-auth — fully local auth (JWT + bcrypt + role guard); forced by offline-first.
Entities — rejected alternatives
- payload-cms — strong, but rejected over BSL license shift (the rug-pull cautionary case).
- refine — dropped for plain React; UI too simple to justify a framework.
- logto-zitadel-oidc — OIDC providers ruled out by offline-first.
Entities — hardware & devices
- uhppote-controller — ❌ rejected/historical; firmware auto-open blocker drove the switch to Dingtian.
- esp32-custom-controller — prevention-grade upgrade; device-level auth.
- atecc608 — secure element; non-extractable signing key (host events + controller auth).
- wiegand — reader standard feeding the controller directly (autonomous permit-holder path).
- lpr-camera — edge-AI plate recognition; host-side casual-identity source.
- zkteco-controller — ❌ rejected/historical; aux-input path was a contender, not pursued.
- dingtian-relay — ✅ CHOSEN access controller; decoupled inputs solve the button blocker (driver verified on hardware).
- bom — reference bill of materials (barrier, loops, controller, readers, payment, host, network).
Concepts — foundational forces
- offline-first — no network dependency in core operation; what it forces (and doesn't).
- threat-model — the operator-at-the-booth reframing; why encryption defends the wrong threat.
Concepts — integrity & anti-fraud
- append-only-event-chain — append-only + hash chain + ATECC608 signing = unforgeable log.
- reconciliation — the real anti-fraud control; what remote sync actually is.
- disk-os-hardening — LUKS/GRUB/Secure Boot; worthwhile but not the main event.
Concepts — device architecture & safety
- device-adapter-pattern — business logic talks to interfaces; swap hardware → new adapter.
- device-registry — catalog of selectable drivers per category (admin-configurable).
- first-run-setup — admin assigns devices per lane from the catalog at install.
- device-input-flow — button → device push → backend decides → relay; backend is source of truth.
- device-discovery — optional driver capability to scan the LAN (no current driver uses it; UHPPOTE was the example).
- barrier-not-a-door — never timed-close a barrier; safety lives in barrier firmware.
- trust-boundary — the core fork: network vs. device; auditable vs. unforgeable.
- fail-state-safety — entry fails closed, exit fails open; manual override; watchdog.
Concepts — access control
- uhppote-udp-protocol — open UDP weakness + the unauthenticated commands that undermine the log.
- network-isolation — mandatory VLAN isolation; the network as security boundary.
- event-log-ingestion — host-side index tracking that makes the UHPPOTE log trustworthy.
- challenge-response-auth — asymmetric nonce scheme for the ESP32 (auth + anti-replay).
- entry-exit-readers — two populations, two integration paths; both can share a relay.
- uhppote-vs-esp32 — comparison: detection vs. prevention.
Dev environment (reference)
- local-dev-workflow — running the stack locally; setup, the dev-hang gotchas, seed:admin.
- wsl-dev-networking — WSL2 NAT blocks device broadcast; use mirrored mode + the gotchas after.
Decisions
- standing-decisions — settled decisions (stack, platform, integrity, access control, readers).
- open-questions — 7 open items (6 procurement + JWT key choice); ESP32 device auth deferred.
- access-controller-button-flow — ✅ RESOLVED: Dingtian decoupled inputs enable ticket-first entry (was a UHPPOTE/ZKTeco blocker).
- autonomous-direction — roadmap: toward fully unmanned (no booth); reshapes threat model + fail-state.
- dingtian-vs-mqtt — transport choice: direct HTTP/UDP now, MQTT parked until multi-lane scale.