Files

T

julian 1b55e2034d Dingtian relay driver — resolves the ticket-first entry blocker

The Dingtian board's inputs are independent of its relays (configurable), so a
button on an input can report to the host WITHOUT auto-firing a relay — solving
the access-controller-button-flow blocker the UHPPOTE/ZKTeco couldn't.

packages/devices:
- access-dingtian.ts: `dingtian` access driver implementing AccessControlDevice
  (relay pulse/latch via UDP string protocol :60001), InputDevice (read inputs +
  poll-based press/release events, active-LOW), and the new PreconditionDevice.
- PreconditionDevice capability on the interface: a device can report config it
  requires for parking and optionally fix it. Dingtian checks input_link_relay
  via the HTTP config API and can disable it.
- httpPort config field — the web/config API port is separate from UDP control
  (this unit uses 8080, not the default 80).
- Register dingtian; export driver objects from the package.

Verified on real hardware (DT-R004 @ 10.0.10.172): status read, relay pulse,
input events; disabled input_link_relay via the driver, then confirmed pressing
inputs fires NO relay (0000) — host-in-the-loop entry works.

Config-write gotcha recorded: config_set.cgi requires "command":"setconfig"
injected after "status" (GET omits it) or the POST silently no-ops.

apps/server/scripts/dingtian-test.mjs: status / watch / pulse hardware test.
wiki: dingtian-relay verified; button-flow marked RESOLVED; index + log.

2026-06-14 14:15:00 +02:00

4.7 KiB

Raw Blame History

type, tags, updated

type

Index

Content catalog for the wiki. Start at overview. Maintained on every ingest. Counts: 1 source · 14 entities · 10 concepts · 2 decision records.

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 — current access controller; cheap, tamper-evident, open-UDP, fixed firmware.
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 — C3/inBio controller; aux-input path may enable host-in-the-loop (driver TBD).
dingtian-relay — relay+input board; inputs decoupled from relays → solves the button blocker (driver TBD).
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-discovery — optional driver capability to scan the LAN (UHPPOTE UDP broadcast).
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.

4.7 KiB Raw Blame History