Update is not available

The Update is not available condition passes when one or more targeted update entities are currently up to date. Use it when an automation should continue only if a device or service does not have an update waiting.

This condition is useful for clean-up automations, status checks, and routines that should run only after everything you target is already up to date.

Using this condition from the user interface

If you prefer building automations visually, Home Assistant walks you through this condition step by step. You pick what to check, tweak a few options, and save. No YAML knowledge required.

To use this condition in an automation:

1. Go to Settings > Automations & scenes.
2. Open an existing automation, or select Create automation > Create new automation.
3. In the And if section, select Add condition.
4. From the search box, search for and select Update is not available.
5. Select what you want to check. Under By target (see Targets), select the update entities you want to check, or a label that you assigned to them. If you select a device, area, or floor instead, update entities marked as configuration or diagnostic entities are not included. This is common for device firmware updates. For details, refer to Entities that are not part of a target.
6. Under Condition passes if (see Behavior), pick Any or All.
7. Under For at least, enter how long the update must have stayed up to date before the condition passes.
8. Select Save.

Options in the UI

Using this condition in YAML

If you work directly in YAML, or you want to know exactly what Home Assistant does under the hood, this section has the technical reference. It lists the field names you use in YAML, their types, and which ones are required. For how an automation is built in YAML, refer to Automations in YAML.

In YAML, put the settings that are specific to this condition under options. Keep target, if the condition uses one, and general settings such as alias and enabled at the top level, next to condition.

In YAML, refer to this condition as update.is_not_available. A basic example looks like this:

condition: update.is_not_available
target:
  entity_id: update.office_router_firmware

This passes when update.office_router_firmware is currently up to date.

Options in YAML

YAML sometimes provides additional options for more complex use cases that are not available through the UI.

Targets of the condition

This condition requires a target. The target is the object that Home Assistant will check. You can point the condition at a single entityAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more], a device, an area, a floor, or a label, and Home Assistant will evaluate every matching update entity behind that target.

• Entity: one specific update entity, such as update.living_room.
• Device: every update entity that belongs to a device.
• Area: every update entity in a room or area.
• Floor: every update entity on a floor.
• Label: every update entity that shares a label.

You can also select different target types in one condition. For example, you can add a specific entity and an area as targets in the same condition to check both of them at once.

To learn which entities Home Assistant includes for a device, area, floor, or label, and how it handles several entities, refer to Automation targets.

Behavior with multiple targets

When you target more than one entity (or select an area, floor, or label that contains several), the Condition passes if option controls how the results combine:

• Any (default): the condition passes if at least one of the targeted entities matches. For example, if you check three smoke sensors and only one of them detects smoke, the condition still passes. This is useful for questions like “is there smoke anywhere in the house?”
• All: the condition passes only when every targeted entity matches. For example, if you check the same three smoke sensors, the condition passes only once all three report cleared. This is useful for “is the entire house safe now?” checks, so your automation does not send an all-clear while one room still has a reading.

Good to know

• This condition checks update entities whose state is off, which means no update is available.
• Update entities that are unavailable or unknown are skipped. With Any, the condition passes if at least one of the other targeted update entities matches. With All, it passes if all the other targeted update entities match. If all targeted update entities are unavailable or unknown, All passes and Any fails.
• If you use for, each matching update must stay up to date for the full time you set.

Try it yourself

Ready to test this? Go to Settings > Automations & scenes, open an automation, and add this condition. Trigger the automation with and without the condition met, and watch whether it continues or stops.

More examples

Real scenarios where this condition gates an automation. Copy any example and adapt it to your setup. In the visual editor, select the UI options listed in the example or paste the YAML code.

Automation: turn off a reminder light after the update has been installed

If you use a light as a reminder for pending updates, this automation turns it off once the update is no longer available.

• Trigger: Time: 21:30
• Condition: Update is not available
  • Target: Guest room speaker update
• Action: Turn off light

alias: "Turn off a reminder light after the update has been installed"
triggers:
  - trigger: time
    at: "21:30:00"
conditions:
  - condition: update.is_not_available
    target:
      entity_id: update.guest_room_speaker_firmware
actions:
  - action: light.turn_off
    target:
      entity_id: light.hallway_lamp

Automation: run a script only after all selected devices are up to date

If you have created a script for a routine that should run only after updates are done, this automation can wait until every targeted update entity is back to up to date. The Upstairs updates label is assigned to the update entities themselves.

• Trigger: Time: 22:00
• Condition: Update is not available
  • Target: Upstairs updates label
  • Condition passes if: All
• Action: Run script

alias: "Run a script only after all selected devices are up to date"
triggers:
  - trigger: time
    at: "22:00:00"
conditions:
  - condition: update.is_not_available
    target:
      label_id: upstairs_updates
    options:
      behavior: all
actions:
  - action: script.evening_shutdown

Still stuck?

To find out why the condition didn’t pass, check it live in the automation editor, and look at the trace of the run. For details, refer to Testing automations. For common problems and their solutions, refer to Troubleshooting automations.

If that doesn’t help, the Home Assistant community is quick to help: join Discord for real-time chat, post on the community forum with the condition you’re using and what you expected to happen, or share on our subreddit /r/homeassistant.

Related conditions

Explore related conditions:

• Update is available: Tests if one or more updates are available.