Merge dictionaries: combine

The combine template function merges multiple dictionaries into a single dictionary. When the same key appears in more than one dictionary, the value from the last dictionary wins. This lets you build up complex data structures by combining smaller pieces.

This is useful when you need to assemble data from multiple sources into a single dictionary. For example, you might want to combine default settings with overrides, merge attributes from several 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] into one payload, or build up a notification data dictionary from multiple parts. The optional recursive parameter enables deep merging, where nested dictionaries are merged rather than replaced, which is helpful when working with deeply structured data.

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]
{{ combine({"a": 1}, {"b": 2}, {"c": 3}) }}
Result (dict)
{'a': 1, 'b': 2, 'c': 3}

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.
combine(
    *args: dict,
    recursive: bool = False,
) -> dict

Function parameters

The following parameters can be provided to this function.

args map Required

One or more dictionaries to merge. When keys overlap, later dictionaries take precedence.

recursive boolean (Optional, default: false)

If true, nested dictionaries are merged recursively instead of being replaced. Defaults to false.

Key overlap behavior

When the same key appears in multiple dictionaries, the value from the last dictionary wins.

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]
{{ combine({"color": "red", "size": "large"}, {"color": "blue"}) }}
Result (dict)
{'color': 'blue', 'size': 'large'}

Recursive merging

With recursive=true, nested dictionaries are merged together instead of one replacing the other.

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]
{{
  combine(
    {"settings": {"brightness": 100, "color": "warm"}},
    {"settings": {"color": "cool", "mode": "auto"}},
    recursive=true
  )
}}
Result (dict)
{'settings': {'brightness': 100, 'color': 'cool', 'mode': 'auto'}}

Good to know

  • When the same key appears in multiple dictionaries, the value from the later dictionary wins.
  • Without recursive=true, nested dictionaries are replaced outright, not merged.
  • The original dictionaries are not modified; a new dictionary is returned.

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.

Build a notification payload

Combine default notification settings with dynamic content.

ActionAn action makes Home Assistant do something, for example, turn on a light, send a notification, or activate a scene. Automations and scripts run a list of actions. [Learn more]
action:
  - action: notify.mobile
    data: >
      {{
        combine(
          {"title": "Home Assistant", "priority": "normal"},
          {"message": "Front door is " ~ states("binary_sensor.front_door")}
        )
      }}

Merge settings with overrides

Start with default settings and override specific values.

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 defaults = {"mode": "auto", "brightness": 128, "color_temp": 300} %}
{% set overrides = {"brightness": 255} %}
{{ combine(defaults, overrides) }}
Result (dict)
{'mode': 'auto', 'brightness': 255, 'color_temp': 300}

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: