julian
7438c0bdc2
Researched Node options for the UHPPOTE controller and chose the official
`uhppoted` npm package (MIT, actively maintained, single trivial dep). Its API
covers the full design: openDoor, getStatus, the event-log set (getEvent,
getEventIndex, setEventIndex, recordSpecialEvents), and setListener/listen.
Rejected alternatives: raw-dgram DIY, node-red-contrib-uhppoted, Go sidecar.
- packages/devices: add uhppoted@0.9.0; new `uhppote` access driver implementing
AccessControlDevice (pulseOpen -> openDoor intent-only; healthCheck/getDoorStatus
-> getStatus). Registered in the catalog alongside zkteco/esp32-relay.
- Local ambient types (uhppoted ships none); CJS interop via default-import +
destructure under NodeNext.
- Config fields: controller serial (required), optional host/protocol (udp|tcp),
doors, timeout.
Security/safety unchanged: unauthenticated UDP -> isolated VLAN assumed; relay
is intent-only ("a barrier is not a door").
wiki: record the library choice on uhppote-controller + log entry.
Verified: builds; `uhppote` shows in the catalog with correct fields;
instantiates and degrades to "offline" gracefully without hardware (on-VLAN
test pending).
44 lines
2.4 KiB
Markdown
44 lines
2.4 KiB
Markdown
---
|
|
type: entity
|
|
tags: [parking, hardware, access-control, current-choice]
|
|
sources: [parking-system-architecture]
|
|
updated: 2026-06-15
|
|
---
|
|
|
|
# UHPPOTE Controller (current choice)
|
|
|
|
The starting access-control hardware: a **UHPPOTE Wiegand 26/34 network controller (4-door)** —
|
|
a cheap reader-plus-relay frontend, acceptable **provided you understand its limits**. The plan
|
|
is UHPPOTE now → ZKTeco later (see [[bom]]). (See [[parking-system-architecture]] §6.)
|
|
|
|
> **Implementation:** integrated via the official **`uhppoted`** npm package (MIT, by the
|
|
> `uhppoted` org — `github.com/uhppoted/uhppoted-lib-nodejs`), added to `@parking/devices` as the
|
|
> `uhppote` access driver ([[device-registry]]). It exposes exactly the protocol commands this
|
|
> design needs: `openDoor`, `getStatus`, and the event-log set (`getEvent`, `getEventIndex`,
|
|
> `setEventIndex`, `recordSpecialEvents`) plus `setListener`/`listen` for auto-push — see
|
|
> [[event-log-ingestion]]. Transport defaults to **UDP** (broadcast `…:60000`), with optional
|
|
> per-call TCP on newer firmware. Note: the lib pulls one trivial extra dep (the npm `os`
|
|
> shim) and tends to use UDP broadcast, which needs socket broadcast permission on the host.
|
|
|
|
## What it is
|
|
|
|
- Combines reader input ([[wiegand]]) and door relays, with an onboard card list enabling
|
|
**autonomous offline decisions** for Wiegand lanes.
|
|
- Stores an **indexed event log** (see [[event-log-ingestion]]): `get-events` returns the
|
|
stored range + current index; each record has event ID, timestamp, card number, door,
|
|
access-granted flag, reason code. **At the record level it's effectively append-only** — no
|
|
command edits/deletes an individual event.
|
|
|
|
## The catch
|
|
|
|
It speaks the [[uhppote-udp-protocol]]: **UDP port 60000, no auth, no encryption**. Anyone on
|
|
the LAN can open any door — and several unauthenticated commands can blind/reset/skew the log.
|
|
So the device is **tamper-evident, not tamper-proof**, and only trustworthy behind
|
|
[[network-isolation]] (mandatory). **Firmware cannot be customized** — the open-source
|
|
`uhppoted` ecosystem is protocol reverse-engineering only; the controller accepts only the
|
|
manufacturer's official firmware images.
|
|
|
|
Make the log trustworthy via [[event-log-ingestion]] (host-side index tracking) landing into
|
|
the [[append-only-event-chain]]. For prevention-grade authentication, see the
|
|
[[esp32-custom-controller]]. The choice between them is the [[trust-boundary]] decision.
|