Get the type of a value: typeof
The typeof template function returns the type name of a value as a string. It tells you what kind of data you are working with, such as str, int, float, list, dict, or bool. This is the Python class name of the value.
This is primarily useful for debugging templatesA 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]. When a template does not behave as expected, it is often because a value is a different type than you assumed. For example, you might think a sensor value is a number, but it is actually a string. Or an attribute you expected to be a list is actually None. Using typeof lets you inspect the actual types at runtime so you can figure out what is going on and write the correct conversion or comparison.
Usage
Here’s how to use this template function. Copy any example and adjust it to your setup.
{{ typeof(42) }}
int
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
-
roundis 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 as0or"unknown", not the wordAny. -
= 0and= "common"are default values. You can leave outprecisionandmethod, androunduses these default values. -
defaulthas no=, but the parameter list marksdefaultas optional. If you leave outdefaultandroundgets a value that isn’t a number,roundraises 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 asdefault.
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 as5 -
float: a decimal number, such as3.14 -
bool:trueorfalse -
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"} -
datetimeandtimedelta: 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:
-
*argsmeans 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 theroundexample, show this value as the first parameter between the parentheses instead.
typeof(
value: Any,
) -> str
Function parameters
The following parameters can be provided to this function.
Common type names
Here are the type names you will encounter most often:
-
strfor text (for example,helloor the result ofstates("...")) -
intfor whole numbers (for example,42orstates("...") | int) -
floatfor decimal numbers (for example,21.5orstates("...") | float) -
boolfortrueorfalse -
listfor a list of values (for example,[1, 2, 3]) -
dictfor a mapping (for example,{"a": 1}) -
NoneTypeforNone
Good to know
- Results are Python class names like
str,int, orNoneType. They are not Jinja or YAML type names. - All entity states are
str, regardless of what they look like. A temperature sensor returning21.5still reports asstruntil you convert it. - Intended mainly for debugging. In production templates, prefer type tests like
is numberor conversion functions likefloat.
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.
Debug a sensor state type
Check what type a state value is. Since all entity states are strings, this confirms the need for type conversion before math.
State type: {{ states("sensor.temperature") | typeof }}
After float: {{ (states("sensor.temperature") | float) | typeof }}
State type: str
After float: float
Check the type of an attribute
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] attributes can be various types. Use typeof to inspect what you are working with.
{{ state_attr("climate.living_room", "hvac_modes") | typeof }}
list
Conditional logic based on type
Handle different types differently in a 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 val = state_attr("sensor.data", "reading") %}
{% if val | typeof == "list" %}
Got {{ val | length }} items
{% else %}
Single value: {{ val }}
{% endif %}
Got 3 items
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.
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:
-
Test if value is numeric: is_number - Tests whether a value can be converted to a finite number.
-
Convert to float: float - Converts a value to a floating-point number, with an optional default if conversion fails.
-
Convert to integer: int - Converts a value to an integer, with an optional default if conversion fails.
-
Convert to boolean: bool - Converts a value to a boolean (true/false), with an optional default if conversion fails.