This release fixes issues for SREs watching stability and regressions.
✓ No known CVEs patched in this version
Topics
Affected surfaces
Summary
AI summaryFixed MeshCore node crashes when contacts have null SNR/RSSI values and corrected repeater protocol bugs.
Full changelog
MeshMonitor v3.8.4
MeshCore hotfix release.
What's Changed
Bug Fixes
- fix: add defensive guards to MeshCore node rendering (#2158) — Closes #2157
- fix: MeshCore repeater serial protocol — three bugs (#2159)
Details
MeshCore Nodes crash (#2158):
Enabling "Show MeshCore" on the Nodes page crashed when contacts had null SNR/RSSI values. Added type validation in mapContactsToNodes() and defensive guards in the render path.
MeshCore Repeater protocol (#2159) — contributed by @NearlCrews:
Three bugs prevented MESHCORE_FIRMWARE_TYPE=repeater from working:
firmwareTypeenv var was ignored when connecting via API- Wrong line terminator (
\ninstead of\r) caused repeater to ignore all commands - Missing wake-up sequence and wrong response parsing for repeater CLI format
Issues Resolved
- #2157 — [BUG] Connecting Meshcore device results to "Nodes failed to Load" error
Full Changelog: https://github.com/Yeraze/meshmonitor/compare/v3.8.3...v3.8.4
🚀 MeshMonitor v3.8.4
📦 Installation
Docker (recommended):
docker run -d \
--name meshmonitor \
-p 8080:3001 \
-v meshmonitor-data:/data \
ghcr.io/Yeraze/meshmonitor:3.8.4
🧪 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
About Yeraze/meshmonitor
All releases →Related context
Related tools
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]