☑️ ChoreOps - Level Up Your Household Tasks

Share your Projects! Custom Integrations
41

Hi and firstly Thank you very much for your hard work and effort you put into this!

I have migrated from KidsChores without any issues, awesome! But there is one little thing that wont work as planned on my side and im not sure what causes this:

Issue: Kids can auto approve the Chores:

I’ll start at the beginning so you know my situation and maybe have an idea:

  • The logged in User to HA is always a Parent since my kids dont have devices to use HomeAssistant on.
  • My Kids do have a Home Assistant Login (If remember correctly it had to be for the KidsChores)
  • Kids claim a chore
  • Click the claimed chore in the Kids Dashboard again and it is auto approved and Points are rewarded.
  • I have tried new chores, added new Kids to test. I know of the auto-approve setting in a chore but this is set to “off”

And another small thing: i get a notification for a claimed chore which is superb, BUT i actually get duplicate Notifications every time. (:raised_hand: Kid1: Chore Claimed
Kid1 claimed Putzen 1 minute ago AND✋ Kid1: Chore Claimed Kid1 claimed Putzen 1 minute ago)

Any ideas? Could it be the Main Login?

42

No, there is not a feature for that at the moment. Not exactly what you are asking for, but you could consider adding “Morning” labels to all those chores so they would show grouped in the chores card or even create a separate card just showing that label group.

43

The ability to approve chores is governed by two things you should check:

  • The HA user account they use may have administrative rights to home assistant rather than being setup as user only access. By default this allows those accounts to approve chores.
  • In ChoreOps there user profile is setup as an approver for themselves or someone else. At this point, if you are given approval rights for any user, you can approve claims from anyone. (This will be changing in the next release)

Advanced: Access Control · ccpk1/ChoreOps Wiki

As for the notification duplication, it is the first I’ve heard of it, which makes me think you should check the following:

  • Confirm the notification service you are using is not a group with multiple endpoints
  • Verify that any other users/approvers are not using the same notification service you have set for yourself.

If you are still having issues after that, head over to the repo and create and issue with your diagnostics download and I’ll help you troubleshoot further.
Issues · ccpk1/ChoreOps

Good luck

44

:rocket: ChoreOps 1.0.7 is Now Live!

Hi everyone! I just pushed the 1.0.7 release. This update focuses heavily on making chore approvals and scheduling more flexible for real life, improving dashboard usability, and tightening up a few important backend issues based on your feedback.

Here is what is new:

:closed_lock_with_key: Stricter Approval Controls (Minor Breaking Change)

This is an important one! We tightened up how chore approvals work so you have much more control over who can approve what:

  • Targeted Approvals: Non-admin approval rights are now strictly scoped to explicitly linked users. (Previously, having approval rights on a single user acted as a global authority for everyone).
  • Admin Override Toggle: Home Assistant Admins no longer automatically get global approval authority if you don’t want them to. There is a new configuration option to turn this off if you prefer stricter controls.(Note: If you suddenly can’t approve a chore after updating, just double-check your user link settings!)

:palm_tree: The “Vacation” Update (Bulk Rescheduling)

You can now bulk reschedule chores after a chosen date using the new reschedule service. This is especially useful for vacations, school breaks, travel, or any time normal household routines need to shift without having to edit every single chore one by one. Service: choreops.schedule_chores_after

:broom: Cleaner Dashboards

Generated dashboards now support filtering out unscheduled chores, as well as chores that are due too far out in the future. This helps keep the chore views much cleaner and focused only on what actually matters right now.

  • Review dashboard yaml pref_ options to exclude chores by group, no due date, or max days from now. (Must regenerate dashboards to get the updates)

:100: Decimal Point Support

Points and dashboards now support decimal precision! This gives families a lot more flexibility when building out reward systems and balancing chore point values or for those of you that want to use real money values.

  • Review dashboard yaml pref_ options to enable decimal display (Must regenerate dashboards to get the updates)

:hammer_and_wrench: Workflow Fixes & Accuracy

This release tightens up the backend engine, including fixes for recurring due-date validation, stale chore dates after resetting auto-approvals, missing custom interval fields and chore update service sync behavior when chores are reassigned to different users.

:earth_africa: Translation Updates

A huge thank you to the community contributors for this! Dashboard translations have been updated for French, and we have officially added Polish as a supported language. That brings us to an amazing 14 total languages supported!

Thank you to everyone who has opened issues, tested changes, contributed translations, and helped improve ChoreOps over the last few weeks. Your feedback is directly shaping how this project evolves!

Releases · ccpk1/ChoreOps

:heart: Support the Project

If ChoreOps helps keep your household running smoothly, there are a few ways you can fuel its development and show that it is providing meaningful value to you and your household.

:star: Star this repository!
If you like this integration, the best (and free!) thing you can do is click the Star button at the top of this page. It helps other users discover the project and builds trust as we grow.

If this work is especially meaningful to you, there’s nothing better than showing it as a sponsor or a tip to help offset the cost of tools, translations, etc.

Sponsor
Buy Me A Coffee

1 Like
45

This is a great tool built into the existing home automation platform. I hope it gets more attention!
I have my son churning through chores to maintain his streak :heart_eyes:

I’ve dug out some older iOS devices (iPhone X and iPad Pro 2018) so kids can claim chores and see their rewards, badges etc as well as an iPad pro for a hub showing a dashboard. Unfortunately with 5 users and 42 available chores it brings the older devices crashing to their knees (Safari and companion app). We need to use modern devices from the last few years to claim chores. I’ve created generic small medium large chores to account for keeping the total number of unique chores down but it would be good if this could be optimised somehow.

It would be great to have a way to pause a cumulative badge for vacation/sickness so people don’t drop out and through the grace period.

I also had a mishap where I created a new achievement that was assigned to a specific user where they had to complete a specific chore 12 times. After submitting, it didn’t respect those 2 conditions and the achievement points were awarded to all users multiple times based on total number of all chores completed. Strange.

Thank you for developing this. I’ve tried thinking of ways to digitally gamify chores in a customisable way and this is it.

46

For the older ios devices, they don’t have the proper support updates to handle the templates used in the modern dashboards, so there isn’t a way to optimize, it is general compatibility. This was reported in [REQ] Legacy iOS-compatible dashboard path for older iPads · Issue #57 · ccpk1/ChoreOps where I did create a “Chores Lite” template that was working for some to do basic claims and approvals from those older ios devices. Just go to your dasboard generator and create a new dashboard using “Chores Lite” template and see if you have any luck.

This is a common request, and it’s something I’ve seen come up for the chore side of the integration as well.

While a “pause” button sounds straightforward, the backend logic for freezing a rolling point window without breaking the progression gets complicated quickly. I’m definitely thinking on a better way to handle this natively, but in the meantime, here is the best way to handle it:

The Current Workaround: Extend the Grace Period

If you know a vacation or a scheduled surgery is coming up, you can manually extend the Grace Period on that specific cumulative badge. This gives the user more “buffer days” to stay within their current maintenance window without the badge resetting.

Maintenance vs. Grace

To give some context on how these two features are intended to work together:

  • Maintenance Windows: These are designed as the “long-term motivator.” They require a user to hit a weekly or monthly point threshold to keep their rank and continue their multi-month path to the next badge tier.
  • Grace Periods: This is the “safety net.” It represents extra days allotted on top of the maintenance cycle specifically to cover being sick or away for a few days.

I’ll keep looking into a more elegant “vacation mode,” but for now, bumping that grace period is the most reliable way to ensure a well-earned break doesn’t kill a hard-earned streak.

I haven’t heard of this one previously, but I’ll take a closer look as we consider some future upgrades to achievements. Badges are much more configurable and well designed implementation at this time.

Good luck and thanks for the kind words.