Smart Home Without the Cloud: Home Assistant for Indian Homes

Smart Home Without the Cloud: Home Assistant for Indian Homes

A smart home that stops being smart the moment your internet drops isn’t really smart. It’s a remote control with extra steps. Cloud-dependent setups—lights, plugs, and voice assistants that phone home to servers in Singapore or Oregon for every routine—revert to manual control during outages. A locally-run hub like Home Assistant, a free open-source platform typically hosted on a Raspberry Pi, keeps automations working because it processes routines on your network, not in the cloud.

About the prices and versions: Rupee figures for the Raspberry Pi, storage, smart bulbs, smart plugs and Zigbee dongle are what Indian sellers were asking when this guide was written, before GST; hardware prices move quickly, so treat them as indicative rather than a quote. The Nabu Casa price is in US dollars, as listed on its pricing page. Commands follow the documentation linked under Sources as it stood when this guide was written; check it before assuming a command or option still matches.

why local-first hits different in India

Comparison: a cloud smart home sends every command to vendor servers abroad and back, failing in outages; a local Home Assistant setup controls devices directly on the LAN.
A smart home that stops when the internet drops is a remote control with extra steps.

We’ve taken to smart devices fast. Alexa and Google Home speakers are a common sight in Indian living rooms now, and a Wipro or Mi bulb goes for less than a movie ticket when there’s a sale on, usually somewhere around ₹400 to ₹600. The catch, and it’s a big one, is that nearly all of this stuff leans on the cloud. You tap the bulb icon, and the command leaves your phone, flies off to a server abroad (Tuya’s cloud for Wipro and Syska, Xiaomi’s for Mi), and comes back to a bulb sitting three metres from where you’re standing.

Think of it like commuting from Whitefield to MG Road for a meeting you could’ve taken on a call from home. That round trip falls apart in exactly the conditions Indian homes hit all the time. ISP outages when it rains. Congested networks in the evening. Companies quietly killing off a cloud service you’d built your routines around. Then there’s privacy, which I think people underrate. When you wake up, when the house sits empty, all of it lives on someone else’s machine. Home Assistant turns that around. One small computer at home becomes the brain, your devices chat with it over local Wi-Fi, and the internet drops to optional. If you’ve read my home automation starter guide, this is the graduation ceremony.

the hardware, and what it actually costs

Table of a Home Assistant build in India: a Pi or a free old laptop as hub, storage, Wi-Fi bulbs, 16A plugs and an optional Zigbee dongle, with approximate costs.
If a laptop is already in a drawer, the hub costs nothing.

Home Assistant isn’t fussy about hardware. Here’s a realistic Indian build, using the prices in the dated note at the top.

ComponentOptionApprox. cost
HubRaspberry Pi 4 (4 GB) or Pi 5₹5,000–₹8,000
Hub (free option)Old laptop you already own₹0
Storage32 GB A2 microSD or small SSD₹600–₹2,500
Smart bulbsWipro / Syska / Mi Wi-Fi bulbs₹400–₹700 each
Smart plugsWipro 16A (check rated wattage against your geyser)₹900–₹1,200
Optional Zigbee dongleSonoff ZBDongle-E₹1,800–₹2,500

The Pi is the classic pick. If you’ve already got one lying around for other tinkering (my Raspberry Pi 5 projects list has a few), it pulls double duty nicely. Granted, the Pi is the obvious answer. But for most people an old laptop turned into a home server is the smarter buy. It’s free, it’s quicker than a Pi, and its battery doubles as a built-in UPS, which counts for more here than just about anywhere. And the power draw is tiny either way. A Pi pulls under 7 watts, so leaving it on 24×7 adds maybe ₹30 to ₹40 a month to your bill.

getting Home Assistant OS on the box

Four steps to install Home Assistant OS: choose it in Raspberry Pi Imager, select the Pi model build, connect Ethernet and power on, then open homeassistant.local:8123.
Set your location during setup so sunrise and sunset automations work.

Easiest path is Home Assistant OS, a purpose-built operating system that handles updates and add-ons so you don’t have to.

  1. Download Raspberry Pi Imager on your PC and insert the microSD card.
  2. In the Imager, choose Other specific-purpose OS, then Home automation, then Home Assistant, and pick the Home Assistant OS build for your Pi model (RPi 4 or RPi 5).
  3. Write the image, slot the card into the Pi, connect it to your router with an Ethernet cable, and power it on.
  4. Wait five to ten minutes, then open the setup page from any browser on the same network:
http://homeassistant.local:8123

Make your account, name the home, set your location so sunrise and sunset automations work (handy for lights), and that’s you in. One thing I’d push on: wire the hub in over Ethernet if you possibly can, not Wi-Fi. The hub is the single device in your house that should never have a shaky connection.

making Wipro, Syska and Mi gear go local

Three levels for Wipro, Syska and Mi devices: the Tuya cloud integration, LocalTuya over the LAN, and fully local Zigbee or ESPHome.
You do not have to pick the hardest level. LocalTuya covers most existing gear.

Here’s the bit most YouTube videos skip over. Budget Indian smart devices are built for the cloud, and prying them loose takes a little effort. There are three levels of commitment, and you don’t have to pick the hardest one on day one.

level 1: cloud integration (easy, still cloud)

Wipro and Syska devices run on Tuya’s platform, and the official Tuya integration brings in devices that are in the Tuya Smart or Smart Life app: you sign in with the User Code from that app and scan a QR code. If your bulbs were set up in a brand app such as Wipro’s, you may need to add them to Smart Life first, so check the integration docs before you reset anything. Mi bulbs come in through Xiaomi’s own Xiaomi Home integration, a custom integration installed through HACS or from Xiaomi’s GitHub rather than built into Home Assistant. Everything lands in one dashboard, which is a real step up on its own. The commands still go out through the cloud, though, so you haven’t fixed the actual problem yet.

level 2: LocalTuya (the sweet spot)

LocalTuya is a community integration you install through HACS. It talks to Tuya devices straight over your LAN using each device’s local key. Pulling those keys out of the Tuya developer portal will eat an evening of your patience, granted. But once it’s done, your Wipro bulb responds over your own network with the internet physically unplugged. A setup like this keeps working through ISP outages.

level 3: Zigbee or flashed firmware (fully local)

For anything new you buy, look at Zigbee devices paired with a ₹2,000 USB dongle, or Wi-Fi devices reflashed with ESPHome. Reflashing is for devices you own and usually voids the warranty. Many Wi-Fi switches and plugs are mains-powered, so never open or flash one while it’s connected to mains, and leave anything that sits in fixed wiring to a licensed electrician. These can operate locally on the LAN when configured without vendor integrations, but firmware updates, backups, DNS, voice services and any enabled cloud integration can still contact external systems. Check each device’s current documentation and settings before describing it as local-only. A sensible split is to move critical switches to Zigbee or ESPHome and leave cheap Tuya bulbs on LocalTuya, since they’re not worth the bother.

automations that actually pull their weight

Home Assistant YAML: when switch.mains_probe_plug becomes unavailable for one minute, send a phone notification that mains power is down.
The same trigger can switch off non-essential plugs to stretch the inverter battery.

Dashboards are nice. Automations are the whole point. A handful that fit Indian homes:

  • Geyser discipline: the 16A smart plug switches the geyser on at 6 AM and off after 25 minutes, which saves real money versus letting it run. Use a plug rated for at least the wattage on the geyser’s nameplate with some headroom, carrying the ISI mark and described by its manufacturer as suitable for a water heater; a wired-in geyser is a job for a licensed electrician, not a plug.
  • Power cut alerts: a smart plug on raw mains (not inverter backup) doubles as a sensor. When it goes unreachable, Home Assistant pings your phone that the house has flipped to inverter.
  • Inverter load shedding: that same trigger kills non-essential plugs so the battery stretches to cover fans and Wi-Fi.
  • Sunset lights: balcony light on at sunset, off at 11 PM, no app-tapping, ever.

The power cut one looks like this in YAML, though you can build the whole thing in the visual editor if you’d rather not touch text:

alias: Power cut alert
triggers:
  - trigger: state
    entity_id: switch.mains_probe_plug
    to: "unavailable"
    for: "00:01:00"
actions:
  - action: notify.mobile_app_your_phone
    data:
      message: "Mains power looks down. House is running on inverter."

Here switch.mains_probe_plug is the smart plug on raw mains: when it loses power, Home Assistant marks it unavailable. How quickly that happens depends on the integration, so tune the for: delay after watching it through a real cut.

And keep your Alexa or Google speaker. Home Assistant exposes its devices to them either through Home Assistant Cloud from Nabu Casa, the official subscription that also funds the project (US$6.50 a month or US$65 a year plus tax on its pricing page when this was checked, billed in dollars), or by self-hosting the integration yourself if you would rather not pay and don’t mind the setup work. That route needs your Home Assistant reachable from the internet over HTTPS, so treat it as a security project: a strong password, multi-factor login and prompt updates. Both are documented routes — don’t go looking for ways to stretch a trial, because that breaks the terms and the project is funded by exactly those subscriptions. With one of them in place, voice control keeps ticking while the logic stays at home. Put your router and the Pi on the inverter line too. Together they sip maybe 15 watts, and a smart home that dies with the mains is, well, not a smart home. Devices left on raw mains drop off and reconnect on their own when supply comes back, and Home Assistant boots back up on its own after a full blackout; give it a few minutes, no fiddling required. If you’re already running Pi-hole, the two sit happily on one device.

a few things worth knowing early

Early Home Assistant tips: reserve IP addresses for devices, back up weekly off the SD card, get one device fully local before expanding, and name entities clearly.
Keep your Alexa or Google speaker: Home Assistant can expose devices to them.
  • Set static IPs (DHCP reservations) for every smart device in your router. LocalTuya breaks silently when an IP shifts under it.
  • Turn on automatic backups in Home Assistant and copy them off the SD card every week. SD cards die. With a backup it’s a 20-minute annoyance instead of a ruined weekend.
  • Buy one device, get it fully local, then expand. Half-working mixed setups are exactly how people give up.
  • During sales, Wipro and Syska bulbs slide down near ₹350. Stock up then, not at MRP.
  • Name your entities properly from day one (light.bedroom_ceiling, not light.bulb_3). Future you will be grateful.

FAQ

Will my existing Alexa routines stop working if I add Home Assistant?

No. Home Assistant sits next to your existing apps rather than replacing them. The bulbs stay paired to their app (Smart Life, or Mi Home for Xiaomi) like before. You can move control over gradually, and once you link Home Assistant to Alexa, the speaker just sees more devices than it used to.

Is Home Assistant really free?

The software’s completely free and open source. Your only costs are the hardware (₹0 if you repurpose an old laptop), electricity of around ₹30 to ₹40 a month, and the optional Nabu Casa subscription if you want effortless remote access and voice linking. Plenty of people run it without ever paying a rupee.

Can I reach my smart home from outside without the cloud?

Yes, using a self-hosted VPN like WireGuard on the same Pi or laptop. Your phone connects home securely and the Home Assistant app behaves as if you were sitting on your own sofa. Jio and Airtel run CGNAT on a lot of plans, so you might need a tunnel through a cheap VPS, but it’s a solved problem.

where this leaves you

A smart home leaning on foreign servers and never-dropping broadband was always an awkward fit for how things actually work here. A Raspberry Pi or retired laptop can keep compatible local automations working during an internet outage, provided the controller, router and devices still have power. Cloud-dependent features, including Alexa voice control, can stop working when the connection drops. It doesn’t have to be finished on day one. Move switches to Zigbee a few at a time, test a backup restore before you need it, and sort out remote access behind CGNAT when you get to it. Even a half-built version beats watching your lights go dark because a server in Oregon hiccupped.

Update history: the power-cut automation now uses current Home Assistant syntax and a trigger that can fire; the Tuya, Xiaomi Home and Imager steps and the Nabu Casa price are corrected; and safety notes and sources are added.

Sources