Section for Anytime Chores

[zakird1]

For chores that can be completed Anytime (i.e. they have no due date), it would be great if those were placed in a separate section. Currently, they appear in the "Due Today" section alongside the other chores that have a true Due Date of today. My example here is the Unload Dishwasher chore. That doesn't have a specific timeframe... it can happen whenever we need it to. We have many others like this as well. Having this in its own section would help organize chores better and help our kids see what is truly due "today".

[ccpk1]

I'm not sure if you've found the configuration options for the dashboards yet. They do require an easy edit to the chores card yaml on the kids dashboard, but it is designed to be quick and simple to find.

In your case I assume "Unload dishwasher" is set as daily recurring.

pref_include_daily_recurring_in_today (default: true)

Keeps recurring daily chores without a due date in today groups.
When false, those chores move to “other” grouping logic.
Allowed: true, false.

More information:
https://github.com/ccpk1/ChoreOps/wiki/Advanced%3A-Dashboard
https://github.com/ccpk1/ChoreOps/blob/main/custom_components/choreops/dashboards/preferences/user-gamification-premier-v1.md

[zakird1]

Hmm... I am trying this but it still shows up in the "Today" section.

Here is my chore setup...

Frequency = Daily
Due Date = Null
Due Window = 0
Completion/Reset Timing = Once Per Day/At Midnight
Overdue: Never

And here is the dashboard YAML for this flag...

[zakird1]

I found another reference to this flag in the YAML further down (I guess I'm not sure which one I'm supposed to change). when I change this second one to false, it does move it out but it also moved ALL chores that are set up as Daily (even those which have a due date) out of the today.

[ccpk1]

It's definitely teh first one. If you look closely, you'll notice that is in the user configuration section. The one further down is for some normalization.

That said, I can reproduce this not working as expected, so I'll have to take a closer look. That Jinja logic gets a little complex and I probably missed something small. You are definitely putting the integration through its paces and keeping me honest. 😄

[zakird1]

Thanks! Also -- I completely understand the complexity of this tool. Bugs are to be expected. Thanks for remaining engaged and I'll help you continue to find these cases.

[zakird1]

Want me to log an issue for this one?

[ccpk1]

Sure, that would be great.

[ccpk1]

Closing the loop on this one... The issue was resolved in pull #276 which is merged in the current release 1.5.2.