IoT Power Reel Wall

An NFC-locked wall that lends power reels to students.

Role
Backend, dashboard and embedded developer · 7-person team
Period
Feb 2024 – Jun 2024
Stack
Nuxt · Prisma · ESP32 · C++/Arduino · NFC (PN532) · Docker · Raspberry Pi · GitLab CI
Runs on
Local only, no cloud
Code

HvA team project; the repository isn't public. Happy to walk through it in an interview.

At a glance

Problem
Power reels in HvA labs were often not returned on time, so the lab needed to track who borrows them.
My contribution
Built the Nuxt check-in/check-out REST API with atomic Prisma transactions and the usage dashboard, containerised the services with Docker, and worked on the ESP32 NFC firmware.
Outcome
A working hardware and software prototype, used in HvA labs: every check-out and return goes through the API and shows in one dashboard.

Context

A self-service lending wall for the power reels of HBO-ICT at the Hogeschool van Amsterdam, built by a seven-person team as an academic client project. Reels were often not returned on time, so the goal was to track who borrows them. The wall replaced the manual sign-out: students scan their HvA pass, and a valid scan releases the lock on a slot.

What I built

My part

  • Built the check-in/check-out REST API in Nuxt, using Prisma transactions so each check-in and check-out is applied atomically, and refusing a second check-out while a student still has a reel.
  • Built the usage dashboard, with separate overviews for locks, checkouts, users, and feedback.
  • Worked on the NFC authentication flow in the ESP32 firmware: a scanned pass triggers a backend lookup that validates the student and releases the solenoid lock.
  • Containerised the services with Docker and deployed them to a Raspberry Pi through a GitLab CI pipeline.

Architecture

The wall's ESP32 firmware (C++/Arduino) reads the pass with a PN532 NFC reader, drives the solenoid lock, and confirms pickup and return with an ultrasonic sensor. It talks to the Nuxt API, which runs with the dashboard in Docker on a Raspberry Pi in the lab.

Decisions and trade-offs

  1. Nuxt server routes for the APIover a separate Express backendNuxt's server directory serves API routes without an external server, so the API and the dashboard live in one codebase and one language. It also builds on Vue, which HvA teaches, which made it easier for a seven-person team to iterate on it together.
  2. A Prisma transaction around every check-out and check-inover separate writes per tableA check-out both opens a lending record and marks the lock's reel as taken. Running both writes in one transaction means they succeed or fail together, so a reel's status and the lending log can never disagree.
  3. Chart.js for the usage graphover D3.jsThe admin only needed standard charts, such as which days reels go out most, and Chart.js was quicker to set up.

Results

  • Delivered a working hardware and software prototype, used in HvA labs.
  • Replaced manual sign-out with an authenticated, auditable lending flow: every check-out and return goes through the API.

What I learned

This was my first project where software had to agree with hardware. A pass scan, a lock and a database row all have to tell the same story, and a lending log that disagrees with the wall is worse than none, which is why every check-out runs in one transaction. Working with six others on one codebase also taught me to keep the API between firmware and dashboard small and explicit, so both sides could move in parallel.