Observe events without controlling the entrance
The documented agent claims configured GPIO lines as inputs and rejects output or unlock configuration. It monitors the selected sensor’s events rather than actuating an entrance. OPTEX’s Accurance OV-102 is a people-tailgating detector for appropriate indoor entrance layouts; sensor placement and the connection to existing access hardware must be confirmed against the selected equipment and site conditions.
Local recording and signed reporting
The software design uses a durable local queue to retain events during a communications outage and sends signed batches with device identity and sequence information. Heartbeats and a watchdog support equipment-health monitoring. Buffering reduces dependence on continuous connectivity, but it does not provide unlimited storage or guarantee immediate reporting during an outage.
Separate tenant data and device ingestion
The source includes a multi-tenant database design with row-level security and an authenticated device-ingest path. Published test evidence covers software behaviour and tenant isolation in the documented test environment. Those results do not prove that a particular live cloud project has been deployed or configured correctly; deployment and access checks must be repeated for the operational environment.
Alert delivery and operator response
The design can route accepted events to configured notification services and identify a device that has stopped reporting. The documented status does not verify actual email or SMS delivery without configured service accounts. Recipients, escalation rules and tests must be agreed before presenting the monitoring service as operational. An alert requires the nominated operator’s response process; it is not proof that unauthorised entry was prevented.
Commission the physical sensor and complete the handover
The installed OPTEX model, outputs, electrical isolation, mounting, coverage and event interpretation must be checked on site. Confirm safe work and egress arrangements with the building’s responsible parties. Bench and field tests should establish real event capture, outage recovery, clock handling, accepted ingestion and notification delivery. The frontend, cloud configuration and maintenance scope are separate deployment deliverables.
Retain the distinction between design and operational proof
The source README documents automated agent, ingest and database tests while identifying live equipment and deployment items that remain unverified. This case study presents that development scope accurately. RJL’s body corporate and access-integration services can assess how supported monitoring fits a building’s existing infrastructure.