SwitchBot Motion or Contact Sensor Not Triggering Automations
- Automation linked to wrong trigger condition
- Hub Mini or Hub 2 required but not set up for cloud automations
- Sensor battery critically low
Problem Description
Your SwitchBot motion or contact sensor records trigger events in the app activity log but the linked automation does not execute. Or the sensor stops detecting events entirely. When the sensor logs events but automations do not fire, the failure is almost always in the automation condition logic or a cloud sync delay — not the sensor hardware itself.
Symptoms
- Sensor shows events in log but automation does not run
- Motion sensor does not detect movement
- Contact sensor shows wrong open/closed state
- Automation triggers with long delay
- Sensor goes offline and stops reporting
- Scene runs sometimes but not consistently
Recognize these? Here's what usually causes it.
Common Causes
- Automation linked to wrong trigger condition
- Hub Mini or Hub 2 required but not set up for cloud automations
- Sensor battery critically low
- Bluetooth range exceeded between sensor and hub
- Motion sensor detection angle or distance not covering the area
- Contact sensor magnet shifted or too far from sensor
Most fixes happen in the first 3 steps.
{"Motion sensors have a 30-second cooldown between detections by default","Contact sensor adhesive may damage paint on door frames when removed"}
Tools & Requirements
These tools will help you complete this fix.
Isopropyl alcohol for remounting
ForPro Professional Collection 99% Isopropyl Alcohol...
CR2 or AAA batteries depending on model
Philips CR2032 3V Lithium Button Cell Batteries, 50 ...
As an Amazon Associate we earn from qualifying purchases.
Step-by-Step Solution
Confirm sensor battery and live status
Replace battery if low and verify the sensor reports live events in SwitchBot app. Dead or sleeping sensors cannot fire automations reliably. This step verifies power integrity, because unstable voltage can mimic software failure and cause intermittent resets. After completing it, boot behavior and command response should remain stable through multiple test cycles.
Check hub proximity and Bluetooth path
Ensure sensor is within stable range of Hub Mini/Hub 2 and not blocked by metal or thick walls. Weak path causes missed trigger delivery. This step stabilizes the connectivity path so the device can complete authentication and maintain a clean control session. After completing it, the device should stay online in the app and respond to commands without repeated reconnect prompts.
Validate automation conditions and time windows
Review conditions, delays, and do-not-run windows in each automation. Misconfigured logic often looks like sensor failure. This step narrows fault scope before deeper hardware replacement decisions, which keeps troubleshooting efficient and evidence-based. After completing it, you should have a clear pass/fail signal that tells you whether to continue or escalate.
Run manual trigger test for each automation
Open/close contact or create motion near sensor and confirm event appears in history. History visibility helps isolate sensor vs rule issues. This step narrows fault scope before deeper hardware replacement decisions, which keeps troubleshooting efficient and evidence-based. After completing it, you should have a clear pass/fail signal that tells you whether to continue or escalate.
Re-pair sensor and rebuild failing automations
If triggers still do not execute, remove and re-add the sensor, then recreate affected automations. Corrupted bindings can survive simple edits. This step stabilizes the connectivity path so the device can complete authentication and maintain a clean control session. After completing it, the device should stay online in the app and respond to commands without repeated reconnect prompts.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If the sensor still misses events after repositioning, check whether a scheduled 'home' or 'away' mode is overriding the sensitivity setting silently.
{"Cloud automations require a Hub — Bluetooth-only scenes only work when phone is nearby","Replace sensor batteries annually even if they still show charge","Test each automation after creating it to verify it triggers correctly"}
Home Assistant issues that only appear after restart are a well-known quirk — triggers that require prior state history simply can't fire until that history rebuilds.
- Automation linked to wrong trigger condition
- Hub Mini or Hub 2 required but not set
- Sensor battery critically low
- Bluetooth range exceeded between sensor and hub
- Motion sensor detection angle or distance not covering the
Before you go — try one of these (they fix most cases).
Most popular upgrades chosen by SwitchBot Motion Sensor / Contact Sensor owners.
SwitchBot RGBIC Neon Rope Light, 5M Matter-Certified Neon...
SwitchBot Smart Lock Pro, Keyless Entry Door Lock, Smart ...
SwitchBot Bluetooth Temperature and Humidity Monitor Mete...
As an Amazon Associate we earn from qualifying purchases.
Official Manufacturer Manual
If you need the complete manufacturer documentation for advanced setup, wiring diagrams, or detailed specifications, you can download the official manual below. The manual includes full technical instructions directly from the manufacturer and may help if your issue requires deeper troubleshooting.
Download the Official SwitchBot Motion Sensor / Contact Sensor ManualSource: switch-bot.com
Need More Help? SwitchBot Support
Note: The contact information below connects you directly to SwitchBot's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.
