Skip to content

How I Use ntfy in My Homelab

One of the first services I deploy on a new server is ntfy. It is lightweight, easy to self-host, and has become the central notification hub for my entire homelab.

Rather than logging into multiple applications every day to check for updates or problems, I let my servers notify me. Most notifications arrive on my phone within a second or two, allowing me to deal with issues immediately, whether I'm at home or travelling.

This page isn't intended as an installation guide (see the ntfy Docker Compose Deployment Guide for that). Instead, it explains how I actually use ntfy in my day-to-day homelab.

Why I Chose ntfy

Before using ntfy I often found myself asking questions like:

  • Has a Docker image been updated?
  • Did last night's backup complete?
  • Has that website changed yet?
  • Is there a hurricane warning for the Caribbean?
  • Has one of my servers gone offline?

Now I don't have to check.

My servers tell me.

My Notification Philosophy

I try to follow one simple rule:

If I would normally check something manually, it should probably become an ntfy notification instead.

The fewer dashboards I need to visit each day, the better.

Docker Image Updates (DIUN)

One of my most useful notifications comes from DIUN (Docker Image Update Notifier).

Whenever a Docker image receives an update, I receive a notification similar to:

Docker Update Available

paperless-ngx
New image available

Current:
2.17.1

Latest:
2.18.0

This allows me to choose when to update rather than discovering outdated containers weeks later.

Website Change Detection

I use ChangeDetection.io to monitor websites that I don't want to keep checking manually.

Examples include:

  • software releases
  • government announcements
  • documentation updates
  • websites that rarely change

When a monitored page changes, ntfy immediately sends a notification.

Personal Reminder System

I also use ntfy together with Mind.

Rather than relying on calendar reminders, I schedule messages that are genuinely useful.

Examples include:

Renew domain

Check UPS battery

Review backups

Doctor appointment tomorrow

These reminders appear as push notifications on my phone.

Backup Notifications

My automated backup scripts send notifications when they finish.

Successful backup:

Nightly Backup Completed

Server:
micropc

Duration:
12 minutes

Status:
Successful

If a backup fails, I receive an alert immediately rather than discovering the problem days later.

Home Assistant Notifications

Home Assistant is another major source of notifications.

Examples include:

  • automation failures
  • sensor alerts
  • weather notifications
  • device status
  • system warnings

Because Home Assistant supports ntfy directly, creating new notifications is straightforward.

Hurricane Monitoring

Living in the Dominican Republic means tropical weather is something I monitor closely.

Home Assistant watches NOAA hurricane activity and sends notifications whenever the official hurricane outlook changes.

I also plan to integrate notifications from the Dominican meteorological service so that I receive both international and local weather alerts.

Server Monitoring

While Netdata provides excellent dashboards, I don't spend all day looking at dashboards.

Instead, I prefer dashboards for investigation and ntfy for notification.

If something important happens, I want my phone to tell me first.

Typical Notification Topics

Rather than placing everything into a single topic, I separate notifications into logical categories.

For example:

docker-updates
backups
weather-alerts
weather-local
mind
changedetection
homeassistant

This makes it easier to subscribe only the devices that need each type of notification.

Why I Self-Host ntfy

There are many cloud notification services available, but self-hosting gives me:

  • complete control
  • no subscription fees
  • no dependence on third-party services
  • unlimited notifications
  • excellent privacy

Once installed, ntfy requires very little maintenance.

What I Still Plan to Add

My notification system continues to evolve.

Future ideas include:

  • UPS power failure alerts
  • Internet outage detection
  • SMART disk warnings
  • SSL certificate expiry reminders
  • Docker backup verification
  • Synology storage alerts
  • Low disk space warnings
  • CPU temperature alerts

The aim is to be informed only when I need to take action.

Lessons Learned

The biggest lesson I've learned is that notifications should be useful, not noisy.

If a system sends too many messages, they quickly become background noise and get ignored.

I try to ensure that every ntfy notification answers one simple question:

"Do I need to do something?"

If the answer is no, it probably doesn't need to be a notification.

Related Guides

Final Thoughts

ntfy has become one of the most valuable services in my homelab. It quietly sits in the background connecting dozens of applications, scripts and automations, ensuring that important events come to me instead of me having to go looking for them.

For such a small container, it has probably saved me more time than almost any other application I run.