Skip to content

Yeraze/meshmonitor

v3.11.0 Feature

This release adds 1 notable feature for engineering teams evaluating rollout.

Published 2mo Monitoring & Metrics
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

meshcore meshtastic mqtt

Summary

AI summary

Added GeoJSON/KML/KMZ overlay layer support with automatic conversion and auto‑discovery.

Full changelog

What's Changed

New Features

  • GeoJSON/KML/KMZ overlay layer support — Upload geospatial files as map overlays with per-layer styling, visibility toggles, and simplestyle-spec support. KML/KMZ files are automatically converted to GeoJSON on upload. Files placed in /data/geojson/ are auto-discovered. (#2488, closes #2487)

Bug Fixes

  • Duplicate cron jobs after reconnects — Timer triggers (auto-welcome, scheduled scripts) fired multiple times after device reconnects due to callback accumulation in the configComplete handler (#2489)
  • Audit log FK constraint on channel migration — Channel migration at startup used userId 0 which doesn't exist, causing SQLITE_CONSTRAINT_FOREIGNKEY error (#2486, reported in #2425)

New Dependencies

  • @tmcw/togeojson — KML to GeoJSON conversion
  • @xmldom/xmldom — XML parsing for KML
  • jszip — KMZ (ZIP archive) extraction

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

View diff on GitHub

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

Share on X Share on Bluesky

Track Yeraze/meshmonitor

Get notified when new releases ship.

Sign up free

About Yeraze/meshmonitor

All releases →

Related context

Earlier breaking changes

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

Beta — feedback welcome: [email protected]