Built to order

IoT Hostel Washing Machine Usage Monitor

Every hostel has the same ritual: students trek to the laundry room, find all machines running, and trek back — repeatedly, all evening. This project builds an IoT washing machine usage monitor for shared laundry rooms: compact sensor nodes on each machine detect the wash cycle from vibration and current signatures, and a cloud dashboard shows a live availability board — which machines are FREE, WASHING, or DONE — plus per-machine usage hours, cycle counts and alerts. Students check the board on their phones instead of walking over; wardens get real usage data for maintenance scheduling and

IoT Hostel Washing Machine Usage Monitor — project thumbnail preview
More project photos (5)

The problem

Shared washing machines in hostels and apartment complexes are a classic commons problem: a handful of machines serve hundreds of residents, there is no booking system, and the only way to know if one is free is to walk to the laundry room. Machines run overloaded, nobody knows which one is due for service, and "someone left their clothes in for three hours" is a daily complaint. This project instruments each machine with a compact sensor node that recognizes the wash cycle from its vibration and current signature — fill, agitate, spin phases are mechanically distinct — and reports state changes over Wi-Fi. The dashboard presents a live availability board (FREE / WASHING / CYCLE DONE), per-machine cycle counts and run-hours, a done-alert feed, and flags for abnormal behavior like a machine vibrating far beyond its normal band or a cycle running far too long. The student delivers the sensing hardware and a genuinely working dashboard demo that mirrors the real deployment.

How it works

  1. A sensor node is mounted on each washing machine's body (vibration sensor) with a CT clamp on its supply cable — no panel is opened.
  2. Firmware continuously watches vibration energy and current draw, classifying the machine into IDLE, FILL, WASH, SPIN or DONE with a phase state machine and debounce timing.
  3. State changes are published immediately over Wi-Fi (MQTT/HTTP); a periodic heartbeat confirms each node is alive.
  4. The backend accumulates cycle counts, run-hours and phase durations per machine; abnormal vibration or over-long cycles raise maintenance flags.
  5. The dashboard renders the live availability board, per-machine usage stats, the done-alert feed and the maintenance flag list.
  6. The student commissions the laundry room with the included procedure: run one supervised cycle per machine to learn its signature, set the phase thresholds, and validate the board against observed cycles.

Tech stack:

  • ESP32 sensor nodes (one per machine)
  • Vibration sensor + SCT-013 CT clamp per node
  • Wi-Fi telemetry (MQTT/HTTP)
  • Web dashboard (HTML/CSS/JS demo included)
  • Phase state-machine firmware
  • Arduino IDE (C/C++ firmware)
  • 5 V USB power per node
Parameter Value
Sensing Vibration + current signature per machine (design)
States IDLE, FILL, WASH, SPIN, DONE (design)
Reporting State change immediate + heartbeat
Metrics Cycle counts, run-hours, phase durations
Alerts Cycle-done, abnormal vibration, over-long cycle
Dashboard Availability board, usage stats, alert feed
Installation External mount, no machine opened

Project features

  • [Live availability board] Each machine shows FREE, WASHING or CYCLE DONE in real time — residents check their phones instead of walking to the laundry room.
  • [Cycle-phase state machine] Firmware recognizes fill, wash, rinse and spin phases from the vibration/current signature, so the board reflects reality, not a timer guess.
  • [Cycle-done alerts] The moment a machine finishes, the dashboard flags it — cutting the "forgotten clothes" idle time that blocks the next user.
  • [Per-machine usage logs] Cycle counts and run-hours per machine give wardens the data behind maintenance scheduling and replacement decisions.
  • [Abnormal-behavior flags] Excessive vibration or abnormally long cycles raise maintenance alerts with timestamps — the early warning a warden never had.
  • [Non-invasive sensing] Nodes mount externally and sense vibration plus supply current via CT clamp — no machine is opened and no warranty is voided.
  • [Working demo dashboard] A single-file web dashboard with realistic simulated laundry telemetry is included for presentation and viva.

What is included

  • Sensor node design (one node per machine in the demo set)
  • Phase state-machine firmware with debounce logic
  • Working single-file dashboard demo with simulated laundry telemetry
  • Mounting and signature-learning commissioning guide
  • Project report PDF (theory, sensing, state machine, dashboard, results)
  • PPT presentation and viva Q&A document

Limitations & prerequisites

  • Phase recognition is signature-based and approximate; heavily unbalanced loads or a machine with a failing damper produce unusual signatures the state machine may misread — stated honestly.
  • Thresholds must be learned per machine model; one laundry room with mixed models needs per-machine commissioning.
  • The dashboard demo ships with simulated telemetry; live data appears only after nodes are mounted and connected.
  • Wi-Fi must cover the laundry room; the node buffers briefly but is not a long-term offline logger.
  • It monitors machine state, not laundry ownership — it cannot tell whose clothes are inside.
  • Cycle-done alerts appear on the dashboard; push notifications to phones need the notification extension listed as future scope.

Frequently Asked Questions

How does it know the wash phase?

Fill, wash, rinse and spin are mechanically distinct: fill is quiet with inlet-valve current, wash is rhythmic agitation, spin is sustained high vibration. The firmware's state machine watches vibration energy plus current to track phases.

Do you have to open the washing machine?

No — nodes mount externally on the body and the CT clamp clips around the supply cable. Nothing is opened, no warranty is voided; the guide documents the fitting.

What does the dashboard show?

A live availability board (FREE / WASHING / CYCLE DONE per machine), per-machine cycle counts and run-hours, a done-alert feed, and maintenance flags for abnormal vibration or over-long cycles.

Does the demo dashboard need hardware?

The included single-file dashboard runs on realistic simulated laundry telemetry for presentation and viva; real nodes replace the simulator with live data through the same interface.

Can students book a machine from the dashboard?

As specified the board is informational; a booking/queue system is documented as future scope in the report.

Is this project suitable for a final-year project?

Yes — for IoT & Embedded, Electronics and Computer / IT programs. It combines non-invasive sensing, embedded state machines, telemetry and a genuinely useful dashboard. Suitable for B.E./B.Tech final-year projects in IoT & Embedded, Electronics / E&TC and Computer / IT.

Components & software requirements
  • ESP32 sensor nodes (one per machine)
  • Vibration sensor + SCT-013 CT clamp per node
  • Wi-Fi telemetry (MQTT/HTTP)
  • Web dashboard (HTML/CSS/JS demo included)
  • Phase state-machine firmware
  • Arduino IDE (C/C++ firmware)
  • 5 V USB power per node
Delivery information

Built-to-order project. Delivery timeline is shared after order confirmation based on current queue.

Support terms

Complete documentation, setup guide, and viva preparation included. Support for setup and explanation provided.

Download abstract (PDF)

Related guides

All guides
Blueprint-style technical illustration of an ESP32 development board at the centre, with sensor nodes, data-flow arrows and a circuit-brain motif representing an AI agent reasoning and sending decisions back.Engineering students building IoT or embedded final-year projects who want to add local AI agent behaviour with ESP32, MQTT and a small language model.

AI Agents on ESP32: Agentic IoT Final-Year Projects

An agentic IoT system observes, reasons, acts, remembers and explains. On ESP32 that means a split architecture: the chip senses and acts while a small local model (Ollama on your laptop) reasons over MQTT — a full LLM needs gigabytes of RAM the chip doesn't have. This guide covers three working patterns (host-reasoned agent, on-device tinyML on ESP32-S3, and a hybrid of both), plus Wi-Fi CSI presence sensing, parts and budget for India, code shapes, and honest limits to state in your report.

Read guide
Technical illustration of three electronic control units linked by a twisted-pair CAN bus cable carrying signal pulses between them.Electronics, E&TC, IoT and robotics students who keep hearing “CAN bus” in EV, automotive and industrial project ideas and want to understand it properly before wiring anything

CAN Bus Basics for Students: How ECUs Communicate

CAN bus is the shared network that lets dozens of controllers in a car, EV or robot communicate over two wires. This guide explains message IDs, arbitration, the physical layer, frame structure, error handling and CAN FD, then walks through building a working two-node bench network with an ESP32 and a transceiver.

Read guide
Illustration of a quadcopter drone build showing labeled parts including frame, motors, propellers, ESCs, flight controller, and battery.B.E./B.Tech Electronics, Mechanical, and Computer Science students planning to build a quadcopter drone who need to select compatible parts without wasting money on mismatched

Drone Build: Parts Selection Guide

Picking drone parts that actually work together is a sizing problem, not a shopping problem. This guide walks the compatibility chain — frame to props to motors to ESCs to battery — with the thrust math, firmware choices, LiPo safety, and the bench-test order that prevents disasters.

Read guide
Get a quotation