Studio Matrx Monthly · Volume 1 · Issue 2 · July 2026
Amogh N P
 In loving memory of Amogh N P — Architect · Designer · Visionary 
Best Smart Home Scenes & Automations for Indian Homes (with Recipes)
Smart Home

Best Smart Home Scenes & Automations for Indian Homes (with Recipes)

Scenes versus automations, the triggers that matter, and twenty recipes that genuinely earn their keep — good morning, geofenced arrival, pre-cool, power-cut handling and more, built on Alexa, Google and Home Assistant.

20 min readAmogh N P5 July 2026Last verified July 2026

A smart home that needs you to open an app for every light and fan is just a slower switchboard. The payoff arrives when the home starts acting on its own — lights easing on at sunset, the AC pre-cooling before you reach the gate, the corridor glowing dim when you pad to the bathroom at 2 AM. That behaviour is built from two simple ideas: scenes and automations. Get the vocabulary and the recipes right, and a modest kit of devices starts to feel genuinely intelligent.

This is a companion to the Studio Matrx smart homes pillar guide and the broader home automation guide. Where a topic deserves depth we link out — lighting, security, networking and voice assistants. To price a setup, use the smart home cost calculator.

The best automation is the one you forget you ever built. You notice it only on the day it stops working — and that is the highest compliment a home can pay you.

Scenes versus automations: the core distinction

A scene is a saved snapshot of device states that you trigger yourself — by tapping a tile, pressing a scene button, or saying "Alexa, movie time." One command sets many devices at once. A Movie scene might dim the living-room lights to 20%, close the curtains, switch the TV on and turn the fan to low. Nothing happens until you ask.

An automation (Alexa calls these Routines, Google calls them Automations, Home Assistant simply Automations) is a scene plus a trigger and conditions — logic that fires without you. "At sunset, if someone is home, turn on the porch and hall lights at 40%." The home decides.

SceneAutomation
Who starts itYou, on demandA trigger (time, sensor, location)
ContainsDevice statesTrigger + conditions + actions (often a scene)
Example"Good night" tap sets everything offLights fade on automatically at sunset
Best forMoods you chooseBehaviour you want by default
Effort over timeTap every timeSet once, forget

In practice you build scenes inside automations. Create a "Leaving Home" scene once, then have a geofence automation run it when you cross out of a 300 m radius. Reuse beats rebuilding.

Anatomy of an automation

Every automation, on every platform, is the same three-part sentence: when this happens (trigger), and if this is true (condition), then do this (action).

Anatomy of an Automation TRIGGER When... Sunset Motion detected You reach home CONDITION And if... Someone is home It is after 10 PM Power is on ACTION Then do... Lights on 40% Start the AC Notify phone Condition is optional — but it is what keeps automations from being annoying Without a condition, sunset lights turn on even when the house is empty and the corridor lights wake you at midday. Conditions add common sense.

The condition is the part beginners skip and later regret. A sunset-lights automation with no condition fires even when you are away on holiday, wasting power and advertising an empty house. Add "and if someone is home" and it behaves.

Trigger types you can use

Trigger typeFires onGood for
Time / scheduleA clock time or sunrise/sunset offsetMorning, night, geyser pre-heat
Presence / locationYour phone entering or leaving a geofenceArriving, leaving, arm-on-leave
Sensor (motion, contact, occupancy)Movement, a door opening, a room occupiedCorridor lights, security, path lighting
EnvironmentalTemperature, humidity, air quality, water levelPre-cool, exhaust fan, tank fill
Device stateAnother device turning on or a scene runningChaining, "TV on → dim lights"
Voice / manual / buttonYou asking or pressingScenes, overrides

Sunrise and sunset triggers deserve a special mention in India: because they follow the sun, a "sunset lights" automation stays correct through the year without you touching it — roughly 5:50 PM in December and 7:00 PM in June across most of the country.

Twenty automations worth setting up

These are the ones that repay the setup effort in Indian homes. Start with three or four, live with them for a week, then add more.

#AutomationTriggerWhat it does
1Good MorningAlarm time / 6:30 AM weekdaysGeyser on, soft lights, weather and calendar read out
2Good Night11 PM or "good night"All lights off, doors checked, AC to sleep temp, arm alerts
3Leaving HomeGeofence exit (all phones)Lights and AC off, arm security, notify if a door is open
4Arriving HomeGeofence entry (any phone)Porch and hall lights on, disarm, gate camera snapshot
5Pre-cool15 min before geofence entry / scheduleAC starts so the room is cool when you walk in
6Sunset LightsSunset, if someone homeFacade, hall and porch lights to a warm 40%
7Movie Mode"Movie" sceneDim to 20%, curtains close, TV and soundbar on
8Night Path LightingMotion 11 PM to 5 AMCorridor and bathroom lights at 15%, off after 2 min
9Geyser Schedule30 min before bath timeHeats only when needed, saves standby loss
10Empty-Room OffNo motion 15 minLights and fan off in unoccupied rooms
11Water Tank FillLevel sensor lowMotor on; auto-off at full, alert on dry run
12Power-Cut NoticeMains power lostPush notification; log start time
13Power RestoredMains returnsNotify; resume geyser/pump schedule safely
14High-Voltage CutoffVoltage sensor over thresholdAlert; cut sensitive-load smart plugs
15Bathroom ExhaustHumidity over 70%Fan on until humidity drops, then off
16Kids Study Mode5 PM weekdaysBright neutral light in study, Wi-Fi TV paused
17Guest Mode"Guest" sceneGuest Wi-Fi on, spare-room AC and lights ready
18Vacation ModeManual toggleRandom evening lights to look occupied; all else off
19Doorbell AnnounceVideo doorbell pressChime on speakers, snapshot to phone
20Low-Battery NagAny sensor battery lowWeekly digest of devices needing a new cell

Numbers 3, 4, 5 and 8 tend to become favourites — they remove daily friction you did not know you were tolerating. Automations 11 to 14 are distinctly Indian: they wrap smart plugs and sensors around the realities of tank-fed plumbing, load-shedding and unstable voltage. Pair them with the security systems guide for the arm-on-leave logic.

A day in the life of an automated home

A Day of Automations 6:30 AM Good Morning 9:15 AM Leaving: arm, off 6:20 PM Pre-cool + arrive 6:50 PM Sunset lights 11:00 PM Good Night Teal = comfort and lighting Terracotta = presence-driven You touched a switch zero times all day Overnight, motion-path lighting quietly handles the 2 AM walk to the bathroom

Notice how presence (geofencing) and time triggers do most of the work, with sensors handling the small, thoughtful moments. Nothing here needs an expensive wired system — a hub, a few smart switches, two motion sensors and a temperature reading are enough.

Building them on each platform

The concepts are identical; the menus differ. Here is where to start on the three common platforms in India.

PlatformWhere to buildStrengthWatch-out
AlexaApp → More → RoutinesEasiest voice triggers, wide device supportGeofencing is basic; cloud-dependent
Google HomeApp → Automations (+ script editor)Good household presence, natural phrasesSome actions still app-only
Home AssistantSettings → Automations / YAMLTotal control, runs locally, any triggerNeeds a hub and a learning curve

Alexa Routines: pick a trigger (schedule, voice, device, location, sound like a smoke alarm), add actions, save. For geofencing, add your phone under Settings and use the Location trigger. Everything runs in Amazon's cloud, so a Wi-Fi outage stops routines.

Google Home Automations: the tap-to-build editor covers most needs; the household routines and script editor (YAML-like) unlock conditions and starters like device state. Presence is handled well when multiple family phones are added.

Home Assistant is the enthusiast's choice and the only one that runs entirely on local hardware — a Raspberry Pi or mini-PC in your home. Its automation editor exposes every trigger, condition and action, and because it is local, automations keep working when the internet drops. It is the right home for the power-cut, voltage and tank-fill recipes. See the local versus cloud discussion and networking guide before you commit.

How to avoid annoying automations

The fastest way to make a family hate the smart home is a badly tuned automation. A few rules keep them welcome.

  • Always add a condition. "If someone is home", "if after sunset", "if the door was actually opened." Unconditional automations are the ones that turn lights on at noon.
  • Use timeouts, not just triggers. Motion-path lights should turn off after two minutes of no motion — otherwise they stay on all night.
  • Dim at night. Night automations should never blast full-brightness white. Warm, 15 to 20% light respects sleeping eyes.
  • Give a manual override. A physical switch or a voice command must always beat the automation. Family members should never feel trapped by the logic.
  • Beware presence flapping. Geofences can trigger repeatedly at the boundary. Use a larger radius (300 m) and a small delay so "arriving" does not fire five times.
  • Start small and observe. Add automations one at a time and live with each for a week before building the next.

A good automated home feels calm, not chatty. If a rule surprises or nags you more than it helps, delete it — a smart home should reduce decisions, not add them.

Where to begin

If you own a hub and a handful of smart switches or bulbs, build these four first: Sunset Lights (with the "someone home" condition), Night Path Lighting, Good Night, and a Leaving-Home arm-and-off. Live with them for a fortnight. You will quickly feel which parts of your day were quietly full of small chores — and that is exactly where the next automation belongs. Cross-reference the lighting guide for scene design and the voice assistants guide to add spoken triggers.

References

Export this guide