Files
parking_solution/wiki/index.md
T
julian b2a0471b08 Rongta 80mm printer: driver, role-based failover, live status monitoring
Add the rongta PrinterDevice driver (ESC/POS over raw TCP 9100) and the
device-agnostic pieces around it:

- Roles + failover: each printer declares a role (entry-dispenser/booth-
  receipt) and failoverRank; printer-routing.ts picks the best healthy printer
  and falls back outside->booth for entry tickets (never the reverse).
- Live status: MonitorableDevice.readStatus()/PrinterStatus capability. The
  Rongta driver scrapes the device's own /prn_stat.htm (Cover/Cutter/Paper
  End/Near End/Off-Line) rather than hand-decoding DLE EOT, whose reply bytes
  on this clone don't match the canonical ESC/POS bit layout (verified on
  hardware) -- avoids a false-healthy. Maps to ready/degraded/offline, fail
  safe on an unreachable or unexpected page.
- Server PrinterMonitor polls enabled printers (PRINTER_POLL_MS, default 5s),
  caches latest, emits "printer-status" on change. Exposed via
  GET /api/printers/status and an SSE stream for the booth UI.

Verified against 10.0.10.6: ready when healthy, offline when unreachable
(no throw), bus emits on change and suppresses unchanged reads.

Wiki: new rongta-printer entity, printer-roles-failover and
printer-status-monitoring concepts; BOM/index/log updated.
2026-06-14 20:26:45 +02:00

5.2 KiB

type, tags, updated
type tags updated
overview
parking
index
2026-06-14

Index

Content catalog for the wiki. Start at overview. Maintained on every ingest. Counts: 1 source · 15 entities · 12 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

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).
  • rongta-printer — ✅ CHOSEN 80mm thermal printer; ESC/POS over raw TCP 9100; driver written, one unit reachable at 10.0.10.6.
  • 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

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.
  • printer-roles-failover — ≥2 printers per lane by role; entry ticket falls back outside→booth.
  • printer-status-monitoring — live poll of paper/cover/cutter/offline via the device's status page; SSE to the booth UI.
  • 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

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.