-
-
Notifications
You must be signed in to change notification settings - Fork 1
Configuration: Badges Periodic
Prerequisites: Configuration: Users, Configuration: Chores Scope: Configure recurring mission-style badges
Note
In kid-facing dashboard wording, these may be presented as Quest Badges or simply Quests. In Home Assistant configuration screens, the setup flow still uses Periodic Badge and Daily Badge terminology.
Periodic badges track goals over a period you define.
They can run in three modes: open-ended, one-time, or recurring.
Use them when you want:
- Weekly/monthly mission targets
- Consistency goals (days/streak patterns)
- Optional penalties for missed targets
- Scope-limited tracking via selected chores
Tip
Daily badges and special occasion badges are a special short-cycle variant of periodic behavior. In dashboard language, this badge family works well as Quest Badges.
- Go to Settings → Devices & Services → ChoreOps → Configure
- Select Manage Badge
- Choose Add Periodic Badge or Add Daily Badge
- Configure fields and save
| Field | Required | Notes |
|---|---|---|
| Badge Name | Yes | Unique display name |
| Description | No | Optional context |
| Labels | No | Optional organization tags |
| Icon | No | Material Design icon |
| Field | Required | Notes |
|---|---|---|
| Target Type | Yes | Defines what is measured |
| Threshold Value | Yes | Required value for success |
Common target families:
- Points-based
- Count-based
- Days-based
- Streak-based
Note
Available Target Type options depend on your badge setup:
- Daily badges exclude streak target types.
- If tracked chores are available but left blank, all chores assigned to that profile are in scope.
- Due-only and no-overdue variants are strict modes and should be used intentionally.
Use selected chores when only specific chores should count toward badge progress.
- Leave blank to include all relevant chores
- Use filters to avoid cross-impact from unrelated chores
- No-overdue and due-only target variants are most useful when this scope is explicit
| Field | Required | Notes |
|---|---|---|
| Assigned To | Yes | Select eligible profiles |
Note
Some UI labels and runtime keys may still use legacy terms such as assigned_kids. Keep literal key names intact when you reference schema/UI contracts.
You can configure award items on success and optional penalties on failure.
- Points
- Rewards
- Bonuses
- Penalties
Periodic badges use a configurable schedule window:
- Frequency (daily/weekly/monthly/etc.)
- Optional custom interval fields
- Optional start/end date boundaries
Daily badges use a simplified reset model and typically do not expose full schedule fields.
| Mode | How to configure | What happens |
|---|---|---|
| Open-ended | Frequency = None (and/or no end date) | Progress continues without automatic cycle rollover |
| One-time window | Set a date window but no valid recurring interval | Badge evaluates in that window and does not auto-start a new cycle |
| Recurring cycles | Use a recurring frequency with a valid cycle boundary | When the cycle ends, counters reset and a new cycle begins |
Tip
For periodic custom schedules, a practical recurring setup is: end date + custom interval + interval unit.
Warning
If you expect automatic resets, make sure your configuration actually defines a repeatable next cycle. End date alone does not guarantee rollover.
- Target: days/streak type
- Schedule: weekly
- Penalty: none or light
- Target: strict no-overdue variant
- Schedule: weekly or monthly
- Penalty: proportional and recoverable
- Tracked chores: selected subset only
- Target: count or points from those chores
- Schedule: short, repeatable windows
- Verify assigned profile is included
- Verify selected target type matches expected behavior
- Check tracked chores filter is not over-restrictive
- Confirm the badge is in the expected behavior mode (open-ended, one-time, recurring)
- Check if target type is a strict no-overdue variant
- Verify overdue behavior on tracked chores
- Confirm schedule window boundaries
- For one-time windows, verify the current date is still inside the configured window
- For daily + day-count style targets, keep threshold realistic for a one-day cycle
- Confirm frequency is not None
- For custom schedules, confirm interval and interval unit are both set
- Verify the badge has a valid cycle boundary to advance into
- Configuration: Cumulative Badges (Rank badges)
- Configuration: Badges overview
- Advanced: Periodic Badges (Quest badges)
- Technical: Badges
Last Updated: March 2026 (dashboard terminology bridge for Quest badge wording)
🚀 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