Yeraze/meshmonitor

v3.10.4 Bugfix

This release fixes issues for SREs watching stability and regressions.

Published 2mo Monitoring & Metrics

✓ No known CVEs patched

✓ No known CVEs patched in this version

Topics

meshcore meshtastic mqtt

Summary

AI summary

Fixed reconnect flood and phantom TCP connection issues for WiFi‑connected devices.

Full changelog

Fix reconnect flood on WiFi-connected devices — Schedulers now wait for configComplete before starting, with staggered initialization and TCP backpressure handling to prevent overwhelming WiFi-connected Meshtastic devices (#2479, closes #2474)
Detect and recover from phantom TCP connections — Adds buffer staleness detection and forced reconnect when data arrives but no messages are parsed, fixing a long-standing issue with USB serial bridges losing inbound data after hours (#2480)
Polygon geofence trigger button never enables — Fixed Leaflet's double-click zoom consuming the polygon finalization event; polygon shape now updates progressively as vertices are added (#2481)
Permissions swap fails on SQLite CHECK constraint (#2476)

Expanded repository test coverage — 363 new tests across all database backends (SQLite, PostgreSQL, MySQL) covering nodes, channels, notifications, neighbors, traceroutes, ignored nodes, channel database, and settings repositories (#2477)
Flaky system test fix — Added retry logic to config import CSRF/login step (#2479)
Translation updates from Hosted Weblate (#2459)

Full Changelog: https://github.com/Yeraze/meshmonitor/compare/v3.10.3...v3.10.4

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track Yeraze/meshmonitor

Get notified when new releases ship.

About Yeraze/meshmonitor

v4.7.2 Route `destination` field now rejects non‑8‑hex nodeId or 64‑hex publicKey, returning HTTP 400.