Skip to content

Yeraze/meshmonitor

v3.8.0 Feature

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

Gateway OTA firmware updates (experimental) are now available via a UI wizard in System Settings.

Full changelog

MeshMonitor v3.8.0

Highlights

Gateway OTA Firmware Updates (Experimental) — Administrators can now check for, download, and flash Meshtastic firmware updates directly from the MeshMonitor UI via a step-by-step wizard in System Settings. Supports Stable, Alpha, and custom firmware URLs with automatic config backup, live progress streaming, and hardware-matched binary selection. Docker deployments only.

New Features

Bug Fixes

  • Disable OTA firmware updates on Tauri desktop builds (#2120)
  • Prevent auto-favorites from overriding manual favorites (#2115) — Closes #2111

Documentation

  • Message delivery status icon documentation and confirmed CSS fix (#2121) — Closes #2118
  • Add Utilization Alert to user scripts gallery (#2112) — Closes #2109

Full Changelog: https://github.com/Yeraze/meshmonitor/compare/v3.7.6...v3.8.0

🚀 MeshMonitor v3.8.0

📦 Installation

Docker (recommended):

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

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