I’ve used choreops.reset_transactional_data with user selection, when I made reset I have found all my chore tasks schedules also has been reset. I dont know why? It is looks like a bug: I want to reset only user achievments, it shouldn’t affect to chore data.
So, periiod fo all tasks has been reset to ‘none’
Learning for achievments. Haven’t managet t.o how to use " Kitchen Specialist: Complete 30 approved chores" with a kitchen label. Not found in documentation how to proprerly use kitchen label etc, how to use tag or something else
It looks like you probably ran the “Reset Transactional Data” service without specifying that you only wanted it to run on only achievements or just a specific achievement. This is part of the reason it requires you confirm the changes you are making are destructive before executing. You can find more detailed instructions in the Services Wiki
There is not currently a capability allowing you to dynamically track and attach all chores with a specific label to an achievement or badge. The current capability is to edit the achievement and select all chores you want associated with that achievement. Configuration: Achievements · ccpk1/ChoreOps Wiki
ChoreOps v1.5.1 is Now Live!
Hello everyone!
Following a beta period focused on fixing edge cases and validating structural integrity, I’m happy to announce that ChoreOps v1.5.1 is officially live and ready for production!
Full Release Notes & Codebase: ccpk1/ChoreOps Releases
Documentation: ChoreOps Wiki
Community & Support
Thank you for your continued testing, bug reporting, and community support. We’re now at over 380 stars on GitHub — a great milestone, and every star, piece of feedback, and encouraging note drives this project forward.
A special thank you to everyone who has contributed financially to help offset development costs. Building an open-source platform like ChoreOps takes an immense amount of time and focus. When you back that work with your wallet, it proves this tool brings real, tangible value to your home.
Release Highlights
This release tightens the core experience with correctness, security, and quality-of-life improvements:
- More Robust Admin Button Security: Admin buttons now require a logged-in account by default, with a new toggle in General Options to restore the legacy behavior if needed. Services remain the recommended path for scripts and automations.
- Accurate Chore State: Fixed stale “overdue” reporting for shared/rotation chores, the “Due Today” count, and standby chore groupings.
- Fewer False Notifications: Suppressed spurious approver alerts for primary-standby chores and fixed the non-gamified approver template.
- Badges & Scheduling: Badge
start_dateis preserved on schedule edits, new clear-date checkboxes, and chore sensors now expose the custom interval for all custom frequencies. - New
choreops.get_ledgerService: Audit point transactions with a structured, filterable ledger dump. - Localization: A big thank-you to Zeljko-07 for a thorough manual revision of the German translations, and to Mountcomb for adding Simplified Chinese — the first East Asian language in ChoreOps!
Quick Upgrading Notice
Breaking change for scripts & automations: Admin buttons now require a logged-in account by default. If you press admin buttons from a script or automation, those calls will be denied — migrate them to the equivalent services (choreops.approve_chore, choreops.disapprove_chore, choreops.apply_bonus, choreops.apply_penalty, choreops.manual_adjust_points), or re-enable the legacy behavior via the “Enforce Authorization for Admin Buttons” toggle in General Options.
Dashboards must be regenerated: To receive all of the improvements and fixes in this release, please re-generate your dashboards using the updated templates. This is required to pick up the dashboard fixes (including the label-grouping fix and the new custom-interval display) — simply updating the integration alone will not apply them.
To Update: Head to HACS, select Redownload, choose the stable v1.5.1 release tag, and completely restart Home Assistant (a full restart is required after a HACS upgrade).
Thank you again to everyone who tested the beta releases and supported this milestone.
Hello @ccpk1,
Very nice application! exited to use it. Is there an option to have a fastmenu in dashboard to create a new task? It’s now 4 a 5 clicks away and that is a bit of a bump to use it easy.
This is not something that exists in the integration today, however the backend integration was built to support it and there have been a lot of requests for it. Below are a couple links to earlier comments about it, but it isn’t something I’ve had time to focus on. Just the base support of this integration and ensuring the platform is stable takes the majority of my free time at the moment.
There was a recent post by ryanlenard showcasing something he built and shared
I haven’t had time to play around with it, but it does have a nice look and for those of you interesting in tinkering, it might be useful.
Chore Manager · Discussion #231
1 Like
I’ve looked through the docs and admit I could be missing it or messing up my workflow but I see that with Badges only the Cumulative badge allows for a Points Multiplier. I was trying to set it up for example:
Kid completes chore: Clean Room
Once approved this awards the Badge: Cleaner Bot - set to reset weekly.
The badge nor chore have points assigned to them but they assign a Points Multiplier of 1.3X for the lifecycle of the badge (the week).
If they go past the week without achieving the Clean Room chore again it falls off and the points return to 1.0x.
But I can only find multipliers in the Cumulative badge option and that doesn’t have a way I see to assign to a specific chore the way the Periodic badge offers. Is there a different way to use the Points Multiplier function in this way and I’m just missing it?
You aren’t missing anything. Cumulative badges are intentionally the only tool that can affect the multiplier. Cumulative badges are based on total points earned, regardless of origin, and were generally designed for longer term overall tracking. There is the concept of maintenance intervals on cumulative badges you can set up to encourage ongoing performance, but those measurements are also based total points earned in that maintenance period. (I.e. earn 500 points each week or the current multiplier level will drop down to the level of the prior badge or 1.0x)
Periodic badges allow for tracking individual chores or groups of chores and support all other reward types.
Is there a way to un-complete a chore and take back the points in a single click? I know we can ‘clear date’ to reset the chore status but the points don’t get deducted. I need to manually reduce the point balance after resetting the date.
There is not a way to automatically revert a completed chore. There have been requests to build this capability, but it’s actually more complicated than is seems. Here is a link to more detail. [REQ] Revert a completed chore back to pending · Issue #90 · ccpk1/ChoreOps · GitHub
400 Stars! Yesterday ChoreOps crossed 400 stars on GitHub — and we marked the milestone by shipping a release! Thank you to everyone who has starred, reported issues, contributed translations, or spread the word. Four hundred stars on a family chore tracker is a genuinely heartwarming milestone.
If ChoreOps is making chore time smoother in your home, please consider giving back:
Star the repository — if you haven’t yet, it’s the easiest way to help others discover ChoreOps.
Sponsor the project — support ongoing development directly through GitHub Sponsors.
Buy Me A Coffee — every coffee fuels the next fix or feature.
ChoreOps 1.5.2 Released
Version 1.5.2 is a focused polish pass — fixing dashboard preferences that silently ignored your configuration, closing state-transition edge cases, and making “never overdue” chores finally tell the truth about being actionable.
Please re-generate your dashboards after updating — the dashboard-side fixes below require the updated templates. Updating the integration alone will not apply them.
Highlights
Dashboard preferences now respect your YAML — if you ever set a preference to false and wondered why nothing changed, this is the fix. Boolean preferences work across all dashboards, the “Show Completed” toggle now actually wins over YAML, and the daily-recurring “Today” filter behaves as documented. The dead pref_include_weekly_recurring_in_this_week preference was removed (use pref_exclude_group_list: ['this_week'] instead).
No more midnight “overdue” flash — chores with pending claims briefly flickered to overdue at the midnight reset, triggering false overdue automations. Fixed.
Standby users respect the claim window — on primary-standby chores, a standby with “claim anytime” could claim before the window opened. A closed window now blocks standbys regardless of claim mode.
“Never overdue” chores now show as due, not pending — chores past their due date with Never overdue handling are now clearly marked as claimable instead of blending in with not-yet-due chores. They’re still never shown as overdue, and the state clears on completion.
state: duewill now also fire for never-overdue past-due chores — review state-based triggers if needed.
Plus: weekday names now work in the applicable_days service field (thanks to first-time contributor @tmmueller!), and German + Simplified Chinese translations received further community refinement.
Full release notes: ChoreOps 1.5.2 on GitHub
Update via HACS, re-generate your dashboards, and enjoy!