Design choice: network-based event emitter
This device is designed as a minimal embedded component whose sole purpose is to emit RFID/NFC events over the network. Its behavior is intentionally limited, deterministic and predictable.
What the device does
The device performs a strictly defined set of operations:
- Read an RFID/NFC card or tag
- Extract the UID
- Associate the UID with a device identifier
- Transmit the event to a remote server over HTTPS
The device does not interpret the event and does not apply any business logic. Each read produces a single network event.
Data transmitted
For each event, the device transmits only the following parameters:
- uid: the RFID/NFC card or tag identifier
- device: the unique identifier of the device
No additional information is generated or inferred by the device.
Communication model
Events are transmitted using a standard HTTPS request to a configurable endpoint. The payload is encoded as application/x-www-form-urlencoded data.
uid=<UID>&device=<DEVICE_ID>
The receiving endpoint can be implemented in any programming language or framework capable of handling standard HTTP requests.
No local storage
The device does not store events locally and does not provide any mechanism for later manual data retrieval.
If the network is unavailable, events are not queued or buffered. The device operates exclusively in online mode.
Server-side timestamping
The device does not generate timestamps. Date and time are assigned by the backend when the event is received and stored.
- Single time reference across all devices
- No clock synchronization or drift management on the device
- Simpler firmware and reduced state
Why a minimal embedded architecture
The device does not perform complex computation. Its priority is reliability and predictable execution. A minimal embedded architecture enables:
- Deterministic behavior
- Simple and verifiable firmware
- Clear failure modes
- Fast recovery after power loss or reset
Network configuration
Network configuration is performed locally through a temporary access point exposed by the device when credentials are missing or invalid.
No external applications or proprietary configuration tools are required.
Scope reminder
This is a data collection component. It does not calculate payroll, manage shifts, or interpret labor regulations. It produces raw events that are intended to be consumed by existing backend systems.