From 81694e7ab3431f46a8458e42fd9ec6614238095d Mon Sep 17 00:00:00 2001 From: Jack Kingsman Date: Mon, 2 Mar 2026 19:15:28 -0800 Subject: [PATCH] Fix an e2e test and add a warning about nodes not showing up on community listings --- .../settings/SettingsMqttSection.tsx | 18 ++++++++++++++++++ tests/e2e/specs/contacts.spec.ts | 2 +- 2 files changed, 19 insertions(+), 1 deletion(-) diff --git a/frontend/src/components/settings/SettingsMqttSection.tsx b/frontend/src/components/settings/SettingsMqttSection.tsx index 2f3aba3..9418077 100644 --- a/frontend/src/components/settings/SettingsMqttSection.tsx +++ b/frontend/src/components/settings/SettingsMqttSection.tsx @@ -103,6 +103,24 @@ export function SettingsMqttSection({ . +
+ Outgoing messages (DMs and group messages) will be reported to private MQTT brokers in + decrypted/plaintext form. The raw outgoing packets will NOT be reported to any MQTT broker, + private or community. This means that{' '} + + your advertisements will not be reported to community analytics (LetsMesh/etc.) due to + fundamental limitations of the radio + {' '} + — you don't hear your own advertisements unless they're echoed back to you. + So, your own advert echoes may result in you being listed on LetsMesh/etc., but if + you're alone in your mesh, your node will appear as an ingest source within LetsMesh, + but will not report GPS data/etc. that would otherwise be captured by an advertisement, as + we faithfully report only traffic heard on the radio (and don't reconstruct synthetic + advertisement events to submit). Rely on the “My Nodes” or view heard packets to + validate that your radio is submitting to community sources; if you're alone in your + local mesh, the radio itself may not appear as a heard/mapped source. +
+ {/* Private MQTT Broker */}