Skip to content

Yeraze/meshmonitor

v4.11.4 Breaking

This release includes breaking changes for platform teams planning a safe upgrade.

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

Affected surfaces

breaking_upgrade

Summary

AI summary

Updates πŸ› Fixes, ✨ Features, and πŸš€ MeshMonitor v4.11.4 across a mixed release.

Full changelog

Patch release rolling up everything merged since v4.11.3.

πŸ”΄ Critical

  • PostgreSQL boot-loop fixed (#3639) β€” Postgres deployments could fail to start with tables can have at most 1600 columns. Update recommended for all Postgres users.

✨ Features

  • MeshCore role icons in the map + Direct Messages node lists (#3647)
  • MeshCore favorites pinned to the top of the Direct Messages list (#3620)
  • Marker spiderfying for overlapping nodes on Map Analysis + Unified maps (#3612)
  • Channel "overshadow" warning when a device channel shares its key with a differently-named Channel Database entry (#3644)
  • Traceroute packetId stored for cross-source trace correlation (#3623)

πŸ› Fixes

  • Node disconnects / TX failures since 4.11.x (stuck module-config fetch) (#3637)
  • Custom-LoRa-config primary channel no longer mislabeled "LongFast" (#3644)
  • TCP source reconnect shows the real per-source address (#3611)
  • Fictitious traceroute segments removed; incoming traceroutes visible again (#3622)
  • MeshCore hashtag #channel secrets derive correctly over plain HTTP-via-IP and at save time (#3606, #3607)
  • MeshCore Last Heard preserved across reconnect (#3645)
  • MeshCore new nodes populate Name/type/Position immediately when heard live (#3646)
  • Unified-map neighbor lines follow the merged node marker (#3642)
  • Adaptive node-type filter per connected source protocol (#3610)
  • Saner uncertainty for weight-dominated single-anchor position estimates (#3616)

πŸš€ MeshMonitor v4.11.4

πŸ“¦ Installation

Docker (recommended):

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

Track Yeraze/meshmonitor

Get notified when new releases ship.

Sign up free

About Yeraze/meshmonitor

All releases β†’

Related context

Earlier breaking changes

  • v4.13.0 Source‑scoped API endpoints now require an explicit `sourceId` parameter.
  • v4.13.0 Auto-Upgrade is retired; remove upgrade sidecar and related config.
  • v4.7.2 Route `destination` field now rejects non‑8‑hex nodeId or 64‑hex publicKey, returning HTTPβ€―400.

Beta — feedback welcome: [email protected]