From site drawings to a smart home dashboard
If you just watched the short demo on my channel, you already know the vibe: a small ESP32 board, a few sensors, a phone holder, and a screen that suddenly feels like a control room for the whole house. No sci-fi lab. No imported “smart villa” package. Just a civil engineer fiddling with wires after site work, trying to make daily life a little more readable.
This post is the longer version of that video—what I actually built, why it matters when you are building or managing a house in Nepal, and how you can think about home automation without getting lost in marketing jargon. If you build from abroad as an NRN, or you are planning services and conduits while the RCC is still open, this is for you.
Subscribe on YouTube @aenishshrestha3928 for the build clips; here we go deeper into the thinking behind them. You can also explore more construction notes on aenishshrestha.com.
What the demo actually was
On camera I showed a compact setup centered on an ESP32. The board is hooked into things I already use at the desk—display modes, quick switches, and a simple UI so I can jump between views (including a YouTube-related screen in the demo). The point was not flashy gadgets. The point was one board that can talk to the network, read sensors, and give me control without walking room to room.
I added a room temperature sensor so the dashboard is not only about switches. It reports the environment of the space I am in. Flip a control on the interface and the state updates on the board-side setup. Everything is tied through the router and a small server path, so monitoring is not locked to standing next to the hardware. In the same spirit, I have been experimenting with monitoring and interaction through ChatGPT-style interfaces—so status is not only a local screen; it can sit in the tools I already open every day.
That is the seed: start small, keep it on your own network, and expand only when a feature saves you a real trip down the stairs or a real phone call to someone on site.
Why a civil engineer cares about home automation
Most of my day is still beams, slabs, contractors, and material tracking. Home automation sounds like a different profession until you notice how often “smart” decisions fail because the building was never prepared for them.
If conduits, neutral points, router placement, and sensor paths are afterthoughts, you end up with ugly surface wiring, dead Wi‑Fi corners, and systems that die the first time the monsoon humidity or a power blip hits them. When you plan like a builder, automation becomes another layer of the house—like waterproofing or earthquake detailing—not a sticker you put on after handover.
NRN angle: the house you cannot walk through every evening
A lot of readers here are Non-Resident Nepalis funding or supervising a home from abroad. Remittance pays for the structure; trust and remote visibility pay for peace of mind. A basic temperature and status dashboard will not replace a good supervisor, but it reduces blind spots. You can see if a room is overheating with closed windows, whether a device came back after load-shedding-style interruptions, or whether someone left a circuit in an unexpected state.
Remote monitoring should stay honest: sensors report; they do not discipline contractors for you. Pair automation with clear site reports, photos, and a material tracker habit. The tech is a window, not a full-time site engineer.
Monsoon, dust, and power reality in Nepal
Nepal homes deal with wet seasons, dusty dry months, and uneven power quality depending on location. Consumer “smart bulbs only” kits often assume stable broadband and gentle climates. When you design around ESP32-class boards and local servers, you can choose enclosures, power protection, and offline-friendly behavior that match how houses here actually live.
Think about: elevated placement away from splash zones, sealed boxes near wet areas, surge protection on the supply side, and not putting your only control path on a single cloud account that fails when the uplink drops.
ESP32 as a practical starting point
I started with ESP32 because it is common, Wi‑Fi capable, and flexible enough for sensors plus simple control logic. In the demo, it is the brain sitting between “things in the room” and “what I see on a screen.”
You do not need to memorize every pin on day one. You need a clear list:
- What you want to measure (temperature first is a great habit).
- What you want to switch or signal.
- Where the board lives (ventilation, access, cable length).
- How it joins your router and what happens if Wi‑Fi drops.
Keep firmware and credentials documented. Future you—or your electrician cousin—should not reverse-engineer a mystery box during festival week.
Room temperature is more than a number
The temperature sensor in the build is the quiet hero. In Kathmandu valley houses and hillside homes, orientation, cross-ventilation, and slab heat all change how a room feels. A sensor turns “it feels stuffy” into a trend you can compare morning vs afternoon, or ground floor vs top floor.
For new construction, leave clean paths for future sensors in bedrooms, kitchen exhaust zones, and server/router corners. You may not install everything in phase one. You will thank yourself when you are not chiseling finished plaster later.
Mobile control, holders, and human habits
In the video I show control from a simple interface and a physical arrangement that includes a mobile holder. That detail matters more than it sounds. If the “smart” UI is annoying to reach, people stop using it and go back to wall switches only—or worse, they leave systems in half-configured states.
Design for the way families actually move: entrance, kitchen, staircase landing. A civil engineer’s instinct helps here—traffic flow, sight lines, children’s reach, and elderly users. Automation should reduce friction, not add a second job.
Server, router, and the “whole house” view
The demo ties into the router and a server-backed path so monitoring is centralized. That is the difference between a lonely gadget and a small system. Once status lives on the network, you can expand rooms without buying five unrelated apps.
Be intentional about design:
- Put the router where structure and walls will not murder the signal—plan during brick and block work if you can.
- Label SSID devices clearly (room + function), not random factory names.
- Separate “experiments” from “family-critical” circuits until you trust the setup.
- Document power sources and backup behavior.
Nepal National Building Code (NBC) practice already pushes us to think about safety, seismic resilience, and proper electrical workmanship. Smart layers should ride on top of code-aware electrical design—not replace licensed work or safe earthing. If you are pouring RCC or running concealed conduits, coordinate low-voltage routes with the same seriousness you give main power.
ChatGPT-style monitoring: useful, not magical
I mentioned monitoring through ChatGPT in the video. The useful idea is conversational status: ask what the room reads, or summarize device state in language humans actually use. The risk is treating an AI chat window as a certified control system for life-safety equipment. Keep AI on the advisory and visibility side until you fully understand failure modes.
For NRN owners, a natural-language summary of home status can sit beside weekly site updates. Still verify critical events with human eyes on the ground.
Building automation into a Nepal house plan
If your house is still on paper—or structure is ongoing—this is the cheapest time to be smart.
During planning and Vastu / layout talks
When you settle room functions, mark candidate points for sensors and access points. Avoid trapping the router in a closed concrete corner “for aesthetics.” Beauty matters; so does a signal that reaches the kitchen.
During structural and electrical rough-in
Coordinate with your electrician for:
- Extra conduit stubs to ceiling sensor points.
- Dedicated, well-labeled neutral and earth practices as per sound electrical norms.
- Space for a small enclosure near the distribution board for future controllers—not a spaghetti nest above the main door.
Earthquake-resistant thinking still comes first: do not compromise structural members for a gadget path. Drill and chase only where the structural design allows.
After plaster and paint
If the house is finished, start with non-invasive nodes: temperature, humidity if you add it later, plug-level controls where safe, and strong Wi‑Fi before you chase walls. Prove the habit of using the dashboard before you expand to more loads.
A simple roadmap you can copy
Here is the sequence I recommend to viewers who message me after the short:
- Fix reliable power and network in one room.
- Deploy ESP32 + temperature sensor and confirm stable readings for a full week—including a rainy day if you can.
- Add one control action you actually use daily.
- Expose status on a single dashboard you open without thinking.
- Only then wire a second room or a chat-based status layer.
Happy building is not “buy everything.” Happy building is “ship something that still works next month.”
Cost mindset without fake numbers
People always ask how much. Honestly, it varies based on how many rooms you cover, whether you use local modules or imported kits, enclosure quality, and whether an electrician must rework finished walls. Skip vanity bundles. Budget for protection, labeling, and time to configure—not only the board price you saw in a thumbnail.
If you are an NRN sending money home, earmark a small “visibility and controls” line in your overall construction budget the same way you earmark waterproofing. It is easier to defend a planned line item than a random shopping spree after handover.
Common mistakes I want you to avoid
- Buying closed apps that cannot export data when you change phones.
- Hiding boards in hot, unventilated cabinets.
- Skipping surge and safe isolation on anything that switches mains—get competent electrical help.
- Automating messy processes: if the household never agreed who controls the living room lights, software will not create discipline.
- Forgetting monsoon ingress paths around external sensors or poorly sealed boxes.
How this ties back to the rest of my work
On this site I write about Nepal house construction realities—material tracking, contractor friction, RCC and panel choices, gates, earthquake-aware detailing, and tools that help civil engineers stay honest with numbers. Home automation sits in that same bucket: practical tech that serves the building and the people funding it.
If you are mid-build, pair this topic with your broader planning reading on Aenish Shrestha’s site and keep the YouTube tab open for the hands-on cuts. The short video shows the board alive; this article is the checklist I wish more owners ran before they bought a box of random smart plugs.
FAQ
Is ESP32 good enough for a full house in Nepal?
It is an excellent starting brain for sensors and staged control, especially when you own the network setup. “Full house” success depends more on wiring quality, power stability, and clear room-by-room scope than on the brand name of the board.
Can NRN owners rely on this instead of site visits?
No. Use it as a complement to supervisors, photo logs, and scheduled calls. Sensors reduce uncertainty; they do not sign off concrete quality or resolve disputes.
Do I need ChatGPT to make home automation work?
No. The core is board, sensors, safe control, and a dashboard. Chat-style monitoring is an optional interface layer for status and summaries.
When should automation be planned in a new build?
Ideally at layout and electrical rough-in, so conduits, router placement, and enclosure space are intentional. Retrofits are possible but often messier after plaster.
What should I automate first?
Start with visibility—temperature and device status—then one high-friction control you repeat daily. Expand only after a week of stable use.
CTA
If this helped you connect the YouTube demo to a real Nepal house plan, stick around. I share builder-in-public notes for NRN and local owners who want clearer control of cost, site truth, and practical tech. Watch the next build update on youtube.com/@aenishshrestha3928, subscribe so you do not miss the field clips, and browse more guides at aenishshrestha.com. Happy building—peace.
