Profiler: Dump log objects

Use this action to investigate objects in memory. When Profiler: Start log objects highlights the growth of a collection of objects in memory, this action helps you investigate it. The representation of each object that matches the given Type is logged.

This action requires an administrator account.

Using this action from the user interface

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

To dump log objects from an automation or a script:

1. Go to Settings > Automations & scenes.
2. Open an existing automation or script, or select Create automation > Create new automation.
3. If you’re setting up a new automation, add a trigger in the When section. Scripts don’t need a trigger. They run when something else calls them.
4. In the Then do section, select Add action.
5. Search for and select Profiler: Dump log objects.
6. Set the Type of object to dump to the log.
7. Select Save.

Options in the UI

Using this action 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.

In YAML, refer to this action as profiler.dump_log_objects. A basic example looks like this:

action: profiler.dump_log_objects
data:
  type: RenderInfo

This logs the representation of every RenderInfo object in memory.

Options in YAML

This action does not support targets.

Good to know

This action is useful for investigating the state of objects in memory. For example, if your system has templates that render too frequently, you can find which templates are the source of the problem by dumping the Template objects:

action: profiler.dump_log_objects
data:
  type: Template

Try it yourself

Ready to test this? Open Developer tools > Actions, search for this action, fill in the fields, and select Perform action. You see what happens on your actual 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] without writing a line of YAML.

Still stuck?

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

Related actions

These actions work well alongside this one:

• Profiler: Start log objects: Starts logging the growth of objects in memory.

• Profiler: Stop log objects: Stops logging the growth of objects in memory.

• Profiler: Start log object sources: Starts logging the growth of objects in memory and tries to find their source.