Why your smart motion and door sensors keep triggering false alarms

A sensor that cries wolf gets ignored, and an ignored sensor is worse than no sensor at all. The good news is that false alarms almost always come from a short, familiar list: the motion sensor is pointed at something warm and moving, a pet is walking through its view, a door contact has drifted out of alignment, a battery is on the way out, or the automation is firing on a single flicker with nothing to steady it. Work through them in order and you can usually turn a jumpy sensor into a calm, dependable one in a few minutes, and without buying anything in most cases. Here's how I'd chase it down.

Quick version if you just want the punchline:

1. Point motion sensors away from windows, vents, heaters and anything else that moves or changes temperature.
2. If you have pets, use a pet-immune sensor, or mount a standard one higher and angle it down.
3. Re-seat door and window contacts so both halves sit close and square, with no gap and no rattle.
4. Check the battery. A weak one throws phantom triggers before it dies completely.
5. Add a little debounce in your automation so one brief blip doesn't set the whole thing off.

The rest of this walks through why each one matters, so you can tell which is actually biting you rather than guessing and hoping.

First check: what is the motion sensor actually looking at

A standard motion sensor is a PIR, a passive infrared detector, and it reacts to moving heat. It does not see people as such, it sees warm things that move across its field of view. That is why placement is nearly always the culprit for false motion alerts. Aim it at a sunny window and passing clouds or a swaying curtain in the light can set it off. Point it at a heating or cooling vent, a fireplace, or a bar heater and the moving warm air reads as a person walking past. Even a hot appliance kicking on in an open kitchen can do it.

The fix: look along the sensor's line of sight and clear those things out of it. Turn it so windows, vents and heat sources sit outside its cone, mount it in a corner covering the room rather than a doorway that frames a window, and keep it off exterior walls that bake in the afternoon sun. Most false motion alarms simply disappear once the sensor stops staring at something warm and moving.

Pets, and why pet-immune sensors earn their keep

If you have a cat or a dog, a plain motion sensor will treat them exactly like a burglar, because to a PIR they are warm and they move. A pet-immune sensor is built for this. It is tuned to ignore movement below a certain size and weight down low, so an animal crossing the floor stays quiet while a standing person still trips it. If your pets have the run of the house, this is the cleanest answer.

There is a no-cost trick too. Mounting a standard sensor higher up and angling it down the wall lifts the bottom of its detection zone off the floor, so a low animal passes underneath the beam. It helps, but it is fussier to get right than a proper pet-immune unit, and a determined cat that likes to climb will still find a way to set it off. If false triggers only ever happen when the house is empty except for the pet, this is your answer.

Door and window contacts that drift out of line

A door or window sensor is a contact sensor: two halves, one with a magnet, that report an open the moment they move apart. So anything that lets them separate, even slightly, reads as the door opening. A loose fit, a gap wider than a few millimetres, a door that rattles in the wind, or the magnet half slowly slipping out of alignment will all fire a false open, often in the small hours when a breeze picks up.

The fix: check that both halves sit close together and square when the door or window is shut, with the alignment marks lined up if the sensor has them. Re-stick or re-screw the magnet so the gap is as small as the sensor allows. If the door itself moves in a draught, a firmer catch, a draught seal, or a small spacer to close the gap will settle it. Once the two halves stay put, the phantom opens stop.

Low battery, the quiet troublemaker

A sensor that used to behave and has suddenly gone jumpy is very often running low on battery. As the cell weakens the sensor sends weaker, less reliable signals, drops off the network and rejoins, and along the way can report triggers and tamper alerts that never happened. It is one of the most common causes of a sensor that false alarms out of nowhere, and one of the easiest to miss because nothing looks physically wrong.

Check the battery level in the app before you change anything else. If it is getting low, replace it and watch for a day or two before assuming the sensor is faulty. On mains-powered or hardwired sensors the equivalent is confirming they are getting steady power, since a marginal supply behaves much the same way as a dying battery.

Weak WiFi or a crowded network

Some sensors, particularly WiFi cameras with built-in motion, misbehave when their connection is poor. A sensor sitting at the edge of coverage drops off and reconnects, and those reconnections can surface as spurious motion or offline-then-online noise that looks like a false trigger. A network crammed with too many devices makes it worse, because the sensor has to fight for airtime and its heartbeat gets lost.

If your false alarms cluster on the sensors furthest from the router, coverage is the likely cause. Getting more WiFi near those sensors, a mesh node or an access point closer to them, gives each one a strong, steady link so it stops dropping and re-announcing itself. Battery Zigbee and Z-Wave sensors sidestep this entirely, which is one reason they are a better fit for a house full of sensors than WiFi ones.

Debounce: stop one flicker from firing everything

Even a well-placed, healthy sensor will occasionally send a single stray reading, a brief electrical blip or a momentary glitch. If your automation acts on that instantly, one flicker rings the alarm. Debounce is the fix: a short delay or filter that makes the automation wait and confirm before it acts.

In practice that means adding a few seconds of delay, or requiring the sensor to report the same state twice in a row, before the automation does anything. A momentary spike no longer survives the wait, so it gets filtered out, while a genuine event that lasts more than an instant still comes through cleanly. In Home Assistant this is a small tweak to the automation, and it is one of the most effective ways to quieten a sensor that is basically fine but a touch twitchy. It is the software equivalent of not jumping at every creak.

Tune sensitivity, but do not blind the sensor

Most sensors and hubs let you turn the sensitivity down, and it is tempting to crank it to the floor the moment one goes off. Do it gently. Turn sensitivity down too far and the sensor misses the very thing you put it there to catch, which is worse than the odd false alarm. Nudge it down a step, live with it for a few days, and only drop it again if you still get false triggers. Fix the placement, pets, alignment and battery first, and you will usually find you barely need to touch the sensitivity at all.

Want it just done?

Tuning sensors so they fire on what matters and stay quiet the rest of the time is fiddly to chase alone and quick for us, and getting placement, alignment and automation settings right together is exactly the kind of job we do every week. Tell us which sensors are playing up and we'll get them calm and dependable, remotely across Australia for the app and automation side, and in person where we cover for the mounting and coverage work.