IoT Geyser Energy Monitor with App Dashboard

Electric geysers heat water brilliantly and waste energy quietly. The element cycles on a thermostat, and a geyser left switched on reheats the tank all day to cover standby losses — energy that buys nobody a hot bath. Because the consumption is invisible, families cannot answer the simplest questions: how many units did the geyser use today, what does one bath cost, would a timer actually save money? This project makes it visible without touching a single wire: a split-core CT clamp around the geyser's supply cable measures current non-invasively, DS18B20 sensors watch inlet and outlet water temperature, and an ESP32 detects heating sessions from the current signature, integrates power over time into kWh, and multiplies by the user's tariff for the rupee figure. A mobile-style app dashboard presents live power, today's energy and cost, a session log with per-session units, weekly bar charts and an estimated standby-loss share. The student gets both the sensing hardware and a genuinely working app demo.

1. A split-core CT clamp is clipped around the geyser's supply cable and DS18B20 probes are strapped at the inlet and outlet — no mains wiring is disturbed.
2. The ESP32 samples current, computes RMS power (using the configured mains voltage), and watches the current signature to mark session start/end.
3. Energy per session is integrated (power × time) into kWh and converted to rupees at the configured tariff; standby reheat cycles are tagged separately.
4. Every 30 seconds the node publishes live power, temperatures and session events over Wi-Fi (MQTT/HTTP) to the app backend.
5. The app dashboard renders the live power dial, today's units and cost, the session log, weekly consumption bars and the standby-loss share.
6. The student commissions the unit with the included procedure: verify the power reading against the geyser's rating plate, run a known session, and document the measured energy in the report.

Tech stack:

• ESP32 (sensing + Wi-Fi telemetry)
• SCT-013 split-core current transformer
• DS18B20 waterproof temperature sensors
• MQTT/HTTP telemetry
• Mobile-style app dashboard (HTML/CSS/JS demo included)
• Arduino IDE (C/C++ firmware)
• 5 V USB power for the node

• [Non-invasive energy metering] A split-core CT clamp measures geyser current without cutting or stripping mains wiring — safe to fit and honest to demonstrate.
• [Session-aware analytics] Firmware detects heating sessions from the current signature and logs each with duration, energy and cost — not just a raw power number.
• [Rupee-cost conversion] Energy is converted to cost at a user-configurable tariff, so "3.2 units" becomes the number families actually care about.
• [Mobile-style app dashboard] A phone-friendly app UI shows live power, today's units/cost, session history and weekly charts — the included demo runs on realistic simulated data.
• [Standby-loss estimate] The app separates reheating cycles (thermostat top-ups with no water drawn) from real usage sessions, quantifying the waste of leaving the geyser on.
• [Temperature context] Inlet and outlet sensors show how hard the element works per session, supporting the efficiency discussion in the report.
• [Tariff and tank configurability] Tank capacity and electricity tariff are settings, so the numbers stay truthful for the student's own home.

• Assembled sensor node (ESP32 + CT interface + temperature probes)
• Split-core CT clamp and waterproof DS18B20 probes
• Firmware source with session detection and energy integration
• Working single-file app dashboard demo with simulated telemetry
• Installation and commissioning guide (non-invasive fitting)
• Project report PDF (theory, metering, analytics, app, results)
• PPT presentation and viva Q&A document

• Energy is computed from current × an assumed mains voltage, not measured voltage — the report states this approximation and its error bounds honestly.
• Power factor is assumed near unity for a resistive element; the figure is approximate, not revenue-grade metering.
• The app demo ships with simulated telemetry; live data appears only after the hardware node is installed and connected.
• Standby-loss tagging is heuristic (reheat cycles with no draw inferred from timing), not a direct measurement of hot-water usage.
• Wi-Fi coverage is required at the geyser location.
• One node monitors one geyser; tariff changes must be updated manually in settings.