Mqttwarn
Mqttwarn is a command-line tool for home automation users that subscribes to Message Queuing Telemetry Transport (MQTT) topics and notifies pluggable services.
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
62/100 Good
- Maintained
- 65last commit 122 days ago
- Popular
- 60984 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
- Security check
- 83no serious findings, 2 minor, CI, tests
Based on 4 of 5 factors.
Availability: platform listings confirmed today, links checked 20 days ago
- GitHub stars
- 984
- Open issues
- 41
- Last commit
- 2026-07-22
- Latest release
- 0.36.1
- License
- EPL-2.0
- Activity
- stale
Checked 6 days ago - source: GitHub (mqtt-tools/mqttwarn)
Resources & Compatibility
Requirements not published yet.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Make the starter config files Run "mqttwarn make-config > mqttwarn.ini" and "mqttwarn make-udf > udf.py" to create the main config and the optional custom-code file. Without these files, mqttwarn has no settings to read and no place to put custom Python helpers. source
- Set the broker and output rules In mqttwarn.ini, set the MQTT broker's hostname and port, then use launch and targets to choose which message handlers run and where messages go, such as a log file or log output. If this points to the wrong broker or omits a target, messages will not be delivered anywhere. source
- Run Docker with config and broker If you use Docker (a packaged app container), mount your folder with mqttwarn.ini into /etc/mqttwarn and connect the container to the Mosquitto broker, as in the example. If the config is not mounted or the broker is unreachable, the container starts but cannot find your rules or any messages. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How do I create mqttwarn's initial configuration files?
Run "mqttwarn make-config > mqttwarn.ini" and "mqttwarn make-udf > udf.py". Without these files, mqttwarn has no settings to read and no place for custom Python helpers.
Where do I set the MQTT broker and message destinations?
In mqttwarn.ini, set the broker hostname and port, then use launch and targets to choose which handlers run and where messages go. If the broker is wrong or a target is omitted, messages will not be delivered.
What does the Docker setup need so mqttwarn can find its rules and broker?
Mount the folder containing mqttwarn.ini into /etc/mqttwarn and connect the container to a broker such as Mosquitto. If the config is not mounted or the broker is unreachable, the container starts but cannot find rules or messages.
What notification services can mqttwarn forward to?
It supports over 70 notification handler plugins and integrates with the Apprise notification library for additional targets.
Answers sourced from github.com, github.com, github.com, selfhost.directory
Community
Collected 49 days ago - public community threads