What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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
A Home Assistant automation that stops firing is usually behaving exactly as written, given what its sensor reported at that moment. The usual culprits are a sensor that went unknown or unavailable, a trigger that only listens for one specific change, and a condition that quietly fails when its input is unusable. The practical fix is not to distrust sensors across the board. It is to diagnose which of these happened, then design the automation for missing data instead of assuming every reading is live.
Unknown and unavailable are different problems
Home Assistant uses two states that look similar in dashboards but mean different things. The official documentation on working with states defines the difference, and it matters for where you look next.
| State | What Home Assistant means | Where to look first |
|---|---|---|
unknown |
The entity exists, but its value is not known. | The entity’s raw state and History, to see whether it ever received a value after startup or a change. |
unavailable |
The entity cannot currently be reached, for example because a device is offline or an integration failed to load. | Device power and connectivity, the integration’s status, and Settings > System > Logs for warnings that mention the entity. |
Treat these as separate diagnoses. An unavailable sensor is a connection or integration question. An unknown sensor is a question about whether the source has produced a value at all. Rewriting the automation before you know which one you have usually hides the real problem.
Free tools Windows power users keep installed
One-click scans. No signup required.
Why a recovery often does not fire your automation
Triggers respond to a moment or a change. They do not keep checking whether a condition is still true. The automation triggers documentation describes this behavior, and it has a specific consequence for sensors that drop out.
#1 Best Overall
- [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.
The From constraint excludes recovery
A state trigger with from: off only fires when the entity moves from off to the target state. If a motion sensor goes unavailable, then comes back as on, that is an unavailable-to-on transition. A trigger constrained to from: off does not match it, even though the sensor now reports the state you care about. The official troubleshooting automations page calls out this case.
Remove the from constraint only when the automation should respond regardless of the previous state. If the goal is to act whenever a condition is true at a given moment, use a trigger for the change and a condition for the state at that moment.
A state trigger with no From or To also responds to attributes
A state trigger that has neither from nor to can fire on attribute changes, not only on changes to the state itself. If attribute updates are causing extra runs, set the intended state explicitly, or use the any-state option that ignores attribute changes.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesRank #2
- [Precise AI-Powered Presence Sensor] Powered by advanced AI, PIR, and 60GHz mmWave radar, the FP300 accurately detects human presence even when you’re still. Its adaptive AI learning continuously optimizes sensitivity to reduce false triggers, ensuring lights and devices stay on even when you’re lounging on the couch, and off when they need to be.
- [Broad Compatibility] Supports Matter over Thread and Zigbee for seamless integration with major ecosystems. Works with Apple Home, Home Assistant, Alexa, Google Home, SmartThings, and Homey via Matter for flexible, reliable automation. (* For third-party Matter ecosystems, a corresponding Thread Border Router and Matter Controller are required. * For Aqara, a Zigbee 3.0 or Matter hub like M2/M3/G410/etc, except G2H, with the latest firmware is needed.)
- [5-in-1 Multi-Sensor] Combines 60GHz mmWave, PIR, light, temperature, and humidity sensors into one compact device. This all-in-one design enables precise detection of presence and environmental conditions, helping automate lighting, climate control, and security systems for a smarter and more energy-efficient home.
- [Long Battery Life & Energy Efficiency] Powered by two replaceable CR2450 batteries, the FP300 offers up to 3 years of battery life in Zigbee mode or 2 years in Thread mode. Optional sensor deactivation helps conserve energy, ensuring consistent and long-lasting performance. What's Included: FP300 Multi-Sensor × 1, Sticker × 1, User Manual × 1
- [Wire-Free & Flexible Installation] Completely wireless with a multi-axis adjustable mount for easy wall, ceiling, or corner setup. No wiring required—relocate anytime for optimal detection and coverage. Featuring a 120° field of view and up to 6 m (20 ft) of detection range, the FP300 can effectively monitor various room layouts. Its minimalist design blends seamlessly into any modern interior, delivering powerful functionality without visual clutter.
A numeric state trigger fires on a crossing, not a level
A numeric state trigger reacts when a value crosses a threshold. It does not repeat while the value stays above or below it. If you need repeated checks, the documented route is a time-pattern trigger combined with a condition, as described in the troubleshooting guide.
Diagnose the failure in order
Work through these steps in sequence. Each one narrows the cause before you change anything.
- Open the automation trace. If no trace exists at the time the automation should have run, the trigger never fired. If a trace exists, read the condition results and note the step where the run ended: before the run started, inside a condition, or inside an action.
- Check the raw state. Open Settings > Tools > States and inspect the entity. A friendly label such as “Open” or “Detected” may correspond to a raw state such as
on. State triggers compare the raw value, so a mismatch between label and raw state will cause a silent miss. - Read the History around the failure. Identify whether the entity became
unavailableorunknown, changed briefly, or bounced around a threshold. Home Assistant keeps state changes for 10 days by default, so check History soon after a failure. Short-term statistics are saved every 5 minutes and long-term statistics every hour, so a brief dropout may not appear in statistics graphs. Use History for that. - If the entity is unavailable, check its source. Confirm device power and connectivity, the integration, and Settings > System > Logs for warnings. If the automation’s action reports an unavailable target, trace that separately. The sensor that triggered the run and the device the action controls can fail independently.
- Review the trigger semantics. Check any
fromconstraint against the transitions in History. Confirm the trigger type matches the behavior you want, using the trigger rules above. - Check the other documented causes. See the list further down before deciding the sensor is the problem.
Guard calculations and decisions against unusable values
A sensor that goes unknown or unavailable for a moment can break templates and conditions that were written assuming a number is always present. The common template patterns page puts it plainly: a sensor that goes unknown or unavailable for a moment can wreck your automations.
Rank #3
- 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.
Check that the value is usable
The has_value function returns true only when an entity is neither unknown nor unavailable. Use it before reading the value, for example {{ has_value('sensor.hallway_temperature') }} in a condition or a template branch, so the automation can take a deliberate path when the reading is missing.
Numeric state conditions fail on unusable values
A numeric state condition does not pass when the measured entity, or a threshold entity it compares against, is unknown or unavailable. This is usually the behavior you want, because it prevents the action from running on no data. It also means the automation silently does nothing, which is why the trace is the first place to look.
Hold the last value, with a freshness check
The documented hold-last-value pattern can keep downstream calculations stable through short dropouts. The held value, though, is not a live reading during the outage. Use it for smoothing, not for decisions that depend on the current state. Where an action would be unsafe on old information, pair the held value with a freshness or availability check. Without that check, a held value can hide a real change for as long as the sensor stays down.
Rank #4
- ZIGBEE STANDARD COMPATIBLE MOTION SENSOR: Works with compatible Zigbee hubs or Echo devices with Zigbee hub built-in, such as Echo (4th Gen), Echo Plus (1st Gen and 2nd Gen), Echo Studio, Eero 6, Eero Pro 6, Home Assistant, SmartThings 2015/2018, Aeotec, Hubitat, Homey Bridge, Homey Pro, Third reality Hub and Third Reality Smart Speaker. Zigbee Hub Required.
- 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.
Filter bouncing sensors with a For at least timer
If a sensor flickers around a threshold or between states, a trigger can fire repeatedly on noise. A For at least duration requires the entity to stay in the trigger state for a set time. Home Assistant resets that timer when the entity leaves the trigger state, and starts over when it returns, so a sensor that keeps bouncing may never satisfy the duration.
Look at History before choosing a duration. Pick a value based on the real behavior of the sensor and on the cost of delaying the response. A longer duration suppresses more noise, but it also delays legitimate responses. A short duration responds quickly, but may still fire on each bounce.
Other causes that look like sensor failures
Several documented causes produce the same symptom, an automation that did not run, even when the sensor was fine:
Best Value
- ZIGBEE STANDARD COMPATIBLE MOTION SENSOR: Works with compatible Zigbee hubs or Echo devices with Zigbee hub built-in, such as Echo (4th Gen), Echo Plus (1st Gen and 2nd Gen), Echo Studio, Eero 6, Eero Pro 6, Home Assistant, SmartThings 2015/2018, Aeotec, Hubitat, Homey Bridge, Homey Pro, Third reality Hub and Third Reality Smart Speaker. Zigbee Hub Required.
- 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.
- A raw-state mismatch between the label you see and the value the trigger compares.
- A renamed entity ID, which leaves the trigger pointing at an entity that no longer updates.
- A disabled automation, or one whose conditions were not met.
- Overlapping triggers or single-run mode that prevents a new run while an earlier one is still active.
- A specific device trigger that the integration does not offer. Home Assistant recommends an entity trigger where the device trigger is not available.
- A replaced device ID after re-pairing or re-adding hardware.
- A breaking change after an update, which is worth checking when the failure started at a specific time.
Choose how an automation should handle missing readings
There is no universal strategy. The right choice depends on how quickly the automation must react, how long stale data stays acceptable, and what happens if the action runs on old information. The comparison below sets out the trade-offs.
| Question | Stop the action when the reading is missing | Use a held last valid value |
|---|---|---|
| Behavior during an outage | The condition or template fails, and the action does not run. | The automation continues using the last valid value. |
| Main risk | Missed responses. The automation can fail silently. | Acting on a value that no longer reflects the room or device. |
| Best fit | Actions where running on old data would be unsafe or wrong. | Calculations and smoothing where brief dropouts should not disrupt output. |
| Extra check to add | An unavailable or unknown check that logs or notifies you. | A freshness or availability check before any decision depends on the value. |
| Recovery handling | Trigger on the recovery transition, without a restrictive from, when the action should resume. |
Confirm the live reading has returned before relying on it again. |
When the sensor itself is the problem
If the diagnosis points to a physical sensor that repeatedly drops offline, is unsuitable for its location, or reports values that cannot be trusted, replacing it may be the right step. Verify the integration and the radio protocol before buying any replacement. Compatibility depends on your hub and integrations, and the official documentation does not establish compatibility for any particular model. Confirm it against Home Assistant’s integration pages first.
Before replacing hardware, confirm the failure in the trace, the raw state, and History. Many failures that look like a bad sensor turn out to be a trigger or condition that never saw the recovery.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →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.
