Frequently Asked Questions (FAQ)

This page covers common questions about ChoreOps and the dashboard experience.

---

Why do I see claiming or authorization errors when pressing buttons?

Most of the time, this means ChoreOps is correctly enforcing access rules for the current Home Assistant session.

Check these first:

• Personal device setup: make sure the ChoreOps user is linked to the matching Home Assistant user account.
• Shared tablet setup: if assignees use a shared dashboard session, enable Kiosk Mode for assignee claim and redeem actions.
• Approver action: kiosk mode does not grant approver or admin privileges, so approval buttons still require the right role.
• Dashboard generator warning: if the generator warned that selected users were unlinked while kiosk mode was off, fix that warning instead of ignoring it unless the limitation is intentional.

Read these next:

• Getting Started: Quick Start
• Advanced: Access Control

If the setup looks correct and the error still does not make sense, continue with Technical: Troubleshooting.

---

Is this still KidsChores? What should I know if I am migrating?

ChoreOps is the evolution of KidsChores: the same core family workflows are here, with expanded features, cleaner role modeling, and improved operational tooling.

The biggest day-to-day terminology change is role-based naming:

• Everyone is a User in ChoreOps.
• Legacy Kid maps to Assignee (the person doing chores and earning/spending points).
• Legacy Parent maps to Approver (the person approving or administering actions).

If you are migrating from KidsChores, use:

• Migration from KidsChores
• Quick Start Guide

---

How does access approval work in ChoreOps?

ChoreOps enforces role-aware permissions for claim, redeem, approve, and disapprove actions. The user in ChoreOps needs to be associated with a Home Assistant user ID for this to work properly.

Short version:

• Assignees do assignee actions
• Approvers/admin-capable users handle approval actions
• Shared-device behavior (including kiosk mode) is configurable

For the complete matrix and caveats, see: Advanced: Access Control

---

Is this only for kids?

No. ChoreOps supports any household or team-style setup where people have assigned work and optional approval workflows.

You can model the same household-friendly patterns as before, or use role-based workflows with different naming that fits your use case.

---

What is the easiest way to reset or start over?

For most users, the preferred method is the reset_transactional_data service because it can reset either everything or only targeted slices of runtime data.

What reset_transactional_data can reset

• Comprehensive reset: reset transactional/runtime state broadly (global scope)
• Granular reset: target one assignee and/or one item type (for example chores only, points only)
• Fine targeting: optionally narrow by item_name when supported

This lets you recover from testing mistakes or stale runtime state without always deleting and recreating all configuration.

See full field definitions and valid values in: Services Reference

Example: comprehensive reset (global)

action: choreops.reset_transactional_data
data:
	confirm_destructive: true
	scope: "global"

Example: granular reset (single assignee + item type)

action: choreops.reset_transactional_data
data:
	confirm_destructive: true
	scope: "user"
	user_name: "Sarah"
	item_type: "chores"

Warning

Reset actions are destructive and cannot be undone. Confirm your target scope before running.

Alternative: full reinstall

If you want a complete clean slate, including definitions and setup state:

1. Remove ChoreOps from Settings → Devices & Services.
2. Restart Home Assistant.
3. Reinstall ChoreOps and configure again.

---

Can assignees approve their own chores?

For users with only an assignee role, self-approval is not allowed.

For users with an approver-capable role, self-approval is allowed and the approver action path always works.

In practice, if a user is configured with only the assign/approve-style approver controls (for example "allow assign to" patterns), they may see only approver buttons. In that setup, the approver button flow acts as a single-step claim/complete path for that approver-capable user.

Use the full policy details here: Advanced: Access Control

---

How do I troubleshoot ChoreOps issues effectively?

Use the troubleshooting workflow for logs, state checks, diagnostics, and issue reporting:

• Troubleshooting guide

---

Have another question? Open an issue at GitHub Issues.