In this guide
- The usual suspects: where an unexpected command comes from
- Reading the clues: time, pattern and scope
- What an activity history tells you, and what it does not
- Five worked cases from Hyderabad homes
- Fixing the cause at the right level
- Designing a home that rarely surprises you
- How Pert delivers it (designed, not DIY)
- FAQs
This article is part of our wider coverage of home automation in Hyderabad. It is the companion to why home automation becomes unreliable, which deals with the opposite problem: commands that should happen but do not. Here the problem is an action nobody remembers asking for. For background on how rules are built and ranked, see sensor-triggered automation: triggers, conditions and actions and how home automation resolves conflicts.
The usual suspects: where an unexpected command comes from
Every change in a light, curtain or scene has a source. In a typical Zigbee home, the gateway receives instructions from a handful of places, and nearly every "ghost" turns out to be one of them.
| Source | How it causes a surprise | How often it is the culprit |
|---|---|---|
| Schedules | A fixed-time rule set up months ago and forgotten, or set to the wrong day, AM/PM or season | Very common |
| Sunrise and sunset routines | A routine tied to the sun runs at a different clock time as the seasons change, so it "suddenly" feels early or late | Common, especially around October to December and March to May |
| Sensor rules | A motion, presence or door sensor fires for a reason you did not picture: a pet, a curtain moving in the breeze, a maid entering early, a door left ajar | Very common |
| Other people | A family member, guest or staff member pressed a keypad button or used the app from another room or another city | Very common, and the most often overlooked |
| Voice assistants | Alexa or Google Home misheard a word from the TV or a conversation, or an assistant routine runs on its own schedule | Occasional |
| Scenes and groups | A scene button or master-off includes a load you did not expect, or a light was placed in the wrong group | Common in the first weeks after handover |
| Power events | After a power cut or a tripped MCB, lights and curtains follow their power-on behaviour, which may be "on" | Common in monsoon and summer |
| Leftover apps and integrations | An old Wi-Fi plug app, a previous installer's account or a forgotten voice routine still sends commands | Occasional, typical after an upgrade from DIY devices |
| A faulty device or wiring | A failing controller, a loose neutral or a switch wired in the wrong place | Rare, and usually shows as flicker or one device misbehaving alone |
Notice how far down the list the actual hardware fault sits. That matters, because resetting or re-pairing a healthy device removes it from its scenes and groups and creates a real problem where there was only a misunderstood rule.
Reading the clues: time, pattern and scope
Before opening any app, write down three things: when it happened (as exactly as you can), what changed (which lights, curtains or rooms, and to what level or position), and whether it repeats. Those three facts usually point straight at the source.
| Clue | Most likely source | What to check next |
|---|---|---|
| Same clock time every day, to the minute | A fixed schedule | The schedule list: time, days of the week, AM/PM |
| Roughly the same time, drifting a few minutes each week | A sunrise or sunset routine, possibly with an offset | The routine's offset, and whether a fixed earliest or latest time would suit better |
| Only when someone walks past or a door opens | A sensor rule | Which sensor, its timeout, and its conditions (time of day, mode) |
| Only on certain days, such as weekends | A schedule with the wrong days, or one person's routine | Day settings; ask who is home on those days |
| Several devices change together, to set levels | A scene, group or master-off | Which scenes contain those devices |
| Everything comes on at once, at full brightness | A power restore | Whether there was a power cut or an MCB trip at that time; the lights' power-on behaviour |
| Happened while the TV or a video call was on | A voice assistant mishearing | The assistant's voice history in its own app |
| One device only, at irregular times, sometimes with flicker | A device or wiring fault | Call your installer; do not reset it yourself |
| No pattern you can find, and nobody admits to it | Another person, an app account or an old integration | The activity history and the list of app users |
Ask the household first
It sounds obvious, but a quick question on the family group chat solves a large share of cases. Teenagers testing the app, a parent pressing the wrong keypad button in the dark, a driver turning on the gate light, or someone switching off the bedroom from their phone at the office are all ordinary explanations. How to manage smart home access for family, staff and guests covers giving each person the right level of control.
What an activity history tells you, and what it does not
Many gateways and smart home apps keep some form of activity history or event log: a time-stamped list of what changed. How much detail it holds varies a great deal between systems, so it is worth asking your installer what yours records and how far back it goes. A useful history answers four questions for each event:
- When did it happen, to the minute?
- Which device changed, and to what state, level or position?
- What triggered it: a named keypad button, a scene, a schedule, a sensor rule, an app user, a voice command, or the device itself reporting a change?
- What else happened in the same second? A scene leaves a cluster of entries with the same time stamp; a single entry points to one direct command.
Limits to keep in mind
- Not every source is visible. A voice assistant or a third-party app may appear only as "cloud" or "integration", without saying which routine or person sent it. Check the assistant's own history for those.
- Power events can look like nothing happened. If a light came on because power returned, the history may show the device rejoining or reporting "on" with no command behind it. A cluster of devices all reporting at the same moment is the signature.
- Gaps are clues too. If the gateway itself lost power or internet, there may be a gap in the history, which tells you the event happened during an outage.
- Clocks must be right. Schedules and history both depend on the gateway knowing the correct time and time zone (IST). A gateway that has drifted or is set to the wrong zone will run schedules at odd hours and record misleading times.
Five worked cases from Hyderabad homes
1. Curtains open at 6:10 am every Sunday
Clue: same time, every day including the weekend; the family only noticed on Sunday because everyone else was up by then on weekdays. Cause: the Morning schedule for the motorised curtains was set to "every day". Fix: keep the weekday schedule, and on weekends either move it later or tie it to the Morning scene button so curtains open when someone actually gets up. How to schedule home automation explains weekday and weekend patterns.
2. The balcony light is on at 2 am
Clue: not every night, mostly on windy evenings in the monsoon. Cause: a motion sensor covering the balcony door was also seeing a sheer curtain moving in the breeze and a potted plant swaying, and the "after sunset, motion turns on balcony light" rule had no end time. Fix: re-aim the sensor away from the curtain, and add a condition so the rule only runs until 11 pm unless the house is in Away mode, when the security rule takes over.
3. Every living room light at 100% after a 3 am power cut
Clue: all lights on together, at full brightness, the night of a storm. Cause: the light controllers were set to switch on when power returns, a setting that made sense during installation testing and was never changed. Fix: change the power-on behaviour to "previous state" for most lights and "off" for bedrooms, then test by switching off the MCB with lights off. Do smart homes work during power cuts covers what should happen when power returns.
4. Bedroom lights switch off while someone is reading
Clue: around 11:30 pm, only on some nights. Cause: a whole-house Night routine at 11:30 pm turned off all lights, including a bedroom where someone was still awake. Fix: rather than turning lights off, the routine was changed to switch the house to Night mode, dimming common areas and turning off only rooms that are empty; bedrooms are switched off by the Good Night button. This is the "people come first" rule described in how home automation resolves conflicts.
5. The dining lights change during a cricket match
Clue: only while the TV is loud; the voice assistant's history showed a command it thought it heard. Cause: a short scene name that sounded like commentary words. Fix: rename the scene to something longer and more distinct, and lower the speaker's sensitivity near the TV. How to name rooms, devices and scenes covers names that voice assistants get right.
Fixing the cause at the right level
Once the source is known, the fix should be as small as possible. Most surprising automations are useful rules with something missing, not bad rules.
| Problem | Small, correct fix | Fix to avoid |
|---|---|---|
| Rule runs at the wrong time | Change the time, days or sun offset; add an earliest or latest time | Deleting the schedule and losing the benefit |
| Rule runs when it should not | Add a condition: time window, house mode, light level, or "only if the room is empty" | Removing the sensor or disabling the rule permanently |
| Scene includes the wrong device | Edit the scene's contents or levels | Creating a second near-duplicate scene |
| Lights come on after power returns | Set power-on behaviour per light or circuit | Leaving lights off at the MCB |
| Voice assistant mishears | Rename scenes and devices; adjust or relocate the speaker | Unlinking the assistant entirely |
| Commands from an unknown app account or old integration | Remove that account or integration; change passwords | Ignoring it because the lights "only" flickered |
| One device misbehaves alone | Have the installer check the device, wiring and mesh route | Factory-resetting or re-pairing it yourself |
Change one thing, then wait
Make one change, note it, and watch for a few days. If you change three rules at once and the surprise stops, you will not know which change fixed it, and if a new surprise appears you will not know which change caused it. A short note of what was changed and when, in the handover document or a shared note, saves a lot of guessing later.
When it might be security
If the history shows commands from an app account you do not recognise, or remote changes at times when nobody in the family was using the app, treat it as a security issue: remove the account, change the app and Wi-Fi passwords, and tell your installer. This is rare in a local Zigbee system with a secured gateway, but it is the one case where you should not wait and watch. Is home automation safe from hacking covers the basics.
Designing a home that rarely surprises you
The best way to deal with unexpected automations is to design a system where every action has an obvious owner. A few habits make the difference:
- Keep a rule register. A simple list of every schedule, sensor rule and routine: what it does, when, and why. It belongs in the handover document and should be updated whenever something changes.
- One owner per load. Each light circuit or curtain should be controlled by a clear set of rules. If a schedule, a sensor and a voice routine all switch the same balcony light, conflicts are guaranteed.
- Prefer modes to blanket "all off" rules. A Night or Away mode that each room responds to sensibly causes fewer surprises than a timer that switches everything off at once. How home automation modes work explains the idea.
- Give every sensor rule an end. A timeout, a time window or a mode condition, so a sensor cannot keep a light on all night.
- Set power-on behaviour deliberately during commissioning, not just leave the factory default.
- Use notifications for big actions. A short alert when the house goes into Away mode or the main door unlocks remotely tells everyone what happened and why. How to design smart home notifications covers which alerts are worth having.
- Clean up after upgrades. When moving from Wi-Fi plugs or another system, remove the old apps, accounts and voice routines so they cannot keep sending commands.
- Review after a month. The first few weeks reveal which rules suit real life. How to fine-tune home automation after you move in is a good checklist for that review.
How Pert delivers it — a designed solution, not a DIY kit
Pert's keypads, tunable and dimmable lighting, motorised curtains and sensors and security devices work together as one Zigbee system through the Pert gateway. Because we design and install the whole system rather than selling a kit, every scene, schedule and sensor rule in your home is one we planned with you, written down and tested before handover. That makes surprises rare, and when one does happen it is quick to trace: we know which rules touch which lights and curtains, and we can adjust a time, add a condition or change power-on behaviour without disturbing the rest of the home. If something in your home ever acts in a way you did not expect, describe when it happened and what changed, and our support team will help you find the cause.
Planning home automation for a Hyderabad flat or villa? We will design the whole system — keypads, lighting, curtains, sensors and security — with clear, documented scenes and rules, so your home does what you expect and nothing you did not ask for. Request a consultation →
Comparing installers? Ask each one whether they provide a written list of every schedule and automation at handover, how power-on behaviour is set, and who you call when something behaves unexpectedly. Those questions sit alongside the wider checklist in best home automation companies in Hyderabad.
Frequently asked questions
Why do my smart lights turn on by themselves?
In almost every case something did tell them to: a schedule or sunset routine, a motion or door sensor rule, another family member using the app or a keypad, a voice assistant that misheard, or a power restore after which the light returned to its power-on state. Genuinely random behaviour from a healthy device is rare. Note the exact time, which lights changed and whether it repeats, then check the activity history if your system keeps one; the cause usually shows itself quickly.
Can a smart home be hacked into switching lights on and off?
It is possible in principle for any connected system, but it is a far less likely explanation than a forgotten schedule, a sensor rule or another person using the app. A local Zigbee system with a secured gateway, strong passwords and current firmware is a hard target. If the activity history shows a command from an app account you do not recognise, remove that account, change the password and tell your installer straight away.
Should I delete the automation that keeps misbehaving?
Usually not. Most surprising automations are useful rules with a missing condition, such as a motion rule that should only run after sunset, or a curtain schedule that should not run on Sundays. Adding the right condition or changing the time keeps the benefit and removes the surprise. Deleting rules one by one tends to leave the home less useful and does not always remove the real cause.
Why did all my lights come on after a power cut?
When power returns, each light controller follows its power-on behaviour: it may come back on, stay off, or return to its previous state, depending on how it is set. If they are set to come on, a 3 am power blip can light up the whole house. On most systems power-on behaviour can be chosen per light or circuit, for example previous state for most lights and off for bedrooms at night, so a power restore does not wake anyone.