v6.1.0

A new Chore Board dashboard card, a Polish translation, and two fixes: cards that went empty when Home Assistant gave a sensor an area-prefixed id, and feature events that fired twice. 10 pull requests since v6.0.0.

Minimum Home Assistant is still 2024.7.0. Read Before you upgrade if you have automations on any of the 11 events listed there.

---

⚠️ Before you upgrade

• 11 notification events have new names. The feature event and the notification event for these types used to share a name, so automations triggered on them ran twice. The feature event keeps its name and now fires once. The event the notification system fires is now taskmate_<type>_notification:
  level_up, badge_earned, celebration, family_goal_reached, season_champion, streak_freeze_used, bounty_posted, wish_pledged, inspection_started, inspection_passed, auction_opened.
  • Most automations need no change. An automation on taskmate_level_up (including the bundled Level up blueprint) now runs once instead of twice.
  • If an automation reads recipients from one of these events, switch its trigger to the _notification event, e.g. taskmate_badge_earned_notification. If you used the recipients is not defined condition to filter out the duplicate, you can remove it.
  • All other notification types (taskmate_pending_chore_approval, taskmate_weekly_digest, …) keep their event names.

---

🆕 New features

🗂️ Chore Board card (#1017, PR #1019)

The admin panel's Today board, as a Lovelace card. Add it with Edit dashboard → Add card → TaskMate Chore Board, or:

type: custom:taskmate-chore-board-card
entity: sensor.taskmate_overview

• Grid: time periods down the side (morning to night, then Anytime) and children across the top, each with a done/total count. Every chore shows today's status: done, awaiting approval, to do or missed. Chores with a daily limit show progress like 1/3.
• Tap to complete: tapping a to-do or missed chore completes it for that child. If the chore has a button entity, the card presses it, so your automations on that button still fire. The chip turns green (or amber if the chore needs approval), the chore's completion sound plays, and a toast offers Undo.
  • Parents' Undo rejects the completion. A child can undo while their undo window is open.
  • Done and pending chips can't be tapped, so a stray tap on a shared tablet can't undo anyone's chore.
  • Photo, timed, open-ended and teamwork chores carry a small icon. Tapping one says to finish it on the child's card, because those need the child card's steps.
• This week: each child's done/total for the last 7 days, the same as the panel.
• One child: set children to a single child to get a simple list grouped by time of day, with a progress bar.
• Options (all optional, all available in the visual editor):

Option	Default	What it does
children	all	Child IDs to show
default_view	today	today or week
show_week	true	Show the This week tab
tap_to_complete	true	false gives a view-only board
show_legend	true	Show the status key under the board
hide_done_periods	false	Hide a time period once every chore in it is done
header_color, card_design, title		As on every TaskMate card. All six designs are supported.

• New sensor: sensor.taskmate_chore_board. Its state is the number of chores still to do today across all children, which is handy for automations ("anything left before bedtime?"). The board itself is in its chore_board attribute, which is not recorded in history. Because the board comes from a sensor rather than the admin-only panel connection, the card works on a non-admin login such as a wall tablet.

🇵🇱 Polish translation (PR #1023)

The integration, cards and admin panel are now fully translated into Polish. Home Assistant picks it up from your profile language. Cards and the panel now come in 10 languages. Thanks to @mborowy2.

---

🐛 Fixes

Cards empty when a sensor has an area-prefixed id (#1018, PR #1025)

Since Home Assistant 2026.6, a new entity on a device that has an area gets the area name in front of its id. If your TaskMate device is in an area, sensors added in v6.0.0 were created as e.g. sensor.familie_taskmate_bounties. The bounty card only looked for sensor.taskmate_bounties, so it showed No bounties right now while the admin panel listed open jobs. The chore auction card was affected the same way.

• sensor.taskmate_overview now publishes where each TaskMate sensor really lives (companion_entities, plus badge_entities for each child's badges sensor). Cards look sensors up there first and fall back to the default ids.
• Renaming a TaskMate sensor yourself now works too. The cards follow the new id straight away, without a restart.
• Nothing to do after upgrading. Cards that were empty fill in by themselves.

Feature events fired twice when their notification was sent (#1014, PR #1015)

See Before you upgrade above. Automations on taskmate_level_up, taskmate_badge_earned, taskmate_auction_opened and the other 8 events listed there now run once.

---

🧰 Maintenance

• Dependency updates: pytest-homeassistant-custom-component (PR #1020), hassfest action (PR #1021), ESLint (PR #1022), brace-expansion (PR #1024).
• PR template lists pl among the locales (PR #1026).
• README lists the Chore Board card and the correct card and language counts (PRs #1027, #1029).

---

🙏 Thanks

Thanks to @mborowy2 for the Polish translation, to the reporter of #1018 for the detail that tracked down the area-prefix problem, and to everyone in discussion #1016 who asked for the board on a dashboard.

Full changelog: v6.0.0...v6.1.0