Significant Lag when Claiming and Approving Chores

[jarek36]

Home Assistant version

2026.5.1

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

Dashboard UI/template

Steps to reproduce

1. Create "Chores Standard" dashboard
2. I have ~15 different chores

Issue description

When using the dashboards from either a tablet, HA app on mobile phone, or my computer, there is up to a 5 second delay from the action of claiming a chore and that chore then showing as claimed. This also happens with approval actions.

Relevant entity IDs (optional)

No response

Logs

Additional context

Running HA via VM on a Synology NAS. VM CPU and memory resources do not spike when those actions are run

[ccpk1]

Take a look at the Troubleshooting guide - Integration vs Dashboard, specifically trying to narrow down whether the performance issue is in the backend integration, or something to do with the way it is rendering your dashboards.

Let me know what you find or if you have questions.

[jarek36]

will do. Appreciate the quick response!

[jarek36]

I’m seeing websocket backlog errors when using ChoreOps, specifically:

"Client unable to keep up with pending messages. Reached 4096 pending messages."

My users' dashboards have decent, albeit inconsistent, responsiveness when claiming chores. The OpsCenter approvals really lag, and if I approve more than 1 at a time, it triggers this websocket error

[ccpk1]

Thanks for letting me know about your setup! Since you are running Home Assistant in a VM on a Synology NAS, I'm wondering if we might be hitting a database I/O (disk write) bottleneck.

One of the unique things about ChoreOps is that it intentionally exposes a lot of rich data to the frontend to allow for high levels of dashboard customization. The tradeoff is that every time you claim or approve a chore, Home Assistant has several UI entities to update and recorder tries to write all of those heavy data updates to your long-term database, which can cause the lag and websocket errors you are seeing.

To test this theory, I'd like to have you try turning off the recorder for the ChoreOps domain to see if you notice a performance difference. Try adding this to your configuration.yaml:

recorder:
  exclude:
    domains:
      - choreops

Restart Home Assistant and try claiming a few chores. Let me know if that helps clear up the delay! If it does, we can work on refining exactly which entities need to be excluded.

[jarek36]

Again, appreciate the responsiveness. The integration is a gamechanger -- kids are fighting to do chores (lol!).

Added that line to the config and it didn't result in any change in the responsiveness. I tried the "lite" dashboards with the same result....

More info:

• Setup: 4 kids, 17 chores total. ~300 entities between them.
• The delay appears before the UI updates, which makes me think it may be backend/event processing rather than frontend rendering
• It's not debilitating (at least for me), just takes some patience to wait on the claim functions before trying to claim another

Happy to help test anything or provide logs if useful.

Thanks again!

[ccpk1]

Sorry I"m just getting back to you now. Any change in behavior since your last post? If not, would you mind doing a diagnostic download and provide it here.?

Also, in the troubleshooting guide, it shows how you can use developer \ states to show the buttons and sensors for a single chore. Can you run through a claim > disapprove > claim > approve while all from the developer \ states view using the buttons and sensors. I'd like to understand roughly how long it takes from when you click claim for the sensor to show up with status of claimed, but all from that developer view so there is no dashboard involved at all. Timing does not need to be precise. Instant, 1 second, 3 seconds, etc.

Thanks

[Ehill05]

I've seen a similar issue on mine, particularly after I have added/edited chores and whatnot.

[jarek36]

Sorry I"m just getting back to you now. Any change in behavior since your last post? If not, would you mind doing a diagnostic download and provide it here.?

Also, in the troubleshooting guide, it shows how you can use developer \ states to show the buttons and sensors for a single chore. Can you run through a claim > disapprove > claim > approve while all from the developer \ states view using the buttons and sensors. I'd like to understand roughly how long it takes from when you click claim for the sensor to show up with status of claimed, but all from that developer view so there is no dashboard involved at all. Timing does not need to be precise. Instant, 1 second, 3 seconds, etc.

Thanks

I should be able to get around to this in the next couple of days. Behavior is the same. Diagnostic file attached. Thanks!

config_entry-choreops-01KRCXN4Y1R9WPH74C3KQ7535M.json