🚀 Release: v3.9.3 — Sub-task / rotation visibility fix

[github-actions[bot]]

🚀 New Release: v3.9.3 — Sub-task / rotation visibility fix

View full release and download on GitHub

---

Fixed

• Parent chore no longer disappears when a bonus sub-task is completed in rotation/alternating mode (#365, #366)
  • On chores with assignment_mode != 'everyone' (alternating / random), the child card's pool daily-limit filter was counting every completion record for the chore — including bonus sub-task completions, which share the parent's chore_id but carry their own bonus_subtask_id.
  • With daily_completion_limit: 1, completing a single sub-task exhausted the parent's quota and the parent vanished from the active child's card before the remaining sub-tasks could be tapped.
  • Filter at taskmate-child-card.js:1758 now excludes records with a bonus_subtask_id, matching the existing pattern used by _renderChoreCard for the everyone-mode case.

Upgrading

HACS → TaskMate → Redownload, then restart Home Assistant. No config changes required. Existing rotation/alternating chores with sub-tasks will start behaving correctly immediately — no state migration involved.

Affected configurations

This bug only manifested for chores meeting all of these conditions:

• assignment_mode set to alternating or random (not everyone)
• Has at least one bonus sub-task
• daily_completion_limit set such that the bonus sub-task count was enough to hit the limit (most commonly daily_completion_limit: 1)

Everyone-mode chores were unaffected — that path already used the correct filter.

Full changelog: v3.9.2...v3.9.3

---

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.