Skip to content
AirPulse
iotEpic1000 XP

AirPulse

A multi room home environment monitor I built end to end: custom ESP8266 and ESP32 sensor nodes streaming to Supabase through a Cloudflare Worker proxy, with a live React dashboard. Hardware to cloud to frontend, all mine.

Role
Creator (hardware, firmware, cloud proxy, and dashboard)
Built in
Personal project
Team
Solo
Stack
6 techs

AirPulse is a multi room home environment monitor I built across the entire stack, from the sensor hardware up to the dashboard.

Custom ESP8266 and ESP32 nodes sit in different rooms and stream environmental readings. Instead of writing to the database directly, the nodes send data through a Cloudflare Worker proxy, which keeps credentials off the devices and gives a single controlled entry point to the backend. Readings land in Supabase, which handles storage and real time updates.

A live React dashboard, built with Vite, reads from Supabase and shows current and historical conditions per room. The result is a complete hardware to cloud to frontend pipeline that I designed and implemented myself.

What was hard → How I solved it

The problem

Streaming readings from multiple ESP8266 and ESP32 nodes without putting backend credentials on the devices

The fix

Routed all device traffic through a Cloudflare Worker proxy so credentials stay off the nodes

The problem

Collecting data from several rooms into one consistent live view

The fix

Used Supabase for storage and real time updates feeding the dashboard

The problem

Owning the full path from hardware to cloud to frontend as a solo build

The fix

Built a live React dashboard with Vite for current and historical conditions per room

What it changed

A working multi room environment monitor running on custom hardware

A clean hardware to cloud to frontend architecture, all self built

Credentials kept off devices via a single controlled Worker entry point

Built with

Frontend
React
Other
ESP32ESP8266SupabaseCloudflare WorkersVite