Skip to content

v4.18.1-rc2

Pre-release
Pre-release

Choose a tag to compare

@Yeraze Yeraze released this 19 Nov 01:48
591fd29

MeshMonitor v4.18.1-rc2

Warning

This is a pre-release for testing. Do not use it in production unless you are helping test it.

Summary

You can now send from the Unified Messages page. Pick a channel, pick one sending node, and send, with replies, tapbacks and delivery status on Unified rows. Only nodes you hold send permission for, that are connected, and that can transmit on that channel appear in the sender list. Each send goes through one node, and the audit log records it without the message text. MeshCore gains Auto Resend: a message is resent until the repeaters you require have heard it. MeshCore channels and rooms can now be muted except for @mentions. Manual MeshCore actions (Poll Status, neighbours, time sync, fetch) now wait for the next transmit slot with a countdown instead of failing with "Too soon". Auto-pathfinding now waits for that slot too. Anonymous sending now needs an explicit admin opt-in. French, Russian and Chinese (Simplified) translations are back above 50%.

Upgrade notes

  • Anonymous sending is now off by default. If you gave the anonymous account permission to send messages, those sends now fail with AUTH_REQUIRED until an admin turns on Allow anonymous sending in Settings. v1 API sends are now audited.
  • The Meshtastic send route now has a rate limit (messageLimiter, 30 sends per minute per IP in production). This also covers the existing Channels and DM tabs.
  • Reverse proxies: manual MeshCore actions can now wait up to 180 s for a transmit slot. If you run behind nginx, set proxy_read_timeout to 300 s (see the reverse-proxy docs).

Features

  • Unified Messages send groundwork: rate limit, send audit and sender list (#3045 P1) by @Yeraze in #6492
  • Send composer on Unified Messages (#3045 P2) by @Yeraze in #6494
  • Reply, tapback and delivery status on Unified Messages (#3045 P3) by @Yeraze in #6496
  • MeshCore: Auto Resend until the required repeaters hear the message (#6240) by @Yeraze in #6488
  • Notifications: mute MeshCore channels and rooms except for @mentions (#6490) by @Yeraze in #6491
  • MeshCore: manual actions wait for the next transmit slot, with a countdown (#6493) by @Yeraze in #6497

Bug fixes

  • MeshCore: auto-pathfinding claims the transmit slot, and Unified replies keep the original message's scope (#6500) by @Yeraze in #6501

Security

  • Anonymous sending only by explicit opt-in, and v1 sends are now audited (#6499) by @Yeraze in #6502

Docs and i18n

  • MeshCore docs: Resend covers direct messages too, by @Yeraze in #6489
  • Machine-translated top-up for fr, ru and zh_Hans, by @Yeraze in #6495

Issues resolved

  • #3045 Unified Messaging: add Send capability with permissions and safeties
  • #6240 MeshCore: Auto Resend until required repeaters heard
  • #6490 Mute unless mentioned
  • #6493 Make manual commands cut to the front of the queue
  • #6499 Meshtastic send route: anonymous sending only by explicit opt-in; audit v1 sends
  • #6500 MeshCore: auto-pathfinding ignores the 60 s TX floor; Unified replies lose the parent's scope
  • #6498 Unified channels list exposes source names to channel-database-only readers (closed as intended, now documented)

Full changelog: v4.18.1-rc1...v4.18.1-rc2

🚀 MeshMonitor v4.18.1-rc2

📦 Installation

Docker (recommended):

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

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