[ISSUE] state attibutes exceed maximum size

[danielsc82]

Home Assistant version

2026.4.4

ChoreOps integration version

1.0.7

Installation method

HACS

Prerequisites

• I checked for existing open and closed issues
• I updated ChoreOps (or confirmed the issue still occurs on the latest version)
• If this is a dashboard issue, I updated dashboard dependencies such as button-card and confirmed the issue still occurs
• I enabled debug logging and can share logs

Issue scope

Both integration and dashboard

Steps to reproduce

1. Click a task button to complete a task
2. Check TOP see python maxing out CPU
3. Check HA Logs see errors with sensor state attribute length.

Issue description

When running actions we see huge slow down in performance of the home assistance server. Currently running on proxmox with 2 virtual CPU's and 8gb of ram, tried running the CPU in host mode (my default ) and also in qemu-x86. When looking at logs I see lots of errors occuring with the sensors being too many bytes. It would appear every time a task is completed in dashboard it submit a line containing all tasks currently present, rather than just the selected task.

Relevant entity IDs (optional)

sensors

Logs

2026-05-04 11:14:49.782 WARNING (Recorder) [homeassistant.components.recorder.db_schema] State attributes for sensor.daniel_choreops_ui_dashboard_helper exceed maximum size of 16384 bytes. This can cause database performance issues; Attributes will not be stored
2026-05-04 11:14:49.783 WARNING (Recorder) [homeassistant.components.recorder.db_schema] State attributes for sensor.olga_choreops_ui_dashboard_helper exceed maximum size of 16384 bytes. This can cause database performance issues; Attributes will not be stored
2026-05-04 11:14:50.620 WARNING (Recorder) [homeassistant.components.recorder.db_schema] State attributes for sensor.daniel_choreops_ui_dashboard_helper exceed maximum size of 16384 bytes. This can cause database performance issues; Attributes will not be stored
2026-05-04 11:14:50.621 WARNING (Recorder) [homeassistant.components.recorder.db_schema] State attributes for sensor.olga_choreops_ui_dashboard_helper exceed maximum size of 16384 bytes. This can cause database performance issues; Attributes will not be stored

Additional context

No response

[danielsc82]

Not sure if this references the same issue exactly but it appears in the logs when trying to click on tasks.

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template/init.py", line 409, in ensure_valid
self._compiled_code = self._env.compile(self.template)
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template/init.py", line 2176, in compile
compiled = super().compile(source)
File "/usr/local/lib/python3.14/site-packages/jinja2/environment.py", line 771, in compile
self.handle_exception(source=source_hint)
~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/jinja2/environment.py", line 942, in handle_exception
raise rewrite_traceback_stack(source=source)
File "", line 372, in template
jinja2.exceptions.TemplateSyntaxError: unexpected char '#' at 18881

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template/init.py", line 583, in async_render_to_info
render_info._result = self.async_render( # noqa: SLF001
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
variables, strict=strict, log_fn=log_fn, **kwargs
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/src/homeassistant/homeassistant/helpers/template/init.py", line 459, in async_render
compiled = self._compiled or self._ensure_compiled(limited, strict, log_fn)
~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template/init.py", line 664, in _ensure_compiled
self.ensure_valid()
~~~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/helpers/template/init.py", line 411, in ensure_valid
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: TemplateSyntaxError: unexpected char '#' at 18881

[ccpk1]

Can you provide a diagnostic download from the integration?

Also, when you say "perform an action" are you referring to claiming a chore, approving a chore or something else in particular?

[danielsc82]

In this case I'm claiming a chore, the system has auto approval on.

[ccpk1]

Thanks for the update. when you get a few minutes to upload the diagnostic download, that will be helpful. I have a few ideas of what it might be and that should allow me to narrow it down quickly.

Here are instructions if you aren't sure how to do that.
https://github.com/ccpk1/ChoreOps/wiki/Technical%3A-Troubleshooting#5%EF%B8%8F%E2%83%A3-if-requested-download-diagnostics-or-access-the-choreops-data-file

[danielsc82]

home-assistant_choreops_2026-05-04T01-14-51.300Z.log

[danielsc82]

home-assistant_choreops_2026-05-06T11-22-57.290Z.log

[danielsc82]

Thats the previous debug log I've taken and a new one I just took now, and also the diagnostics file.

config_entry-choreops-01KPWWBGA738HG2TVDVAHQK061.json

[ccpk1]

What you are doing at around 135 chores per user is definitely beyond the level I originally built and tuned the dashboards for! The ChoreOps backend itself is solid and can handle large numbers of chores, but the dashboard/helper layer and the Home Assistant sensor/template/UI layer have real practical limits that we started hitting at that scale.

So, this was not a case of the data model failing; it was more that the way information is surfaced into Home Assistant entities and dashboards needed to be redesigned for a workload of that size.

Why this happens:
That limit is partly intentional. One of the things that makes this integration different is that it exposes a lot of meaningful state directly into Home Assistant instead of hiding everything inside a private backend database and proprietary system/cards. The tradeoff is that we have to work within the limits of Home Assistant entities, templates, helper payload sizes, and frontend rendering.

The Fix:
To support your scale properly, I made some architectural changes so the dashboard data can be split and handled more safely at high density, instead of trying to force everything through one oversized helper surface. The good news is that I now have a real fix direction that supports this properly in testing, but it took more than a simple patch. I’m refining that now and expect to have something ready for you to test within the next day or so.

A quick note on performance:
Please keep in mind that even when the dashboards are working correctly at that density, they are still likely to feel sluggish if you try to render very large chore lists all at once. That is purely a frontend rendering issue, not a backend correctness issue. The data will flow accurately, but forcing the browser to render 100+ complex rows with custom cards is always going to be heavy.

You can absolutely optimize this by creating cards that show smaller, targeted groups of chores, or by using simpler cards (like a standard Entities card) that just show the chore sensor and a claim button. Those kinds of views render much faster and work exceptionally well at scale. Considering you are the first I've heard of to run into these limits, I'd like to keep this dialog going with you after the fix testing as you might have some tips or pointers we could document that would help others in the future using it for larger numbers of chores.

[danielsc82]

I have to say, I haven't managed to get simpler cards working. I tried to make my own but really ran into a dead end early. The intention was to make differnt parts of dashboard for each part of the house. Appreciate you looking into a fix here.