MeshMonitor v4.14.1-rc3 — Movement Triggers

⚠️ Pre-release. This is a release candidate for 4.14.1. It ships on the :dev Docker tag, not :latest. Run it if you want the changes early and can tolerate rough edges; report anything you hit.

Summary

This candidate adds two Automation Engine triggers built for stationary GPS fleets — rooftops, towers, and gateways you want to hear about the moment they move. Pair either with a Send-message or Notify action for a tamper / theft alert.

• Left home is the primary theft detector. It fires when a watched node drifts farther than a threshold (default 300 m) from a home anchor MeshMonitor learns per node and stores in the database — so a restart never silently re-homes a node that was carried off. The anchor is seeded from position-history inliers (dropping GPS spider-lines), gently self-corrects while the node sits still, and can be reset from history at any time.
• Became mobile is a coarser companion: it fires when a hand-selected node's mobility flag flips from stationary to moving.

Also in this candidate: you can now set a node's private key from Device Configuration — for restoring an identity from backup or moving it to replacement hardware — and node purges now clean up the automation bookkeeping they used to leave behind.

Features

• Left-home / tamper trigger — per-(automation, node) home anchors persisted across restarts, history-inlier seeding, EMA self-correction near home, a Reset homes from history action, a stationary-first node picker, and {{ node.longName }} / {{ node.nodeId }} message tokens. (#4648)
• Became-mobile trigger — fires on a stationary → mobile flip (MeshMonitor's >100 m position-history heuristic) for hand-selected nodes. (#4648)
• Set a node's private key from Device Configuration — local device only, X25519; on a change MeshMonitor derives the matching public key and writes both, so the node can never be left advertising a key that no longer matches its secret. Guarded behind a confirmation that spells out the impersonation / duplicate-key risk. (#4632, #4654)

Fixes

• Node purge now clears its automation bookkeeping — auto-favorite targets and assignments (#4633), and auto-traceroute / auto-time-sync allowlists (#4630), so a re-added node no longer inherits stale state.
• MeshCore: a lost out_path acknowledgement is treated as success, not failure. (#4625)

Docs

The CHANGELOG now covers the full 4.14.1 rc1 → rc3 history, and the feature guides were reconciled with what shipped across the candidates (Analyzer Observer static MQTT auth, the new Device Configuration security section, position-estimation anchors, and the theme chart color scales).

Upgrade

Docker :dev users receive this automatically.

🚀 MeshMonitor v4.14.1-rc3

📦 Installation

Docker (recommended):

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

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