Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

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

Use a watchdog that measures the age of each entity’s reports, not an automation that waits for a state-change event. Choose the timestamp that matches what “fresh” means for that entity, check it on a schedule, and combine the check with native availability or MQTT expiry when those features exist.

Why a state-change trigger misses a silent entity

A state-triggered automation runs because Home Assistant received an event. If a temperature sensor stops communicating, no new event arrives, so that automation has nothing to evaluate. Silence must therefore be detected by a clock-based check: run an evaluation periodically or use an integration feature that expires the entity after a defined interval.

There is no universal timeout. A mains-powered meter that reports every few seconds can be considered stale after a short gap; a battery sensor that normally reports every 15 minutes needs a much longer allowance. Set the threshold above the device’s normal reporting cadence and include enough margin for sleep cycles, wireless retries and your acceptable detection delay.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Choose the timestamp that represents freshness

Home Assistant stores several timestamps on a state object. They answer different questions, so selecting the wrong one is the most common cause of false alarms.

#1 Best Overall
Sale
Compressed Air Duster,130000RPM Super Power Cordless Air Duster,Rechargeable Brushless Blower,3 Gear Adjustable Blower with LED Light,Dust Remover for Computer/House/Outdoor/Car
  • Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
  • With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
  • Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
  • Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
  • Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
Property Changes when Use it when Typical false-positive risk
last_changed The state value changes. A changing value is the signal you need, such as a motion state changing from off to on. High for quiet sensors. A healthy sensor can report the same value repeatedly without changing this timestamp.
last_updated The state value or one of its attributes changes. Attribute changes count as meaningful activity, but identical full-state reports do not. Possible when the integration receives reports but neither the state nor attributes change.
last_reported The integration writes the state again, even when state and attributes are identical. The integration emits regular reports and you want to know whether Home Assistant received them. It records Home Assistant’s receipt/write time, not proof that a device-origin timestamp is current or that the physical sensor is measuring correctly.

Home Assistant’s state-object documentation describes last_reported as the date and time the entity last reported its state. The same documentation notes that some integrations, including MQTT, write state only when something changes unless force-update behavior is enabled. Establish the integration’s actual behavior before choosing a clock.

A timestamp also reflects Home Assistant’s own write or receipt. If a gateway republishes an old value, the entity can look recently updated even though the underlying device has not produced a new measurement. For high-assurance monitoring, use a device-provided sequence number, measurement timestamp or explicit online status when the integration exposes one.

Inventory the entities and their normal cadence

Start with a deliberately selected list rather than every entity in the installation. Lights, helpers, scenes and calculated template entities do not necessarily have an independent reporting cadence. A watchdog should cover entities for which silence has operational meaning: leak sensors, freezer probes, power meters, security contacts, presence beacons or gateway status sensors.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Rank #2
EVEO® Screen Cleaner Spray Kit (Streak-Free) TV Screen Cleaner for Smart TV, Lcd, LEd, Oled | Computer Screen Cleaner Spray and Wipe Microfiber Cloth - TV, Monitor, Laptop, iPad, Car - 6.7oz 1 Pack
  • Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
  • Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
  • Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
  • Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
  • Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth

Record the behavior that matters

  • Find the normal interval between reports while the device is healthy.
  • Determine whether identical values still create state writes.
  • Check whether the integration exposes available/unavailable status, an availability topic or an expiry setting.
  • Decide how much detection delay is acceptable. A five-minute evaluation interval can add almost five minutes after the threshold is crossed.
  • Document startup behavior. Note whether a retained message, cached gateway value or restored state can appear immediately after a restart.

Use a threshold per device class when cadences differ. For example, a five-minute allowance may be reasonable for a sensor expected every minute, while a 45-minute allowance may be safer for a battery device expected every 15 minutes. These are illustrative settings, not universal recommendations.

Build a periodic stale-entity check

The basic pattern is a time-pattern automation that calculates the age of each selected entity and alerts only when the age exceeds its configured limit. The following example checks every five minutes. Replace the entity IDs and limits with values established for your devices.

alias: Watch selected entities for stale reports
triggers:
  - trigger: time_pattern
    minutes: '/5'
conditions: []
actions:
  - variables:
      watched:
        - entity_id: sensor.kitchen_temperature
          max_age: 900
        - entity_id: sensor.freezer_temperature
          max_age: 1800
        - entity_id: sensor.water_leak_status
          max_age: 600
  - variables:
      stale_entities: >-
        {% set ns = namespace(items=[]) %}
        {% for item in watched %}
          {% set entity = states[item.entity_id] %}
          {% if entity is not none and entity.last_reported is not none %}
            {% set age = as_timestamp(now()) - as_timestamp(entity.last_reported) %}
            {% if age > item.max_age %}
              {% set ns.items = ns.items + [item.entity_id ~ ' (' ~ (age | int) ~ ' seconds)'] %}
            {% endif %}
          {% endif %}
        {% endfor %}
        {{ ns.items | join(', ') }}
  - condition: template
    value_template: '{{ stale_entities | length > 0 }}'
  - action: notify.mobile_app_your_phone
    data:
      title: Home Assistant entity may be stale
      message: 'No recent report from: {{ stale_entities }}'
mode: single

This example deliberately uses last_reported. If the integration does not write identical reports, substitute last_updated or last_changed according to the meaning you established. A missing timestamp is not silently treated as healthy; add an explicit startup policy for entities that have not reported since boot.

Rank #3
Sale
BladeHawks RGB Gaming Mouse Pad Extra Large Extended 31.5x12 Inch-Black | LED mouse pad with 14 lighting modes, covers keyboard & mouse, anti-slip rubber base, waterproof surface, USB powered
  • 【Large size】:Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
  • 【LED backlight mouse pad】:Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
  • 【Anti-slip rubber base】:Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
  • 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
  • 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.

Prevent notification floods

The scheduled automation will notify on every run while an entity remains stale. Add a notification latch, a cooldown or a transition check. One practical design is an input_boolean per monitored group: send the first alert and turn the helper on; suppress later alerts while it is on; clear it when every entity is fresh again. A separate recovery automation can announce that reporting resumed. Keep the stale list in the alert so the message identifies the affected entity and its measured age.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Use an explicit startup grace period

After Home Assistant restarts, integrations may still be initializing. A watchdog that starts immediately can report every device before connections are ready. Add a condition that requires Home Assistant uptime to exceed a chosen grace period, or delay enabling the automation until startup is complete. Treat an entity with no timestamp after that grace period as a separate “never reported” condition rather than assigning it an arbitrary age.

Alternative: a time-aware template trigger

A template can express the stale condition, but it must be evaluated as time passes. Referencing now() in a template does not make an automation run continuously by itself. Pair the calculation with a time-pattern trigger, or use a template trigger whose referenced entities and time-based evaluation are configured so it is re-evaluated at the required interval.

Rank #4
Sale
Vaydeer Wrist Rest for Keyboard and Mouse, Computer Ergonomic Wrist Support Pad, Soft Memory Foam Arm Cushion for Desk, Palm Hand Office Laptop Typing
  • 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
  • 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
  • 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
  • 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
  • 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.

For a small, fixed set, a periodic trigger with a template condition is easier to audit. For a larger inventory, create a template sensor that publishes a list or count of stale entities and let a separate automation react when that result changes. Keep the entity list curated and give each entity its own cadence; one global timeout will either miss failures or create noise.

Use native availability and MQTT expiry when available

A freshness watchdog complements, rather than replaces, an integration’s online/offline signal. An entity that is explicitly unavailable should be handled immediately, while an entity that still has a value but has not reported recently needs the age check.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

MQTT expiry

MQTT sensors can be configured with an availability topic and an expiry interval. expire_after is expressed in seconds; when no new state message arrives within that period, Home Assistant marks the sensor unavailable. Availability payloads can map explicit device messages such as online and offline to the entity’s availability state.

Best Value
Sale
Under Desk Cable Management Tray No Drill, Metal Mesh Cable Management Under Desk with Clamp Mount, 2 Hole Cable Tray with Wire Management and Cord Organizer for Home Office Standing Desk
  • 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
  • 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
  • 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
  • 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
  • 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
mqtt:
  sensor:
    - name: Freezer temperature
      state_topic: house/freezer/temperature
      expire_after: 1800
      availability_topic: house/freezer/status
      payload_available: online
      payload_not_available: offline

Set expire_after above the normal publish interval, with margin for expected delays. Expiry catches a missing MQTT state message without a separate polling automation, but it does not validate the measurement itself. Keep the periodic age check if you need to detect a stale value that remains available because an intermediary is replaying or republishing data.

Retained-message and restart caveat

MQTT retained messages can be delivered when Home Assistant starts or reloads the entity. That delivery updates Home Assistant’s state even when the payload was produced earlier. Therefore, a new Home Assistant timestamp after startup is not automatically proof of a fresh device measurement. Test the retained-message policy, consider including a device-generated timestamp or sequence number, and decide whether startup should suppress alerts until a non-retained report arrives.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

What homeassistant.update_entity can and cannot do

The homeassistant.update_entity action requests an update from entities and integrations that support that operation. It does not change how often an entity updates on its own, and it cannot force a sleeping battery device, failed gateway or silent MQTT publisher to produce a new value.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
action:
  - action: homeassistant.update_entity
    target:
      entity_id:
        - sensor.kitchen_temperature

Use this action as a diagnostic or as a deliberate refresh before another task, not as the watchdog itself. If the request succeeds, observe which timestamp changes and whether the integration actually obtained a new measurement. A manual refresh that leaves the age unchanged is evidence to investigate the integration or transport path.

Choose an approach by failure mode

Situation Best first mechanism Why Important limitation
Device publishes at a known cadence and repeats identical values Periodic check of last_reported Every accepted report counts as activity. The timestamp is Home Assistant’s receipt/write time.
Integration writes only when a value or attribute changes Periodic check of last_updated, or a device availability signal Matches the events the integration actually records. A constant but healthy value can look stale if no availability signal exists.
Only value transitions matter last_changed with a threshold suited to expected transitions Detects absence of meaningful state changes. Quiet periods are indistinguishable from failure without another signal.
MQTT device has regular messages expire_after plus availability topics, backed by an age check when needed Native expiry can mark the entity unavailable automatically. Retained or replayed payloads can make old data appear newly received.
Large, mixed inventory Curated watch list with per-entity limits and grouped notifications Prevents helpers and irregular entities from generating noise. Requires maintaining the inventory as devices change.

Diagnose a stale alert before changing the timeout

  1. Check the selected timestamp. In Developer Tools, inspect the entity and compare last_changed, last_updated and last_reported. Confirm that the one used by the automation changes when a normal report arrives.
  2. Verify the expected cadence. Watch the entity during a healthy period. If reports are event-driven rather than periodic, a fixed timeout may be the wrong test.
  3. Separate unavailable from stale. An explicit unavailable state points to availability, authentication, transport or integration failure. A normal value with an old timestamp points to missing reports or replayed data.
  4. Inspect the transport. For MQTT, check the state topic, availability topic, publish interval, broker logs and retained flag. For other integrations, inspect the integration’s diagnostics and connection status.
  5. Test a supported manual refresh. Run homeassistant.update_entity and observe whether any timestamp changes. Do not assume a successful action means the physical device responded.
  6. Check restart timing. Note whether the alert occurred during startup, after a gateway restart or immediately after a retained MQTT message. Apply a startup grace period or device-origin freshness field where appropriate.
  7. Review notification state. If alerts repeat every evaluation, add a latch or cooldown. If recovery is not announced, add a separate fresh-again transition.

Common design mistakes

  • Using only a state trigger: it cannot observe an event that never arrives.
  • Using last_changed for a stable measurement: unchanged temperature or power values can be healthy.
  • Applying one timeout to every entity: reporting intervals vary by integration, device type and power mode.
  • Assuming unavailable means stale: an entity can retain a plausible but old value without becoming unavailable.
  • Treating an update request as a polling scheduler: the action does not alter the integration’s normal cadence.
  • Trusting a post-restart timestamp blindly: restored state and retained MQTT payloads can be old.
  • Watching every entity automatically: helpers, calculated sensors and event-driven entities need different semantics.

A practical rollout checklist

  • List only entities for which missed reports have a clear consequence.
  • Measure each entity’s normal report interval and identify whether identical reports are written.
  • Select last_changed, last_updated or last_reported deliberately.
  • Set a per-entity threshold above normal cadence and document the expected detection delay.
  • Run the evaluation on a schedule; do not rely on a state-change trigger alone.
  • Use native availability or MQTT expire_after where supported.
  • Define startup grace and “never reported” behavior.
  • Test a real disconnect, not only a changed sensor value.
  • Suppress repeat notifications and provide a recovery message.
  • Revisit thresholds after firmware, broker, network or battery changes.

What a reliable alert tells you

A useful notification names the entity, the timestamp used, the configured limit and the measured age. “Freezer temperature has not reported for 1,247 seconds; limit 1,800 seconds” is actionable because it distinguishes a timing condition from a generic offline message. Include whether the current state is unavailable, the last known value and the time Home Assistant last wrote it when that context is safe to disclose.

Monitoring freshness is not the same as validating correctness. A sensor can report regularly while being miscalibrated, stuck at a plausible value, or disconnected from the physical process it measures. Pair the freshness watchdog with domain-specific checks—such as impossible ranges, a device heartbeat counter or an independent sensor—when the consequence of a missed or false reading is serious.

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.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.