Skip to content

Yeraze/meshmonitor

v3.10.1 Feature

This release adds 3 notable features 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

Add a UNIQUE constraint to notification preferences userId, fixing 500 errors on save.

Full changelog

Changes since v3.10.0

Features

  • Dead nodes report with bulk delete on Security tab (#2414)
  • Icon style toggle — switch between Lucide and emoji sidebar icons (#2420)
  • API exercise test validates response structure on all 3 backends (#2422)

Bug Fixes

  • Channel database no longer shadows device channels with same PSK (#2415)
  • System backup history queries use wrong column names (#2421)
  • Left-align all packet monitor table columns, fix missing Date colgroup (#2428)
  • Add UNIQUE constraint to notification preferences userId — fixes 500 on save (#2429)
  • Auto-mark messages as read when viewing channel or DM — fixes persistent unread indicator (#2430)

🚀 MeshMonitor v3.10.1

📦 Installation

Docker (recommended):

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

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

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]