Skip to content

Configuration: Challenges

ccpk1 edited this page Mar 2, 2026 · 3 revisions

Warning

Challenges will be made available in future update.

Prerequisites: Configuration: Users, Configuration: Chores, Configuration: Points Scope: Configure time-bound assignee or group goals


Overview

Challenges are time-bound goals designed to drive short-cycle focus.

Use challenges when you want:

  • Campaign-style goals for a date range
  • Team or cohort targets with urgency
  • Automatic point rewards on successful completion

Note

The challenge/achievement model is legacy and expected to evolve in future ChoreOps versions. This page documents the current configuration contract and will be updated as the model is re-imagined.


Legacy configuration reference

Note

Challenges are currently unavailable for new setup in this release. The steps below are retained as legacy reference for existing installs and migration context.

  1. Go to SettingsDevices & ServicesChoreOpsConfigure
  2. Select Manage Challenge
  3. Choose Add Challenge
  4. Complete the form and save

Field guide

Basic fields

Field Required Notes
Name Yes Unique challenge name
Description No Optional context or rules
Labels No Optional organization tags
Icon No Material Design icon

Assignment and scope

Field Required Notes
Assigned Assignees Yes Who participates in the challenge
Selected Chore No Leave blank to count qualifying activity across chores

Goal and timeframe

Field Required Notes
Type Yes Challenge behavior model
Criteria Yes What is counted toward progress
Target Value Yes Completion threshold
Reward Points Yes Points granted on completion
Start Date Yes Challenge start time
End Date Yes Challenge end time

Behavior summary

  • Progress is evaluated within the configured date window
  • Updates occur as qualifying chore lifecycle events are processed
  • Completion awards configured points
  • After end date, challenge progression stops

Warning

Date windows should be explicit and realistic. Very short windows can look like tracking failures when no qualifying events occur in time.


Recommended setup patterns

Pattern 1: Weekend sprint

  • Short date range
  • Clear target value
  • Visible, motivating reward

Pattern 2: Monthly campaign

  • Team-wide assignment
  • Mid-range target and balanced reward
  • Label related chores for easier monitoring

Pattern 3: Seasonal focus

  • Themed chores and labels
  • Fixed start/end dates
  • Communicate scope clearly to participants

Example goal ideas

  • Weekend Warrior: Complete 10 approved chores between Friday and Sunday
  • Monthly Marathon: Complete 50 approved chores during a calendar month
  • Theme Sprint: Complete a target number of chores with a specific label before end date

Challenges vs badges

  • Use challenges for short, time-bound campaigns with explicit start/end dates
  • Use badges when you need broader motivational structures beyond campaign windows
  • Use linked badges with challenges when you want challenge completion to trigger badge recognition

Troubleshooting

Challenge progress not updating

  • Confirm current time is within start/end window
  • Confirm assigned assignees and criteria match real activity
  • Confirm selected chore (if set) is the one being completed

Challenge ended unexpectedly

  • Check end date and timezone interpretation in Home Assistant
  • Reopen or recreate with corrected dates if needed

Related docs


Last Updated: February 2026

Clone this wiki locally