iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
You can run a smart home without speaking to it. Automations can start when movement is detected, when a person remains in a room, when a door opens, or when a clock or solar event occurs. A practical setup uses a motion sensor for fast reactions, a presence sensor for people who sit still, and time or sunrise/sunset triggers for routines that should happen predictably.
The most reliable design follows Home Assistant’s trigger-condition-action model: an event starts the automation, optional conditions decide whether it is appropriate, and an action controls lights, plugs, climate equipment, blinds, scenes, or notifications. This approach removes voice commands from the critical path while preserving precise control over when devices respond.
How voice-free automation works
In an event-driven system, you do not tell a device what to do each time. You define a rule once, then let the home react to events. Home Assistant describes a trigger as the part of an automation that starts it when something specific happens, such as sunset, a door opening, or a button press.
Recommended Free Tools
Trigger, condition, action
- Trigger: The event that starts evaluation. Examples include motion changing to detected, a presence zone becoming occupied, the clock reaching 07:00, sunrise, sunset, a door opening, a temperature crossing a threshold, or a webhook arriving.
- Condition: A gate checked after the trigger. You can require that the room is dark, a door is closed, someone is home, or a quiet-hours schedule is not active.
- Action: The work performed when the trigger and every condition pass. Actions can turn lights on, set a thermostat, close blinds, activate a scene, switch a plug, or send a notification.
Separating these stages prevents common mistakes. A motion event can be valid but still unsuitable for turning on a light at noon, and a scheduled climate change may be inappropriate when a window is open. Conditions provide that second decision without requiring another voice command.
#1 Best Overall
- ZIGBEE STANDARD COMPATIBLE MOTION SENSOR: A Zigbee Hub is required. Compatible with Zigbee hubs and Echo devices with built-in Zigbee hubs, including Echo (4th Gen), Echo Plus (1st & 2nd Gen), Echo Studio, Echo Show 8 (3rd Gen), Echo Show 10 (2nd & 3rd Gen), Echo Hub, Eero 6, Eero Pro 6, Home Assistant, SmartThings (2015/2018), Aeotec, Hubitat, Homey Bridge, Homey Pro, and Third Reality Hub Gen2 Plus.
- CREATE ROUTINES: Using the Alexa app, create your own routines that are triggered when motion is detected. Customize Alexa messages like “Welcome Home” or “Motion Detected in Living Room” when motion is detected.
- SMART LIGHT CONTROL: If you have a smart light or smart plug connected to the Alexa service, you can create a routine in the Alexa app that will enable it to automatically turn on when motion is detected (and off when no motion is detected for a period of time that you specify).
- HASSLE-FREE SETUP: Installs in a few seconds. Just make sure device in paring mode and compatible Echo device automatically discovers it by saying “Alexa, discover devices”. Only for indoor use.
- GREAT RANGE AND LONG BATTERY LIFE : Capable of detecting motion up to 20 feet (6 meters) away. 2 AAA batteries can last for 2 years in typical usage.
Local processing and privacy
Home Assistant is designed to run locally on your own hardware. Local execution can reduce cloud dependence and keep sensor events inside your network, but the result depends on the device and integration path. A sensor may use local Matter, Thread, Zigbee, or another connection while a particular platform feature still depends on a cloud service. Check the exact entities and automations exposed by your hardware before assuming that every function is local.
Pick a trigger according to what you need to detect
Motion: detect movement quickly
Passive infrared (PIR) motion sensors detect changes caused by a moving warm body. They are well suited to hallways, bathrooms, stairs, and entryways where the desired behavior is immediate: movement starts the lights, and an inactivity timeout turns them off. A PIR sensor does not prove that a room is empty simply because no movement was detected during a short interval. Someone reading, showering behind a curtain, or sitting at a desk can remain in the room while generating little PIR activity.
Placement affects results. Aim the sensor across the path people take rather than directly toward the direction of travel, keep its field of view clear, and avoid pointing it at heat sources or strong sunlight. Battery models are easy to place but require battery maintenance; wired models avoid that task but need a suitable power route.
Presence: detect continued occupancy
Presence sensors, commonly based on millimetre-wave (mmWave) radar, are intended to continue detecting an occupant who is moving very little. That makes them useful for a desk, reading chair, living room, or bathroom where switching lights off merely because a person is still would be frustrating. Presence is an occupancy state, not just a movement event, so an automation can keep ventilation or lighting active while the state remains occupied.
Aqara describes its FP2 wired mmWave sensor as covering up to 40 m² (approximately 430 sq ft), detecting up to five people simultaneously, and supporting up to 30 configurable zones. It also includes a light sensor and can expose room or zone occupancy to Home Assistant, HomeKit, Alexa, and Google Home. Those are manufacturer specifications, not independent measurements; wall construction, furniture, mounting angle, firmware, and integration support can change real-world behavior.
Time and solar events: act predictably
Time triggers are deterministic. Home Assistant supports a specific time, repeating intervals, and time-pattern triggers, as well as sunrise and sunset events. They are appropriate when the routine should run whether or not a sensor notices movement: opening blinds in the morning, enabling a climate schedule, starting quiet hours, or turning exterior lights on around sunset.
Solar triggers follow the sun rather than a fixed clock. Sunset varies through the year, so a sunset rule is usually better than a hard-coded winter time for outdoor lighting. Add a condition such as “someone is home” if the action should not run in an empty house.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Rank #2
- Home Automation: The smart sensor can control GoveeLife intelligent devices in the same space and automatically turns them on or off when motion is detected. Ideal for areas such as bedrooms, hallways, and bathrooms where hands-free operation is ideal.
- Detection Range & Trigger Interval: Sensing distance 16-19ft (5-6m), sensing angle ±60°. The device operates only within the detection range. The adjustable trigger interval (60-180 seconds) prevents unresponsiveness caused by false triggers.
- Maximum compatibility: The GoveeLife Smart Motion Sensor supports most devices in the Govee Home app. You must own at least one Govee Home WiFi product to deploy your distributed gateway. Connect your devices to enhance your experience.
- Anti-false alarm function: This device has a trigger detection interval function, which can be adjusted from 60 to 180 seconds (the minimum trigger interval is 60 seconds). This function can ignore your inadvertent movement and make your device run according to your wishes.
- Distributed Gateway: Featuring GoveeLife dual-mode devices (sold separately) that support both Wi-Fi and Bluetooth. Only Govee Home WiFi products can interact with the H5121. Maintains an effective distance of 55m/180ft between devices and sensor. (only support 2.4G WiFi)
Other device and platform events
Door and window openings, temperature thresholds, button presses, NFC tags, app events, and webhooks can all start automations. These events are useful when the home needs a deliberate signal rather than inferred occupancy. For example, a door contact can start an entry scene immediately, while a temperature trigger can start a fan only after a threshold is crossed.
| Trigger type | What it detects | Good uses | Main limitation |
|---|---|---|---|
| PIR motion | Movement | Fast lights in halls, stairs, and bathrooms | May not detect a still occupant; requires an off timeout |
| mmWave presence | Continued occupancy, including low movement | Desk, living room, reading area, ventilation | More placement and calibration work; capabilities vary by integration |
| Time or time pattern | Clock time or repeating interval | Morning routines, quiet hours, scheduled climate changes | Does not know whether anyone is home unless you add a condition |
| Sunrise or sunset | Solar event | Exterior lighting and seasonal schedules | Needs an occupancy or presence condition when an empty home should stay inactive |
| Door, temperature, button, tag, or webhook | A device or platform event | Entry scenes, thresholds, deliberate controls | Each event requires compatible hardware and an exposed entity |
Build a motion-triggered hallway or bathroom routine
Plan the behavior before installing hardware
- Choose the light or scene that should turn on.
- Set a brightness or color appropriate to the time of day; bright white light may be useful in the morning, while a dim warm scene is less disruptive overnight.
- Choose an inactivity period. A short period suits a passageway; a longer period is safer in a bathroom.
- Decide what should prevent activation, such as daylight, an open door, or an away mode.
A Philips Hue indoor motion sensor is one example of this category. Philips Hue documents it as battery powered, requiring a Hue Bridge, and supporting different lighting behavior by time of day. The bridge requirement matters: the sensor and lights need that hub path even if another platform is used for broader automation.
Configure it in Home Assistant
- Open Settings → Automations & scenes and choose Create automation.
- For the trigger, select the motion sensor’s state entity and set it to the detected or “on” state.
- Add a numeric illuminance condition if the lights should run only below a chosen brightness threshold.
- Add any occupancy, door, or time condition that should block the action.
- Choose the light or scene action and set the desired brightness.
- Add an off action that runs after the sensor has remained clear for the selected duration. A “no motion for” period is preferable to an immediate off command.
- Save, then test once in daylight and once in darkness. Watch the automation trace to confirm which trigger, condition, and action executed.
Example automation logic
trigger:
- platform: state
entity_id: binary_sensor.hall_motion
to: 'on'
condition:
- condition: numeric_state
entity_id: sensor.hall_illuminance
below: 80
action:
- service: light.turn_on
target:
entity_id: light.hall
data:
brightness_pct: 55
- wait_for_trigger:
- platform: state
entity_id: binary_sensor.hall_motion
to: 'off'
for: '00:02:00'
- service: light.turn_off
target:
entity_id: light.hall
mode: restartThe entity names and service names in this example are illustrative; select the entities exposed by your own integration. The important pattern is motion as the start event, illuminance as a guard, and a delayed off action after inactivity.
Use presence for rooms where people sit still
Position and zone the sensor
Mount a presence sensor where its radar view includes the seating or work area but does not look through large obstructions unnecessarily. Divide a larger room into zones when you need different behavior: a desk zone can control a task light, while a sofa zone can control ambient lighting. With the FP2, Aqara advertises up to 30 configurable zones and up to five people detected at once within the stated coverage area.
Free tools Windows power users keep installed
One-click scans. No signup required.
Use the built-in light sensor, where exposed by the integration, to avoid turning lights on when daylight is sufficient. Treat the advertised 40 m² coverage as a design limit rather than a guarantee for every floor plan. Metal furniture, walls, mirrors, and mounting height can affect the usable detection area.
Configure an occupied-state automation
- Pair the sensor through the supported integration and confirm that the room or zone occupancy entities appear.
- Create an automation with the occupancy entity changing to occupied as the trigger.
- Add a light-level condition if lighting should run only when the room is dim.
- Turn on the light, fan, or scene for that zone.
- Create a separate automation for the occupancy entity changing to clear, optionally requiring it to remain clear for a delay such as five minutes before switching equipment off.
- Test with one person seated, two people moving in different zones, and an empty room. Confirm that the platform reports the zones you intend to use.
Why presence and motion are often combined
A PIR sensor can provide an inexpensive, fast arrival signal, while mmWave presence keeps the room active after movement stops. One rule can turn on a light immediately from PIR; a second rule can keep it on while presence remains detected. The off rule should require both no motion and no presence, otherwise a quiet occupant may be left in the dark.
Schedule routines with time, intervals, and solar events
Fixed-time morning routine
A fixed-time trigger is appropriate for a repeatable morning sequence. At a chosen time, open blinds, set a comfortable climate target, or activate a low-brightness scene. Add a presence condition if the routine should run only when somebody is home. If different household members follow different schedules, create separate routines rather than embedding a long chain of exceptions in one automation.
Rank #3
- [NOTES] Requires Aqara Zigbee 3.0 hub (Not compatible with other Zigbee hubs). Requires a secured 2.4 GHz Wi-Fi for Hub M2/M1S/E1/M1S Gen2 and Camera Hub G2H Pro/G2H, and 2.4/5 GHz Wi-Fi for Camera Hub G3.(Wired connection via Ethernet RJ45 for Hub M2 is also supported.) The Motion Sensor P1 is compatible with Aqara Home, HomeKit, Alexa, IFTTT, Home Assistant. (*Note: No light sensitivity function in HomeKit and Alexa; Please update hub firmware for optimal use.)
- [5-Year Battery Life] The Zigbee motion sensor boasts an impressive five-year battery life, maintaining reliable performance even in low temperatures or with lightning-fast detection timeouts. The Aqara Motion Sensor P1 dimensions are 1.46"D x 2.17"W x 2.76"H.
- [Configurable Detection Timeout] Easily adjust the Aqara motion sensor timeout without any hardware modifications. Through the Aqara Home app, configure the timeout from 1 to 200 seconds to save energy or capture every movement promptly. Zigbee2MQTT and comparable third-party USB dongles are not officially supported by Aqara. Full product functionality may be limited or unavailable.
- [Adjustable Viewing Angle & Detection Distance] Experience a wide detection range with a 170° field of view up to 4 meters and 150° up to 7 meters. The flexible 360° stand makes it easy to adjust the angle, so the motion sensor only triggers when needed. Choose from three sensitivity levels (high, medium, low) to fine-tune detection distance based on your setup. For a stable connection, ensure the motion sensor is placed within 393 inches (10 meters) of the Aqara Zigbee Hub.
- [Alert System and Home Automations] Set up the Aqara Home Alert System or integrate it with HomeKit and other supported systems for continuous monitoring and local sound, light alarms, and cloud notifications upon motion detection. The Zigbee motion detector seamlessly integrates into smart home automations. Easily configure "IF" and "THEN" smart automations, such as turning on lights via Aqara Smart Wall Switch or powering devices with the Aqara Smart Plug.
Sunrise and sunset lighting
Use a sunrise trigger for a gentle morning scene and a sunset trigger for exterior or entry lighting. A condition for household presence avoids lighting an empty home, while a door or lock condition can make an entry scene more specific. Because sunrise and sunset shift daily, these triggers remain aligned with seasonal daylight without editing the automation each month.
Repeating intervals and time patterns
Time-pattern triggers can perform recurring checks, such as evaluating indoor temperature every 15 minutes or reminding you to ventilate after a long period. Keep the interval long enough that the action is not repeatedly sent to the same device. If the action changes a climate target or starts a motor, add a state condition so the command is issued only when a change is actually needed.
Quiet hours
Represent quiet hours with a schedule helper or an equivalent time condition. During that period, let motion or presence continue to control essential low-level lighting, but suppress notifications, loud scenes, or bright lights. This is an example of a condition changing the action without disabling the trigger itself.
Combine triggers and conditions to avoid unwanted actions
Most useful automations have more than one signal. A motion trigger plus a low-illuminance condition prevents daytime lights. A presence trigger plus an “at home” condition prevents activity in a room that should be inactive while the household is away. A sunset trigger plus a closed-blinds condition avoids sending a motor command when the blinds are already closed.
Use separate on and off logic
Turning something on and turning it off usually need different evidence. Motion can turn a hallway light on immediately, but the off action should wait for a clear state. Presence can keep a lamp on while a person remains seated, while the off action should wait for the zone to be clear for a grace period. Keeping these decisions in separate automations makes each one easier to test.
Choose a restart strategy
If new motion arrives while an off timer is counting down, the automation should restart or cancel the pending off action. Otherwise the light may switch off while someone is still walking. Home Assistant’s automation mode setting controls how overlapping runs are handled; select the mode that matches the device and the behavior you want, then test repeated triggers.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Interoperability: Matter, Thread, and platform entities
Matter and Thread can make a device available across supported ecosystems, but they do not guarantee identical features everywhere. A platform may expose basic motion while omitting a manufacturer’s zone, light-level, or multi-person entity. Before buying, verify the exact trigger entities available in the platform that will run your automations.
Rank #4
- 【Advanced Motion Detection】Completely hands-free and smart operation of your connected lights. The switch automatically turns lights on when motion is detected and turns off after a preset time. Ideal for areas such as bedrooms, hallways and restrooms where hands-free operation is ideal.
- 【Daylight Detection】Smart ambient light detection will sense daylight and prevent lights from turning on during the day.
- 【Smart Mode & Away Mode】Set different light triggers based on your routine for effortless control. Automatically turns devices on and off at different times to give the appearance that someone is home.
- 【Works w/ All Bulb Types】600W Incandescent/Halogen, 300W CFL/MLV/ELV
- 【Voice & App Control】Manage your device with voice commands via Amazon Alexa, Google Assistant, or Samsung SmartThings. Hands-free operation of your lights from anywhere through the free Kasa app.
Aqara’s Motion and Light Sensor P2 is described as a native Matter-over-Thread device. Aqara lists compatibility with Apple Home, Google Home, Alexa, SmartThings, Home Assistant, Homey, and Aqara Home, while Home Assistant lists the P2 among Aqara Matter products and describes local connectivity. The practical question is not just whether the sensor pairs; it is whether your chosen controller receives motion, illuminance, occupancy, and battery entities in the form your rules require.
| Example device | Connection and power | Documented capabilities | Important dependency or qualification |
|---|---|---|---|
| Aqara Presence Sensor FP2 | Wired mmWave | Up to 40 m² coverage, up to five people, up to 30 zones, built-in light sensor | Manufacturer claims; local automation and exposed entities depend on the supported configuration |
| Aqara Motion and Light Sensor P2 | Matter over Thread | Motion and light sensing; listed for Apple Home, Google Home, Alexa, SmartThings, Home Assistant, Homey, and Aqara Home | Requires a compatible Thread/Matter path; capabilities can differ by platform |
| Philips Hue Motion Sensor | Battery powered | Indoor motion detection and time-of-day lighting behavior | Requires a Hue Bridge |
Reliability, privacy, power, and maintenance
Local versus cloud execution
Local control can keep an automation working during an internet outage and reduce the amount of occupancy data sent to a remote service. It is not automatic: check whether pairing, entity updates, and the final action all use the local path. A cloud-only integration may continue to function normally but will depend on internet access and the provider’s service.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Power choices
Battery sensors simplify installation but add a maintenance task. Record the battery type and keep a spare available. Wired presence sensors avoid battery replacement but need a permanent power position and a cable route. For a rental or temporary setup, a battery PIR may be easier; for a fixed desk or room installation, wired presence can be more convenient if a socket is nearby.
Latency and false activations
Wireless path, hub processing, and cloud round trips all affect response time. Test the complete path rather than judging a sensor in isolation. If lights activate when nobody is present, narrow the detection zone, move the sensor away from a window or heat source, or add a second condition. If lights fail to activate, check battery level, network attachment, entity availability, and the automation trace.
Firmware, geography, and integration changes
Product capabilities and platform support can change with firmware, region, certification, or integration version. The specifications and compatibility statements above reflect official documentation available on October 18, 2026; confirm current support for your country and software version before purchasing. Advertised coverage, person counts, and zone totals are not independent accuracy, latency, reliability, or battery-life tests.
Troubleshoot the most common failures
The light turns off while someone is present
- Replace a short PIR timeout with a longer clear-state delay.
- Add a presence sensor in the seating or work zone.
- Ensure the off rule requires both no motion and no presence.
- Check whether the sensor’s field of view is blocked by furniture.
The light turns on in daylight
- Add an illuminance condition and verify that the sensor reports a current value.
- Check whether the platform uses lux, a binary “bright/dark” state, or a different entity.
- Allow for sensor placement: a shaded sensor may report darkness even when the room is bright.
The scheduled routine runs at the wrong time
- Confirm the controller’s time zone and daylight-saving configuration.
- Use a sunrise or sunset trigger when the intent follows daylight rather than a fixed clock time.
- Review conditions that may be blocking the action, such as an away state or open door.
A Matter or Thread sensor pairs but exposes too little data
- Inspect the entities created by the integration, not just the device name.
- Check that a compatible Thread border router and Matter controller are online.
- Compare the platform’s exposed entities with the capabilities promised by the manufacturer.
- Update firmware and integration software only after recording the current automation configuration.
Choose a starting design
| Your goal | Best first trigger | Power and privacy priorities | Setup effort |
|---|---|---|---|
| Lights that react as soon as someone walks through | PIR motion with a clear-state timeout | Battery is simplest; local processing improves outage resilience | Low |
| Lights or ventilation that must stay on while someone sits still | mmWave presence, optionally paired with PIR | Wired power is convenient for a fixed location; verify local entity support | Medium to high |
| Morning, evening, or quiet-hour routines | Fixed time, interval, sunrise, or sunset | No occupancy sensor required, but add a home/away condition when appropriate | Low |
| One device usable across several ecosystems | Matter over Thread, after checking exposed entities | Requires compatible Thread and Matter infrastructure | Medium |
| Maximum control over personal data | Locally processed sensor and controller path | Keep automations on local hardware and audit cloud dependencies | Medium |
A practical rollout checklist
- Start with one room and one outcome, such as a hallway light.
- Identify the exact trigger entity your controller receives.
- Add one condition, usually illuminance or home/away state, before adding complex exceptions.
- Implement a delayed off action separately from the on action.
- Test movement, still occupancy, daylight, darkness, an empty room, and an internet outage if local resilience matters.
- Inspect automation traces and sensor history for a full day.
- Only then expand to additional rooms, zones, schedules, and scenes.
Which approach should you choose?
Use PIR when the requirement is “react when somebody moves,” presence sensing when the requirement is “stay active while somebody remains,” and time or solar triggers when the requirement is “run at a predictable moment.” Conditions such as illuminance, door state, and household presence turn those raw events into rules that behave appropriately. For many homes, the best progression is a simple local PIR automation first, followed by mmWave presence in rooms where still occupants cause nuisance shutoffs, and scheduled or solar routines for predictable background tasks.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
