Steve H.

Expert ★★★★★ 27,853 satisfied customers

Specialities: door and window sensor delay diagnostics, contact sensor state lag, magnet alignment checks, battery and signal-related sensor problems.

What to check first when a door sensor changes from open to closed too slowly: battery, magnet alignment, signal path, sensor wake-up behavior, and automation delay settings

Technician

Before we blame the door sensor itself, I want to separate two look-alike problems: the sensor may really be reporting late, or the automation may be adding the delay after the sensor reports correctly.

Let’s start with the safest checks first. I do not want you changing the sensor position, battery, and automation rules all at once.

When you open or close the door, do you see the state change slowly inside the app itself, or does the app update quickly and only the automation reacts late?

Customer

The app seems slow too. I open the door and it can take a few seconds before it shows open, then all my automations happen too late.

Technician

That is helpful, because it points toward an event delay before the automation even starts.

A few short questions so we do not chase the wrong cause:
1) Is this Zigbee, Z-Wave, Matter, Wi-Fi, or something you are not sure about?
2) Did this start suddenly, or has it always been a little slow?
3) Is it only one door sensor or several?

Customer

It is only this one door sensor. I think it is Zigbee. It used to be fast and now it feels delayed almost every time.

Technician

A sudden change on one sensor usually means we should check the simple physical causes before digging into the automation logic.

Let me ask this from the “what changed” angle: was there a recent battery change, hub move, router move, new metal object nearby, or did the sensor get bumped even a little?

Customer

I changed the battery maybe two weeks ago, and the door gets used a lot. I also put a shoe rack nearby recently.

Technician

Those are exactly the kinds of details that matter. A battery that is not making perfect contact, or a sensor and magnet that shifted slightly, can make the state change look lazy or inconsistent.

I also want to rule out a misleading issue: sometimes the sensor is fast, but the platform is waiting because of a built-in debounce, delay setting, or a slow route back to the hub.

When the state changes late, is it usually open, closed, or both directions?

Customer

It seems worse when the door opens. Closing sometimes looks normal, but opening can take a few seconds.

Technician

That uneven behavior is a good clue. If one direction is slower, I start thinking about magnet spacing, alignment, or the way the sensor is waking and reporting rather than a simple automation rule.

Trust moment: I do not want you peeling the sensor off the frame yet. First, just look at the gap. Does the magnet still line up cleanly with the sensor body when the door is closed, or is it slightly off-center now?

Customer

Looking at it now, the magnet is a little lower than the sensor. Not by a lot, but not perfectly lined up either.

Technician

That could absolutely be part of it, especially on a frequently used door. A sensor can still “work,” but if the magnet alignment is marginal, the state change may not look crisp every time.

Let’s keep going with safe checks only:
• Is the battery level shown as low, normal, or unknown?
• Is this door far from the hub or separated by thick walls, a metal door frame, or appliances?
• Did you notice the delay after the battery swap, or only later?

Customer

Battery says normal. The door is near the garage entry, and there is a metal frame. The delay might have started after the battery change, but I did not notice it right away.

Technician

A metal frame plus slightly off magnet alignment is a very believable combination. It can look like the automation is broken when the real issue is the sensor event arriving late or inconsistently.

This is common after small physical changes, but we should rule out risks before assuming the radio path is the only cause. Does your app show an event history or log where you can compare the exact door event time to the automation time?

Customer

Yes, I can see the event history. The automation runs right after the state changes, but the state itself is late.

Technician

Perfect. That takes the automation engine off the suspect list and puts the focus back on the sensor, magnet, or signal path.

One more thing I want to rule out: does this delay happen only after the door has been closed for a while, or even if you open-close-open it within a few seconds? That helps tell us whether the sensor may be sleeping or filtering repeated changes.

Customer

It is more noticeable after the door has been closed for a while. If I test it again right away, it sometimes reacts faster.

Technician

That is useful. It can point to a sensor wake-up pattern, a weak route, or a contact/magnet threshold that is right on the edge.

Another trust moment: do not rebuild all your automations around the delay yet. If the sensor path is the issue, changing every automation just hides the real problem and creates more cleanup later.

Customer

That is exactly what I was about to do, so I am glad I asked first.

Technician

Then the clean path is this: verify event history, inspect magnet alignment, note the battery timing, and think about whether anything near the door changed the signal environment.

If the sensor event is late but the automation fires immediately after, the automation is only the messenger. The better diagnosis is at the device level.

Customer

That makes sense. I was blaming the routine, but it sounds like the sensor event is what is really late.

Technician

Exactly. If you keep the checks small and controlled, you will know whether the real cause is alignment, battery contact, radio path, or a platform-side delay setting attached to the sensor state.

That is much safer than treating every broken automation as a separate problem.

Customer

Got it. I will check the event timing, look at the magnet alignment, and avoid changing all the automations for now.

Quick answer: the accepted fix

Accepted first approach when a door sensor changes state slowly and automations trigger too late:
• Check the event history first to confirm whether the delay starts at the sensor or inside the automation
• Inspect the sensor and magnet for small alignment drift, loose mounting, or a wider gap than before
• Note any recent battery change, door impact, nearby metal object, or hub placement change that may affect reporting
• Compare delayed “open” events versus delayed “closed” events, because one-sided lag often points to physical positioning or threshold issues
• Make one small change at a time and retest, instead of rewriting every automation to compensate for a slow sensor

FAQ

Sources

• Google Nest Help — Troubleshoot Google Home automations
• Home Assistant — Template integration (binary sensor delay_on / delay_off support)
• Aeotec Help Desk — Door / Window Sensor 7 user guide
• SmartThings Community — Door/Window Sensor delay

Matt ● replies in < 1 min

Technician Expert

⭐⭐⭐⭐⭐ Trusted by 27,000+ customers

Alex · Expert's Assistant

Start Chat

5 Tech Support Specialists are online right now.