You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a major release. It introduces a full chore recurrence system, removes the smart reward pricing engine in favour of simple fixed costs, and includes several bug fixes and stability improvements.
⚠️ Breaking Changes
Smart Reward Pricing Removed
Dynamic reward pricing has been removed entirely. All reward costs are now fixed values set by the parent.
What this means for existing installations:
Any reward that used dynamic pricing will retain whatever cost was last calculated — this becomes the new fixed cost. Review your rewards after upgrading and adjust costs if needed.
The Days to Goal, Override Point Value, and Completion % Per Month fields no longer exist.
Reward costs are now simply: set a number, that's the cost.
completion_percentage_per_month Removed from Chores
This field has been removed from the chore model. It is no longer stored, exposed in the sensor, or accepted in the config flow. Existing chore data is migrated automatically on first startup — the field is silently stripped.
🆕 Chore Scheduling — Two Modes
Chores now have a Scheduling Mode which determines how they appear and when they can be completed.
Mode A — Specific Days
The existing behaviour. Choose which days of the week the chore appears on the child card. Leave empty to show every day.
Schedule Mode: Specific days of the week
Due Days: Monday, Wednesday, Friday
Mode B — Recurring
The chore has a rolling recurrence window. Once completed, it is not available again until the window expires.
Recurrence
Window
Every 2 days
2 days from last completion date
Weekly
7 days from last completion date
Every 2 weeks
14 days from last completion date
Monthly
30 days from last completion date
Every 3 months
90 days from last completion date
Every 6 months
180 days from last completion date
type: custom:taskmate-child-card
entity: sensor.taskmate_overview
child_id: a8c8376a
recurrence_done_mode: dim
Configurable in the card visual editor.
🆕 Last Completed Store
A new lightweight store tracks the two most recent completion timestamps per chore per child, separately from the prunable completion history. This is what drives recurrence window checking and is never pruned regardless of the history_days setting.
Undo behaviour: Undoing a completion restores the previous completion as the window anchor — a child can't claiam a weekly chore by repeatedly completing and undoing.
🐛 Bug Fixes
Child Card — notAvailableRecurrence Error
The variable used to apply the recurrence dim/hide state was defined in the filter scope but referenced in the render method — causing a ReferenceError that prevented the child card from rendering. Fixed.
Reward Pricing — Static Cost Now Consistent
async_claim_reward and async_approve_reward were still calling the removed dynamic pricing method. Both now use reward.cost directly.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
🚀 New Release: v2.0.0
TaskMate v2.0.0 — Chore Scheduling & Simplified Rewards
This is a major release. It introduces a full chore recurrence system, removes the smart reward pricing engine in favour of simple fixed costs, and includes several bug fixes and stability improvements.
Smart Reward Pricing Removed
Dynamic reward pricing has been removed entirely. All reward costs are now fixed values set by the parent.
What this means for existing installations:
completion_percentage_per_monthRemoved from ChoresThis field has been removed from the chore model. It is no longer stored, exposed in the sensor, or accepted in the config flow. Existing chore data is migrated automatically on first startup — the field is silently stripped.
🆕 Chore Scheduling — Two Modes
Chores now have a Scheduling Mode which determines how they appear and when they can be completed.
Mode A — Specific Days
The existing behaviour. Choose which days of the week the chore appears on the child card. Leave empty to show every day.
Mode B — Recurring
The chore has a rolling recurrence window. Once completed, it is not available again until the window expires.
Configurable in the card visual editor.
🆕 Last Completed Store
A new lightweight store tracks the two most recent completion timestamps per chore per child, separately from the prunable completion history. This is what drives recurrence window checking and is never pruned regardless of the
history_dayssetting.Undo behaviour: Undoing a completion restores the previous completion as the window anchor — a child can't claiam a weekly chore by repeatedly completing and undoing.
🐛 Bug Fixes
Child Card —
notAvailableRecurrenceErrorThe variable used to apply the recurrence dim/hide state was defined in the filter scope but referenced in the render method — causing a
ReferenceErrorthat prevented the child card from rendering. Fixed.Reward Pricing — Static Cost Now Consistent
async_claim_rewardandasync_approve_rewardwere still calling the removed dynamic pricing method. Both now usereward.costdirectly.📋 Files Changed
Backend:
models.py·storage.py·coordinator.py·sensor.py·button.py·config_flow.py·const.py·strings.json·translations/en.jsonFrontend:
www/taskmate-child-card.js·www/taskmate-rewards-card.js·www/taskmate-overview-card.js·www/taskmate-parent-dashboard-card.js⬆️ Upgrading
/config/custom_components/taskmate/Upgrading
Update via HACS or by downloading the latest release and copying to
/config/custom_components/taskmate/.After updating, restart Home Assistant. Lovelace resources will update automatically on restart.
💬 Questions or issues with this release? Reply below or open an issue.
Beta Was this translation helpful? Give feedback.
All reactions