-
Notifications
You must be signed in to change notification settings - Fork 2
Multi Parent Approval Routing
tempus2016 edited this page Jul 22, 2026
·
2 revisions
By default every approval buzzes every parent. Two other modes are available via the parent_routing setting, for households where that gets noisy.

| Mode | Behaviour |
|---|---|
all (default)
|
Every enabled parent, as before |
home |
Only parents whose presence entity says they're here |
round_robin |
One parent per notification, rotating |
For home mode, give each parent a presence entity in the notification settings — a device_tracker.*, a person.*, or anything that reads home / on / true / present.
An unseen approval is worse than a redundant buzz, so every failure path widens the audience rather than narrowing it:
- Nobody home → everyone is told, not nobody.
- No presence entity set → that parent counts as available and is never silently cut out.
- Broken or unavailable presence sensor → fails open.
- Round-robin state pointing at a deleted parent → starts from the beginning rather than wedging.
Round-robin position is tracked per notification type, so a reward claim doesn't advance the chore-approval rotation. Each kind of approval keeps its own place in the queue.
None of this touches child notifications. A reminder for a child must always reach that child — routing applies only to the parent-facing approvals.
- Notifications — the full notification system, actionable callbacks and bus events
- Quiet Hours — per-child do-not-disturb windows
- Reminder Escalation — nudge → reminder → parent alert
- Parent Access — giving a second parent control without HA admin rights
-
Settings — where
parent_routinglives