Skip to content

Yeraze/meshmonitor

v3.6.3 Feature

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

Published 3mo 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

Differentiate own vs others' tapback reactions by color.

Full changelog

What's Changed

Features

  • Differentiate own vs others' tapback reactions by color (#1950)

Bug Fixes

  • Add networking support to LXC template (#1954) - Fixes #1672
  • Consistent map pin click centering and popup positioning (#1953)
  • Use actual data tables for node packet type distribution (#1952)
  • Increase auto-responder script timeout from 10s to 30s (#1942)

Performance

  • Add server-side in-memory cache for link previews (#1944)

Other

  • Update deployment guide for accuracy (#1946)
  • Clean up LXC template build workflow release notes (#1945)
  • Translations update from Hosted Weblate - Russian (#1943)

Issues Resolved

  • #1672 - LXC deployment image/scenario on PM 9.1
  • #1929 - Short name incorrect
  • #1934 - Stations with icons as short name don't update on map
  • #1936 - Rounding to integers in graphs is still not fully fixed
  • #1949 - Window off screen again
  • #1951 - Traceroute results

🚀 MeshMonitor v3.6.3

📦 Installation

Docker (recommended):

docker run -d \
  --name meshmonitor \
  -p 8080:3001 \
  -v meshmonitor-data:/data \
  ghcr.io/Yeraze/meshmonitor:3.6.3

🧪 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.

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.

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]