Host reboot required

The Host reboot required condition passes while the system Home Assistant runs on needs a reboot, for example after an update of Home Assistant OS. This is only available on Home Assistant OS.

Use it to run a routine only while a reboot is pending, like a reminder at a moment that suits you. To hold off a routine while a reboot is pending instead, wrap this condition in a Not condition.

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 Host reboot required.
5. Select Save.

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 homeassistant.host_reboot_required. It has no options:

condition: homeassistant.host_reboot_required

This passes while a reboot is pending.

Good to know

• This condition only passes on Home Assistant OS. On other installation types, Home Assistant does not manage the host, so it never needs a reboot.
• The reboot stays pending until the host reboots, also when you restart Home Assistant in the meantime.
• To act the moment a reboot becomes pending, use the Host reboot required trigger.

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: weekly reboot reminder

Every Sunday morning, send a reminder, but only while the host needs a reboot.

• Trigger: Time
  • At time: 10:00:00 AM
  • Weekdays: Sunday
• Condition: Host reboot required
• Action: Send a notification message
  • Target: My Device (notify.my_device)

alias: "Weekly reboot reminder"
triggers:
  - trigger: time
    at: "10:00:00"
    weekday: sun
conditions:
  - condition: homeassistant.host_reboot_required
actions:
  - action: notify.send_message
    target:
      entity_id: notify.my_device
    data:
      message: "The Home Assistant host still needs a reboot."

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:

• Restart required: Tests if Home Assistant needs a restart to apply installed updates or changed settings.