Skip to content

Yeraze/meshmonitor

v3.8.3 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

Fixed MeshCore unable to receive incoming messages.

Full changelog

MeshMonitor v3.8.3

What's Changed

Bug Fixes

  • fix: resolve MeshCore display issues on Nodes page (#2151) — Closes #2154
  • fix: enable receiving incoming messages on MeshCore companion devices (#2150) — Closes #2149

Refactoring

  • refactor: reorganize Settings page into focused sections (#2148)
  • refactor: frontend review batch 1 — shared modal, toast theming, accessibility (#2152)
  • refactor: frontend review batch 2 — design tokens, CSS split, lucide icons (#2153)
  • refactor: frontend review batch 3 — error boundaries, context splitting (#2155)

Features

  • feat: add favorite lock toggle and filter (#2147)

Documentation

  • docs: add better-sqlite3 rebuild troubleshooting to LXC guide (#2146)

Issues Resolved

  • #2149 — [BUG] Meshcore Messaging only sends but cannot receive
  • #2154 — [BUG] Telemetry Dashboard Search Broken

Full Changelog: https://github.com/Yeraze/meshmonitor/compare/v3.8.2...v3.8.3

🚀 MeshMonitor v3.8.3

📦 Installation

Docker (recommended):

docker run -d \
  --name meshmonitor \
  -p 8080:3001 \
  -v meshmonitor-data:/data \
  ghcr.io/Yeraze/meshmonitor:3.8.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]