Description

Messages appear briefly in the LongFast channel view then disappear approximately 1 minute after arrival. The message is preserved in the MQTT broker, physical nodes, and third-party clients — only MeshMonitor drops the displayed entry.

Steps to Reproduce

1. Run MeshMonitor with multiple sources connected simultaneously (e.g. several direct MQTT sources + a BLE-forwarding node)
2. Send or receive a LongFast channel message
3. Observe message appear in the channel view
4. Wait ~60 seconds — message disappears from the channel view

Expected Behavior

Message remains visible in channel history after initial display.

Actual Behavior

Message vanishes from the channel view after ~1 minute. MQTT broker, physical nodes, and third-party clients all retain the message correctly.

Environment

• MeshMonitor version: v4.11.5
• Source configuration: Multiple direct MQTT sources (pointing to third-party MQTT host) + one T096 nRF52 node connected over Bluetooth using the built-in broker/forwarder
• Total sources: 5+ (Unified, Main MQTT, lilygo T3S3, T096, Home mqtt, Canadaverse bridge)

Suspected Cause

Packet-ID-based deduplication across multiple sources. The same packet may arrive first via a direct MQTT source (message displayed), then arrive again ~1 minute later via the BLE-forwarding T096 node (which relays with latency). The second arrival appears to remove the already-displayed message rather than being silently ignored.

This is potentially the same class of issue as #2741 (traceroutes evicting real DMs).

Authored by NodeZero 0️⃣