Skip to content

Kuma ntfy alerts: DOWN priority dropped to default (3) #80

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mathewcsims merged 2 commits into from
Aug 9, 2026
Merged

Kuma ntfy alerts: DOWN priority dropped to default (3) #80

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3b84e38
Kuma ntfy alerts: DOWN priority dropped to default (3)
mathewcsims Aug 9, 2026
750fba6
Merge branch 'main' into kuma-ntfy-down-priority-default
mathewcsims Aug 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 8 additions & 6 deletions SETUP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3437,12 +3437,14 @@ monitors; attach it per-monitor where a phone push is wanted (first user:
`Eddie (host)`, which carries both Discord and ntfy). Config: server
`https://ntfy.mathewcsims.uk`, topic `alerts`, auth method **access token**
using the same write-only `PUBLISHER_TOKEN` from the "Ntfy" Pass item that
Apprise embeds. Priorities are deliberate: **3 (default) for UP, 4 (high)
for DOWN** — never 5/max, because max bypasses phone Do-Not-Disturb and the
Eddie monitor fires a DOWN/UP pair *every night* during the NAS's scheduled
04:00–06:00 power-off window (see Known values). Kuma's provider defaults
would have been 4/5 (`ntfyPriorityDown` falls back to `priority + 1`,
capped at 5 — `server/notification-providers/ntfy.js` at this tag).
Apprise embeds. Priorities are deliberate: **3 (default) for both UP and
DOWN** (Mathew's call, 2026-08-09) — the Eddie monitor fires a DOWN/UP
pair *every night* during the NAS's scheduled 04:00–06:00 power-off window
(see Known values), so anything louder would be nightly noise, and 5/max
would bypass phone Do-Not-Disturb. Kuma's provider defaults would have
been 4/5 (`ntfyPriorityDown` falls back to `priority + 1`, capped at 5 —
`server/notification-providers/ntfy.js` at this tag), so both fields are
set explicitly.
Verified live via the `testNotification` Socket.IO event: test push arrived
on the `alerts` topic.

Expand Down