Configuration: Notifications

ChoreOps sends Home Assistant mobile notifications to keep assignees and approvers informed about chore, reward, and points activity.

---

What you can configure

You can control notifications at two levels:

1. Per-user delivery (which device/service receives messages)
2. Per-chore moments (which chore events trigger reminders)

Tip

Keep high-signal notifications on (overdue, disapproval, reminder) and disable low-signal events for routine chores.

---

Notification event groups

Chore events

Event	Typical recipient	Action buttons	Auto-clear
Chore Claimed	Approver	Approve / Disapprove / Remind	Yes
Chore Approved	Assignee	No	No
Chore Disapproved	Assignee	No	Yes
Chore Now Due	Assignee	Claim	Yes
Chore Reminder	Assignee	Claim	Yes
Chore Overdue	Assignee + Approver	Claim (assignee), Complete/Skip/Remind (approver)	Yes
Chore Missed	Assignee + Approver	No	No

Reward events

Event	Typical recipient	Action buttons	Auto-clear
Reward Claimed	Approver	Approve / Disapprove / Remind	Yes
Reward Approved	Assignee	No	Yes
Reward Disapproved	Assignee	No	Yes

Gamification events

Examples include badge, achievement, challenge, bonus, and penalty notifications when those features are enabled.

---

Due-date notifications explained

Chore due timing uses separate notification moments:

• Chore Now Due: sent when the due window opens
• Chore Reminder: sent before the due time
• Chore Overdue: sent after the due time passes

For one chore and one assignee, these three messages behave as one collapsing notification family:

• Chore Reminder replaces Chore Now Due
• Chore Overdue replaces either earlier transient message
• only the latest valid transient state should remain on the device

Example timeline for a chore due at 5:00 PM with common defaults:

• 4:00 PM → Chore Now Due
• 4:30 PM → Chore Reminder
• 5:00 PM → Chore Overdue (if still incomplete)

If the chore is claimed, approved, missed, reset, skipped, or deleted, stale transient due-state prompts are cleared so outdated action buttons do not remain on the device.

Rotation overdue with steal available

When a Chore uses rotation and overdue handling is set to allow steal:

• The current turn holder still receives a normal overdue message
• Other assignees can receive a special overdue message that clearly says the Chore is available to steal
• Approver overdue messaging and action buttons stay the same

Note

This special message is only used for overdue rotation chores with steal enabled.

---

Action buttons

Approver actions

• Approve
• Needs Work / Disapprove
• Complete (for overdue workflows)
• Skip (reschedule overdue chore)
• Remind in 30 min

Assignee actions

• I Did It / Claim (claim from due/reminder/overdue notifications)

---

Configure notification delivery per user

1. Go to Settings → Devices & Services → ChoreOps → Configure
2. Open Manage User
3. Edit a user profile
4. Set Notification Service (for example notify.mobile_app_phone)
5. Save

Leave the notification service blank to disable direct notifications for that profile.

---

Configure notification tap URL

When a push notification is tapped, the Home Assistant Companion App opens your last-viewed screen by default. You can set a custom destination per user so tapping a notification navigates directly to the relevant dashboard.

Two URL fields are available in each user's Admin and approval options section:

Field	Purpose	Example
Notification tap URL	Used for notifications about the user's own activity (chore approved, badge earned, points awarded)	/lovelace/my-chores
Approval notification tap URL	Used for approval-request notifications (chore or reward claimed, needs review). Only shown when Can approve is enabled.	/lovelace/approval-center

1. Go to Settings → Devices & Services → ChoreOps → Configure
2. Open Manage User → Edit a user profile
3. In the Admin and approval options section, enter the dashboard URL relative to your Home Assistant instance (e.g., /lovelace/0) or an absolute URL
4. Leave blank for the default Companion App behavior (opens last screen)

Tip

• A user who is both an assignee and an approver can set different URLs for each role
• Relative paths like /lovelace/approval-dashboard work with the Companion App
• Action buttons in notifications are unaffected — the tap URL is only used when tapping the notification body itself

---

Configure per-chore reminder behavior

1. Open Manage Chore in the ChoreOps config flow
2. Edit the target chore
3. Configure due-window, reminder, and overdue notification options
4. Save

This lets you keep reminders on for high-priority chores while silencing routine chores.

---

Language behavior

Notification text uses each recipient’s configured user language.

• Mixed-language households are supported
• Missing translations fall back to English
• Titles, body text, and action labels are localized

Set language in Manage User for each profile.

---

Mobile app requirements

To receive actionable notifications:

• Install the Home Assistant Companion App (iOS/Android)
• Sign in to your Home Assistant instance
• Allow notification permissions
• Use the matching notify.mobile_app_* service in the user profile

---

Troubleshooting

Not receiving notifications

• Confirm user has a valid notification service
• Confirm mobile app is installed and logged in
• Confirm notification permission is enabled on device
• Confirm chore notification options are enabled for that chore

Wrong language

• Check user profile language
• Save profile and retry a notification event

Action buttons do nothing

• Confirm notification came from Companion App (not browser push)
• Update Companion App to a recent version

Why did one due message replace another?

• This is expected for chore due timing
• Chore Now Due, Chore Reminder, and Chore Overdue are designed to collapse to the newest valid message for that chore

---

Related documentation

• Configuration: Users
• Configuration: Chores
• Advanced: Chores
• Technical: Notifications

---

Last Updated: June 2026 (notification tap URL per user)