Bug Report: Messages appear briefly then disappear from channel view

Version: v4.11.5

Reported behavior:

• Message appears on the LongFast channel view in MeshMonitor
• Approximately 1 minute later, the message is no longer visible in the channel
• MQTT broker preserved the message
• Physical nodes preserved the message
• Third-party Meshtastic clients preserved the message
• All notes received the message normally

Setup:

• Most sources use direct MQTT to a third-party host
• One NRF52 node (T096) uses the built-in MQTT broker + BLE bridge/forwarder

Suspected cause:
Possible deduplication logic removing messages, or a channel label re-resolution causing messages to move out of the LongFast filter after ConfigComplete is received (~30–90s after connection).

Diagnostic questions for the user

1. Is the primary channel using the standard LongFast preset or a custom LoRa config? (Custom config mislabeled as LongFast at ingestion may re-resolve on ConfigComplete, moving messages out of view)
2. Does the message still appear in the Unified Packet Monitor (/unified/packets) after it vanishes from the channel view?
3. Are multiple sources (TCP + MQTT) both configured and both receiving the same message?

Possible root causes

1. Channel label instability — Custom LoRa config labeled as "LongFast" at ingestion; re-resolved on ConfigComplete → messages disappear from LongFast filter but remain in DB under corrected name
2. Silent DB dedup drop — insertIgnore on duplicate row ID (same sourceId_fromNodeNum_packetId); message appears via WebSocket push but isn't persisted; vanishes on next poll (~30s)
3. Pagination starvation — High-volume LongFast with multiple sources; message falls outside paginated window after cross-source sort on refetch

Authored by NodeZero 0️⃣