In this guide
- Why most smart home alerts end up muted
- The three alert tiers: critical, actionable and informational
- Twelve alerts worth designing for a Hyderabad home
- Five tools that cut noise: modes, delays, windows, cooldowns and escalation
- Who should receive what
- What still works when the internet is down
- The first two weeks: tuning alerts to the family
- How Pert delivers it (designed, not DIY)
- FAQs
This article is part of our wider coverage of home automation in Hyderabad. Alerts are built from the same trigger, condition and action logic as any other automation; if that vocabulary is new, start with sensor-triggered home automation: triggers, conditions and actions, then come back here.
Why most smart home alerts end up muted
A typical 3BHK with a main door contact, two balcony door contacts, three motion sensors, a video doorbell and a couple of cameras generates a surprising number of events. A family of four opens the main door 20 to 40 times a day between school runs, deliveries, the milk packet, domestic help and evening walks. A passage motion sensor can fire more than a hundred times. If each event becomes a notification, the phone buzzes every few minutes, and every buzz trains the family to ignore the next one.
The fix is to separate two things that cheap setups treat as one: an event (something a sensor noticed) and an alert (something a person needs to know now). Every event can be recorded. Only a small fraction should ever reach a lock screen. A useful target for a well-designed home is:
- Zero to three phone notifications on an ordinary day at home.
- Every notification either needs an action or confirms something you explicitly asked to be told about.
- No notification for something the household did on purpose a moment ago — if you pressed Leaving on the entrance keypad, you do not need your phone to tell you the lights went off.
The three alert tiers: critical, actionable and informational
Before any individual alert is written, we agree three tiers with the family. Each tier has its own delivery, its own recipients and its own rules about night time.
| Tier | Meaning | Examples | How it is delivered | At night |
|---|---|---|---|---|
| Critical | Something may be wrong right now; someone should look immediately | Main door opened while in Away mode; indoor motion while nobody is home; balcony door opened during Night mode | Phone notification to all responsible adults, plus a local action in the home (lights on, local chime) | Always delivered, even in quiet hours |
| Actionable | Needs attention soon, not this second | Main door left open for 5 minutes; doorbell ringing while you are out; gateway offline for 10 minutes | Phone notification to the person most likely to act | Held until morning unless it is security-related |
| Informational | Useful to know, never urgent | Sensor battery low; curtains closed on schedule; power restored after an outage; who came home at what time | Event log in the app, or a daily or weekly summary | Never pushed |
The discipline is simple: when someone asks for a new alert, the first question is which tier it belongs to. Most requests turn out to be informational, and move to the log.
Twelve alerts worth designing for a Hyderabad home
These are the alerts we most often design, written the way we write them on a project: what triggers them, the conditions that must also be true, how long we wait before sending, and the tier. Times and delays are starting points that are tuned to each family.
| # | Alert | Trigger | Conditions | Delay | Tier |
|---|---|---|---|---|---|
| 1 | Door opened while away | Main door contact opens | Home is in Away mode | None | Critical |
| 2 | Movement in an empty home | Indoor motion sensor | Away mode; not a pet-exempt zone | Two detections within 60 seconds | Critical |
| 3 | Balcony or terrace door at night | Balcony door contact opens | Night mode active (for example 11pm to 5:30am) | None | Critical |
| 4 | Main door left open | Main door contact open | Any mode | 5 minutes by day, 2 minutes after 10pm | Actionable |
| 5 | Visitor while you are out | Video doorbell button | Away mode | None | Actionable |
| 6 | Movement at the gate or door while away | Doorbell or camera motion detection | Away mode; person-sized movement; outside delivery hours if preferred | Cooldown 15 minutes | Actionable |
| 7 | Gateway offline | Gateway stops reporting | — | 10 minutes, to ride out brief power blips | Actionable |
| 8 | A device stopped responding | Keypad, curtain motor or sensor unreachable | — | 30 minutes | Actionable to the system manager |
| 9 | No morning movement (elderly parents) | Time of day reaches, say, 9:00am | No motion in parents' room or passage since 5:00am; parents not away | — | Actionable to adult children |
| 10 | Night-time bathroom stay (elderly parents) | Bathroom door contact closes | Night mode; door still closed | 40 to 45 minutes | Actionable |
| 11 | Battery running low | Sensor battery below about 20% | — | Collected weekly | Informational |
| 12 | Power restored | Gateway reboots after an outage | — | Once, with outage duration | Informational |
Notice what is not on the list: "door opened" while the family is home, "motion in the living room", "lights switched off", "curtains closed". Those are events for the log. Alerts 9 and 10 are covered in more depth in home automation for elderly parents in Hyderabad, and alerts 1 to 3 depend on the Away and Night modes described in how to plan Away mode for a smart home.
Five tools that cut noise: modes, delays, windows, cooldowns and escalation
1. Modes decide whether an event matters
The same event means different things at different times. A main door opening at 7:30pm on a weekday is the family coming home; the same door opening while the home is in Away mode is the most important alert in the system. Almost every good alert has a mode as a condition. That is why we put Leaving, Arriving and Good Night on the entrance and bedside keypads: pressing a physical button is the most reliable way for a house to know whether anyone is home or awake, and it quietly switches the right alerts on and off.
2. Delays filter out normal behaviour
A door that is open for ten seconds is someone walking through it. A door that is open for five minutes is a door someone forgot. Delays turn raw sensor states into meaningful situations. For motion, requiring two detections within a minute avoids the single false trigger from a curtain moving in the AC draught or sunlight sweeping across a floor.
3. Time windows respect how the family lives
Quiet hours stop actionable alerts from waking people for things that can wait until morning. Delivery windows (for example, 8am to 9pm) stop camera motion at the gate from pinging every time the building's security guard walks past.
4. Cooldowns stop repeats
If a camera sees movement at the gate, one alert is useful; twelve alerts in four minutes are not. A cooldown of 10 to 15 minutes per alert means you hear about the situation once, with the full detail in the log.
5. Escalation makes sure someone responds
For critical alerts, we define a primary person and a backup. If the primary has not opened the alert within about five minutes, the backup is notified. In a joint family this often means the alert goes first to the person who set Away mode and then to a sibling or neighbour who can check in person.
Who should receive what
Alerts should follow household roles, not simply whoever installed the app. A starting point we use:
| Person | Critical | Actionable | System health | Summary |
|---|---|---|---|---|
| Homeowners (both adults) | Yes | Yes, split by who is usually home | One of them | Weekly |
| Adult children living elsewhere | Yes, as escalation backup | Only elderly-care alerts | No | Optional |
| Elderly parents | Usually no; local cues instead | No | No | No |
| Teenagers | No | Door-left-open only, if useful | No | No |
| Domestic staff, drivers | No | No | No | No |
| Your installer | No | No | With your consent, gateway and device health | No |
Two principles sit behind the table. First, anyone who receives an alert must be able to do something about it; notifying a person who cannot act only adds anxiety. Second, privacy matters: a log of who came and went at what time is sensitive information, and it should be visible only to the people who need it.
What still works when the internet is down
It helps to be precise about where each part of an alert lives. The detection and the automation — a door contact opening, the gateway checking the mode, the passage lights switching on — happen locally, between the sensors and the Pert gateway inside the home. The phone notification travels from the home over the internet to a cloud service and then to your phone. So when the broadband goes down, the house still reacts, but your phone may not hear about it until the connection returns.
That is why we design every critical alert with a local half as well as a phone half:
- Lights as a deterrent and a signal. On alert 2, the living and passage lights switch to full and the curtains stay as they are, so the house visibly reacts.
- A local cue for people at home. On alert 3, a soft passage light or a chime tells the family inside, even if nobody's phone is nearby.
- Backup power for the essentials. The gateway, the Wi-Fi router and the sensors' nearest routers go on inverter-backed circuits.
- A "while you were offline" summary when connectivity returns, so nothing is silently lost.
Cameras and the video doorbell are Wi-Fi devices and depend on the network for live view and their own alerts; placing them well is covered in how to plan CCTV camera and sensor placement at home. What keeps working in each outage scenario is set out in do smart homes work during power cuts and internet outages?
The first two weeks: tuning alerts to the family
No alert plan is right on day one, because it depends on habits nobody writes down: when the help arrives, whether the balcony door is opened at 5am for the plants, whether a cat sleeps in the passage. We plan a short tuning period after handover:
- Days 1–3: start conservative. Critical alerts on; actionable alerts on with generous delays; everything else in the log only.
- Days 4–10: read the log together. Look for events that happened often and harmlessly (tighten or move them to the log) and situations that went unnoticed (add an alert).
- Day 10–14: adjust delays and windows. A 5-minute door delay may need to be 8 minutes for a family that carries groceries in from the car.
- Test every critical alert once, deliberately: set Away mode, open the door, confirm who receives what and how quickly, and check the local action happens.
- Revisit after life changes — parents moving in, a new pet, new domestic help, a long trip.
A useful sign of success: after a month, the family can describe every notification they receive, and none of them feels like noise. Our home automation handover and testing checklist includes the alert tests.
How Pert delivers it — a designed solution, not a DIY kit
On a DIY setup, every sensor arrives with notifications switched on and each app decides for itself what to tell you. On a Pert project, alerts are part of the design. We agree the three tiers and the household roles at the consultation; decide which modes the home needs and put Leaving, Arriving and Good Night on the right Stella keypads; position door contacts and motion sensors so they report the situations that matter rather than every passer-by; write each alert with its trigger, conditions, delay and recipients; pair each critical alert with a local action using the home's lighting and curtains; put the gateway and network on inverter backup; test every critical alert before handover; and tune the plan with you over the first two weeks. After that, when your household changes, we adjust the alerts with it. That is the difference between a box of sensors and a home that knows when to speak up.
If you are comparing who should design yours, best home automation companies in Hyderabad sets out what to ask — including how they plan alerts and who they send them to. For the security hardware itself, see smart home security in Hyderabad: locks, cameras and sensors.
Want a smart home that tells you what matters, and stays quiet otherwise? We will map your modes, sensors and alert tiers to the way your family actually lives, and test every critical alert before handover. Request a consultation →
Frequently asked questions
How many smart home notifications should I get in a day?
On an ordinary day at home, very few — zero to three is a good target, and most should be things you asked for, such as the doorbell ringing while you are out. Each door opening, each motion event and routine confirmations belong in the event log or a daily summary. A system that sends dozens of pings a day gets muted within weeks, and then it cannot warn you about the one event that matters.
Which smart home alerts are actually worth having?
Alerts tied to a situation, not just a sensor: the main door opening in Away mode; the main door left open for more than five minutes; a balcony door opening during Night mode; indoor motion when nobody is home; the doorbell ringing while you are out; the gateway offline for more than ten minutes; and, for elderly parents, no morning movement by a set time. Low batteries and routine events are better in a weekly or daily summary.
Do smart home alerts work when the internet is down?
Phone push notifications need the internet. The local part of an automation does not: the gateway can still detect a door opening, switch on lights, flash a passage light or sound a local chime. So we pair every critical alert with a local action, keep the gateway and router on inverter backup, and send a summary when connectivity returns so you know what happened while it was offline.
Who in the family should receive smart home alerts?
Decide by role. Critical security alerts go to every adult who can act on them, with a backup person if the first does not respond. Actionable alerts go to whoever is usually home at that time. System health alerts go to one person who manages the system, and to your installer if they provide support. Children and domestic staff generally should not receive security alerts.
