What's New
Auto Delete by Distance
A new automation feature that automatically removes nodes beyond a configurable distance threshold from your home coordinate. Keep your node database focused on your local mesh.
- Home coordinate — Set your location manually or use your connected node's position
- Distance threshold — Configure the maximum distance (in km or miles) to keep nodes
- Configurable interval — Run cleanup every 6, 12, 24, or 48 hours
- Protected nodes — Favorited nodes and your local node are never deleted
- Activity log — Track what was deleted and when
- Run Now — Trigger an immediate cleanup from the Automation tab
Auto Traceroute Improvements
- Retraceroute After now accepts 0 hours, meaning nodes are always eligible for retraceroute on every cycle (#2269)
- Minimum interval raised to 3 minutes to prevent excessive mesh traffic
Bug Fixes
- Multi-database parity — Implemented missing PostgreSQL/MySQL methods for full feature parity across all backends (#2267)
- Auto-key repair — Fixed state tracking on PostgreSQL/MySQL and improved device DB awareness (#2264)
- System tests — Dev containers are now shut down before system tests to prevent port conflicts
Translations
- Updated Spanish translations (#2271)
PRs Included
- #2270 — feat: auto delete nodes by distance (#2266)
- #2272 — fix: auto-traceroute interval and expiration limits (#2269)
- #2267 — fix: multi-database parity
- #2264 — fix: auto-key repair on PostgreSQL/MySQL
- #2271 — Translations update from Hosted Weblate
- #2274 — chore: bump version to 3.9.4
Issues Resolved
🚀 MeshMonitor v3.9.4
📦 Installation
Docker (recommended):
docker run -d \
--name meshmonitor \
-p 8080:3001 \
-v meshmonitor-data:/data \
ghcr.io/Yeraze/meshmonitor:3.9.4🧪 Testing
✅ All tests passed
✅ TypeScript checks passed
✅ Docker images built for linux/amd64, linux/arm64, linux/arm/v7
📋 Changes
See commit history for detailed changes.