Advanced: Dashboard
Target audience: Power users and maintainers Prerequisites: ChoreOps installed and at least one generated dashboard Related: Getting started: Dashboard generation
In ChoreOps, dashboard generation is built into Options Flow. You can:
- Generate dashboards from UI options
- Choose template IDs and admin layout in the generator
- Update/rebuild without re-pasting full template files
Note
Available template choices are shown in the generator UI. This page avoids hardcoded lists so maintenance stays low when templates evolve.
Install required frontend cards from HACS → Frontend.
Note
The generator validates dependencies from template metadata. Missing recommended cards warn; missing required cards require explicit acknowledgment to continue. In the review step, section headings remain plain and each missing card row is prefixed with ❌.
Generated dashboards are intended to be dynamic building blocks, not locked layouts.
- Every generated card is powered by ChoreOps sensors/buttons
- You can keep generated layouts as-is, or customize heavily
- You can copy any card from a generated view and paste it elsewhere in Home Assistant
Most cards are designed to adapt by assignee context (kid/profile name/slug), so reuse is straightforward.
Generated cards read from runtime entities and helper attributes, including:
- Dashboard helper sensor per assignee
- Chore/reward/badge sensors
- Button entities for claim/redeem/approve/disapprove actions
Because data is entity-driven, you can remix cards into other dashboards, tabs, or conditional sections without changing backend logic.
For contracts and troubleshooting, see Technical: Dashboard generation.
Most generated cards can be copied and pasted into other dashboards and views. They are intended to be self-contained building blocks.
The main exceptions are:
- The full Chores card in the Chores templates
- The Chores card in the Gamification template
Those two chores cards are not fully self-contained. They rely on shared template code that lives at the dashboard level, outside the individual card or view. If you copy only the visible kid view or card into another dashboard, the chores section can lose those shared definitions and show a configuration error.
If you want to move or reuse one of those two advanced chores cards, use one of these approaches:
- Use the dashboard generator to create the full dashboard first, then make your custom changes there. You can generate multiple dashboards with different names if you want separate layouts.
- Use the Chores Essential template instead. It has fewer features, but it is much easier to place into an existing dashboard and rearrange with drag-and-drop.
- If you want to move the Standard or Gamification chores version into another dashboard, open the raw dashboard editor and copy the shared template definitions too, not just the visible card or view. Those shared pieces are required for the chores card to work.
Tip
For most other cards, simple copy/paste is still the right approach.
Generated templates use a translation sensor to render localized dashboard terms across languages.
- If you want multi-language behavior, keep using translation-sensor-based labels
- If your custom dashboard is single-language only, you can hardcode your own strings and wording
Hardcoded labels are valid for personal layouts, but they will not auto-localize if users/languages change later.
Before generating dashboards, the final review screen shows links to template preference details. These preferences are additional customizations that can be applied with a quick dashboard edit after dashboards are generated and are more advanced than what the UI exposes.
Think of pref_* options as an extra tuning layer after generation. They are used for additional sorting, filtering, layout, and display customization.
Examples of what preferences can help with:
- Sorting or filtering chores differently
- Hiding completed or blocked items
- Grouping by labels instead of time buckets
- Adjusting columns or layout behavior in supported templates
- Tuning how sections display after the dashboard has been generated
Note
The generator UI covers the common setup path. The linked preference docs cover the more advanced manual adjustments you can make afterward.
- Go through the dashboard generator as usual.
- On the final review screen, open the linked preference guide for the template you selected.
- Generate the dashboard.
- Make only the quick manual
pref_*edits you actually need.
This is especially useful when the built-in UI gets you close, but you want a little more control over sorting, filtering, or layout behavior.
Use generated cards as reusable modules:
- Copy a chore card from generated view A
- Paste into a family overview, room-specific page, or parent dashboard
- Keep entity references aligned with the target assignee/template context
For most cards, that is all you need. For the full Chores card and the Gamification chores card, use one of the three portability options above.
A common pattern is creating multiple chore cards by label.
Example approach:
- Duplicate a chore card block
- Set one to show label group A
- Set the second to show label group B
This is typically controlled through card preference/options (pref_* style settings in template-driven cards) plus label filters.
You can duplicate reward cards for different categories (for example: daily treats vs long-term rewards) using the same dynamic data source and different filters/sort preferences.
You can reorganize sections (chores, rewards, badges, stats) freely in Lovelace while preserving all generator-backed behavior.
Generator updates/rebuilds can overwrite generated dashboard content.
- If you do heavy custom card edits directly in generated dashboards, treat them as changes you may need to reapply after rebuild
- For long-lived custom layouts, consider cloning generated blocks into your own custom dashboard and managing that separately
Warning
Card-level preference/filter tweaks (including pref_* options) are convenient, but can be reset by generator overwrite/rebuild operations.
Before card-level dashboard troubleshooting, run the integration preflight checks first: Technical: Dashboard generation → Preflight: confirm integration operations
- Verify required frontend cards are installed
- Confirm target entities exist in Developer Tools
- Run dashboard update from generator
- Verify assignee/template entity references
- Verify label/filter options match real data labels
- Likely generator overwrite/rebuild replaced generated sections
- Reapply customizations or move custom cards to a separate custom-maintained dashboard
Last Updated: March 2026
🚀 Getting Started
- Home
- Installation
- Migration from KidsChores
- Quick Start
- Quick Start Scenarios
- Dashboard Generation
- Backup & Restore
⚙️ Configuration
- General Options
- Points
- Users
- Chores
- Rewards
- Badges - Overview
- Badges - Cumulative
- Badges - Periodic
- Achievements
- Challenges
- Notifications
🔧 Services
💡 Tips & Tricks
- Template Cookbook for Chores, Rewards, and Approvals
- Auto-Approve Chores
- Calendar Event Due Dates
- NFC Claim Workflow
- Overdue Penalty Automation
- Critical Overdue Alerts
📖 Advanced Topics
- Dashboard Integration
- Access Control
- Chores - Advanced
- Badge Cumulative - Advanced
- Badge Periodic - Advanced
📚 Technical Reference
- Points
- Users
- Entities & States
- Chores
- Badges
- Configuration Detail
- Dashboard Generation
- Notifications
- Weekly Activity Reports
👩🔧 Troubleshooting