Yeraze/meshmonitor

What's Changed

Bug Fixes

• Accept new nodeNum on same-device reboot — when firmware reboots with a different nodeNum, MeshMonitor now accepts it and merges the old node's metadata instead of rejecting it. The old approach caused identity mismatches where MeshMonitor used the old nodeNum while the firmware broadcast on the new one (#2106)
• Fix isLocked desync for node names changed outside MeshMonitor — node names changed via the Meshtastic app (or after factory reset) are now properly picked up. The isLocked flag was incorrectly blocking NodeInfo updates, the authoritative source for node identity (#2106)
• Prevent duplicate outgoing messages in chat (#2104) — closes #2027

New Features

• Per-node cooldown for geofence triggers — prevent repeated geofence alerts for the same node within a configurable time window (#2105) — closes #2103

Dependencies

• Bump mysql2 from 3.17.4 to 3.18.2 (#2102)
• Bump maplibre-gl from 5.18.0 to 5.19.0 (#2101)
• Bump @types/supertest from 6.0.3 to 7.2.0 (#2100)
• Bump pg and @types/pg (#2099)
• Bump globals from 17.3.0 to 17.4.0 (#2098)
• Bump production-dependencies group with 4 updates (#2097)
• Bump development-dependencies group with 3 updates (#2096)

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

🚀 MeshMonitor v3.7.6

📦 Installation

Docker (recommended):

docker run -d \
  --name meshmonitor \
  -p 8080:3001 \
  -v meshmonitor-data:/app/data \
  ghcr.io/yeraze/meshmonitor:latest

Upgrade: Pull the latest image and restart your container.

🚀 MeshMonitor v3.7.6

📦 Installation

Docker (recommended):

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

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