MeshMonitor v4.12.3

MeshMonitor 4.12.3 adds two new capabilities: a reusable Pause action for the Automation Engine (build custom delayed sequences like "message trigger → pause → send message"), plus a dedicated configurable pre-send delay on Auto-Acknowledge for both Meshtastic and MeshCore. It also brings the Meshtastic Position History map feature to MeshCore — per-node movement trails with a configurable retention window. On the reliability side, this release closes out a batch of MeshCore fixes: deleted contacts no longer get resurrected by the next sync, the saved-regions/default-scope view no longer spams background requests and throws a spurious error banner, GPS position from a telemetry poll now updates Contact Details, and the Virtual Node bridge now correctly forwards delivery ACKs and real hop counts to a connected companion. The MeshCore "Direct Messages" tab and its permission are renamed to "Node Details" to reflect that they also gate node-detail info, not just DMs. Traceroute's "last traced" age can no longer go negative when a node's device clock is ahead of real time — an ingest-time clamp plus a migration repair existing rows. A sticky section-nav bug that scrolled configuration-page navigation behind the fixed header is fixed, and duplicate WARN-level log spam from security/telemetry checks on large meshes has been quieted.

Features

• Automation Engine "Pause" action + configurable Auto-Ack pre-send delay — #3879, closes #3876
• MeshCore node position-history movement trails on the map — #3877, closes #3852
• MeshCore auto-acknowledge {SCOPE} token — #3866, closes #3865

Bug Fixes

• MeshCore: deleted contact resurrected on the next sync — #3882, closes #3878
• MeshCore: intermittent "Failed to load saved regions" banner — #3881, closes #3880
• MeshCore Virtual Node: DM ack + inbound hop count bridging — #3875, closes #3869, #3871
• Sticky section-nav scrolled behind the fixed header — #3873, closes #3872
• MeshCore: "Direct Messages" tab/permission renamed to "Node Details" — #3870, closes #3867
• Duplicate WARN log spam from security/telemetry checks — #3864, closes #3863
• MeshCore: GPS position from a telemetry poll now persists to Contact Details — #3862, closes #3861
• Traceroute "last traced" could show a negative age — #3860, closes #2768

Testing

• Happy-path tests for channel reorder + MeshCore delete — #3857 (thanks @temalo!)

Documentation

• release: 4.12.3 — version bump + docs catch-up — #3883

Issues Resolved

#2768, #3852, #3861, #3863, #3865, #3867, #3869, #3871, #3872, #3876, #3880, #3697

Full Changelog

https://github.com/Yeraze/meshmonitor/compare/v4.12.2...v4.12.3

🚀 MeshMonitor v4.12.3

📦 Installation

Docker (recommended):

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