Wtf? Template output exceeded maximum size of 262144 characters

hello,

pls help!
i use the following tempate in “Tools” to export all entities i have for external analyses.

but now i can´t do it at once, because it´s to much output size?
i have solved this prob for me to skip the “area”, then it worked! now i have to do two exports and then combine them in excel, but this is anoying.
edit: not even without area it doesn´t work. then there no instant error, but output in tools is endlessly idling…
is there a chance to extend the output size, or any other technique to export that metadata into any file?

thanx in advance
br Frank

## alle Entities mit Areas etc.
## ALLE Devices mit zusatzinformationen (ACHTUNG: dauert! ewig!...nö geht relativ schnell? 2025-07-05)
## von ComunityUser Taras , ohne leerzeichen am Anfang nd model ID separat!
Entity ID;Device;Domain;Manufacturer;Model;Model ID;Area;Integration;ID
{% for s in states -%}
{%- set identifiers = (device_attr(s.entity_id, 'identifiers') | default([], true)) | first | default([], true) -%}
{%- set integration = identifiers[0] | default('-', true) -%}
{%- set unique_id = identifiers[1] | default('-', true) -%}
{%- set manufacturer = device_attr(s.entity_id, 'manufacturer') | default('-', true) -%}
{%- set model = device_attr(s.entity_id, 'model') | default('-', true) -%}
{%- set model_id = device_attr(s.entity_id, 'model_id') | default('-', true) -%}
{%- set area = device_attr(s.entity_id, 'area_id') | default('-', true) -%}
{{s.entity_id}};{{s.name}};{{s.domain}};{{manufacturer}};{{model}};{{model_id}};{{area_name(area)}};{{integration}};{{unique_id}}
{% endfor %}

Have you considered just using an API call?

Grab a copy of the core.entity_registry from the hidden .storage folder & paste it into excel. You can remove the first few lines which will allow you to change the csv into proper excel columns

No it’s a fundamental truth like water is wet.

Id probably go with Shadows solution if it’s one off.

Learn how to do what Drew suggests if it’s a repeating act because again that limit is a fundamental and you must build around the limit.

hi @Didgeridrew thanx
no not really sorry :innocent:
as a non developer i like the word “just” in your comment :wink::wink:
i would need a patient teacher for simply starting with that topic at all.
but i put it on my bucket list as i´m interested in learning to use APIs…

thanx for that hint! :+1:

hi @ShadowFist ,

thanx for your comment.
i take a look into ‘entity_registry’ file. it seems “column names” are besides the values, what would make it a little bit complicated for my needs?

now i build me a short workaround with two separated template calls, what results i´m copying into my existing excel, where this is “merged” via XLOCKUPs.
i used that to clean up some template errors and added a tabulator separator, what makes simply copy&paste into excel much more convenient.

but thank for that, good to know where the central entity files is! :+1:

thanx @NathanCu ,

No it’s a fundamental truth like water is wet.

i expected this, but thanks for your honesty :wink:

i need it regularly, but just from time to time to check my influxbd and mariadb exclusions and continious_querys.
currently because my both databases size(s) have “exploded” over the last two weeks

What are you using this for regularly? You should link up with an ai and have it build a script for you instead of this manual process.

As a fellow non-developer… don’t insult yourself, it’s easier than it looks at first glance. :upside_down_face: