2026.10.4
Home ▸ Template functions

Human-readable time remaining: time_until

The time_until template function returns a human-readable string describing how much time remains until a given datetimeA value representing a specific moment in time, including the date, time, and time zone. For example, 2026-04-05 14:30:00+00:00. Used for timestamps, scheduling, and time-based calculations. in the future. Give it a future datetime, and it returns something like “3 hours” or “2 days 6 hours” instead of a raw number of seconds.

This is useful whenever you want to display a countdown or remaining time in a natural format. For example, showing how long until the next alarm goes off, displaying “arrives in 45 minutes” for a delivery, or reporting how much time is left on a timer. The function only works with datetimes in the future. For past datetimes, use time_since instead. You can control the level of detail with the optional precision parameter, which determines how many time components (years, months, days, hours, minutes, seconds) to include.

Usage

Here’s how to use this template function. Copy any example and adjust it to your setup.

TemplateA template is an automation definition that can include variables for the action or data from the trigger values. This allows automations to generate dynamic actions. [Learn more] 
{{ time_until(as_datetime(states("sensor.next_alarm"))) }}
Result (stringA piece of text, like a name, message, or entity ID. In templates, wrap strings in quotes, like "living_room" or "lights are on".) 
6 hours

Function signature

The signature is a technical summary of this template function. It shows the name of the function, the values (called parameters) it accepts, and what type of data each parameter expects (for example, a piece of text or a number).

Function parameters that have a = with a value after them are optional. If you leave them out, the default value shown is used automatically.

Function parameters without a = are usually required. A few optional parameters have no default value, so the signature shows them without a = as well. To check whether a parameter is required, look at the parameter list below the signature. Each parameter is marked as Required or Optional.

The most common optional parameter without a default value is default. The default parameter sets the value a function returns when the function can’t produce a result, for example, when float gets text that isn’t a number. If you leave out default, there is no fallback value, so most functions raise an error and the template fails. The parameter list of each function says what happens. If you set default, the function returns your value instead.

How to read a signature

Here is the signature of the round filter as an example:

round(
    value: Any,
    precision: int = 0,
    method: str = "common",
    default: Any,
) -> float | int | Any
  • round is the name of the function.
  • Between the parentheses are the parameters. Each parameter has a name, followed by a colon and the type of value the parameter expects. The type only tells you what kind of value to pass. For default: Any, you pass a value of any type, such as 0 or "unknown", not the word Any.
  • = 0 and = "common" are default values. You can leave out precision and method, and round uses these default values.
  • default has no =, but the parameter list marks default as optional. If you leave out default and round gets a value that isn’t a number, round raises an error.
  • -> shows the type of value the function returns.
  • Inside a signature, | means “or”. This function returns a decimal number, a whole number, or the value you passed as default.

round is a filter, so the first parameter, value, is the value before the |. For example, {{ 3.14159 | round(2) }} returns 3.14.

The types you’ll see most often:

  • str: text, such as "hello"
  • int: a whole number, such as 5
  • float: a decimal number, such as 3.14
  • bool: true or false
  • list: a list of values, such as [1, 2, 3]. list[str] is a list of texts.
  • dict: a set of keys and values, such as {"name": "Kitchen"}
  • datetime and timedelta: a date and time, and a duration. For details, refer to Dates and times.
  • None: no value
  • Any: any type of value

Some signatures use special forms:

  • *args means you can pass any number of values, separated by commas. For example, average(1, 2, 3).
  • value | name(...) means the function is a filter. The value before the | is passed to the filter as its first parameter. Some filter signatures, like the round example, show this value as the first parameter between the parentheses instead.
time_until(
    value: datetime,
    precision: int = 1,
) -> str

Function parameters

The following parameters can be provided to this function.

value datetime Required

A datetime object representing a point in the future. The function calculates the time remaining between now and this datetime.

precision integer (Optional, default: 1)

The number of time components to include in the output. A precision of 1 might return “6 hours”, while a precision of 2 might return “6 hours 15 minutes”. Higher precision gives more detail. Use 0 to include every time component that isn’t zero.

Controlling precision

By default, time_until returns only the largest time component. Increase the precision to include more detail.

TemplateA template is an automation definition that can include variables for the action or data from the trigger values. This allows automations to generate dynamic actions. [Learn more] 
{{ time_until(as_datetime(states("sensor.next_alarm")), 1) }}
Result (stringA piece of text, like a name, message, or entity ID. In templates, wrap strings in quotes, like "living_room" or "lights are on".) 
6 hours
TemplateA template is an automation definition that can include variables for the action or data from the trigger values. This allows automations to generate dynamic actions. [Learn more] 
{{ time_until(as_datetime(states("sensor.next_alarm")), 3) }}
Result (stringA piece of text, like a name, message, or entity ID. In templates, wrap strings in quotes, like "living_room" or "lights are on".) 
6 hours 15 minutes 30 seconds

Good to know

  • Only works with datetimes in the future. A datetime in the past is returned unchanged, without an error. For past datetimes, use time_since instead.
  • The last unit shown is rounded to the nearest whole number. All other units are cut off. For example, 2 hours 45 minutes gives "3 hours" with a precision of 1.
  • Because of this rounding, the result doesn’t carry over to the next unit. For example, 59 minutes 40 seconds gives "60 minutes", not "1 hour".
  • Units that are zero are skipped and don’t count toward the precision. For example, 2 hours and 15 seconds gives "2 hours 15 seconds" with a precision of 2.
  • Durations shorter than half a second return "0 seconds".
  • If the input isn’t a datetime, it’s returned unchanged. This includes none, which as_datetime returns for states like unknown.
  • Datetimes without a time zone are accepted. They’re treated as your local time.

Try it yourself

Ready to test this? Open Settings > Tools > Template, paste the example into the Template editor, and watch the result update on the right. Edit the values to see how the function adapts to your own entitiesAn 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].

More examples

Real scenarios where this function comes up in automations and templates. Copy any example and adapt it to your setup.

Show time until next alarm

Display a countdown to the next alarm on your dashboard.

TemplateA template is an automation definition that can include variables for the action or data from the trigger values. This allows automations to generate dynamic actions. [Learn more] 
{{ "Alarm in " ~ time_until(as_datetime(states("sensor.next_alarm"))) }}
Result (stringA piece of text, like a name, message, or entity ID. In templates, wrap strings in quotes, like "living_room" or "lights are on".) 
Alarm in 6 hours

Countdown to a scheduled event

Show how long until a calendar event starts, with more detail.

TemplateA template is an automation definition that can include variables for the action or data from the trigger values. This allows automations to generate dynamic actions. [Learn more] 
{% set event_time = as_datetime(states("sensor.next_appointment")) %}
Starts in {{ time_until(event_time, 2) }}
Result (stringA piece of text, like a name, message, or entity ID. In templates, wrap strings in quotes, like "living_room" or "lights are on".) 
Starts in 2 hours 30 minutes

Time remaining in an automation condition

Only run the rest of an automationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] if a scheduled event is less than 1 hour away. time_until returns text, so you can’t compare its result with a duration. Instead, subtract now from the event time and compare the result with a timedelta.

AutomationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] 
condition:
  - condition: template
    value_template: >
      {{
        as_datetime(states("sensor.next_event")) - now()
        < timedelta(hours=1)
      }}

Still stuck?

The Home Assistant community is quick to help: join Discord for real-time chat, post on the community forum with your template and expected result, or share on our subreddit /r/homeassistant.

Tip

AI assistants like ChatGPT or Claude can also explain or fix templates when you describe what you want in plain language.

Related template functions

These functions work well alongside this one: