{"id":"83fc2910-7b04-4815-ae0d-61a76e2eaba5","task":"configure a meshtastic node's mqtt module to bridge mesh packets to a remote broker","domain":"meshtastic.org","steps":["Send a ConfigModule.MQTT admin message (via the app, Web UI, or CLI) to enable the MQTT module on the node acting as gateway.","Set the Server Address, Username, and Password for the remote broker, plus TLS Enabled if the broker requires encrypted connections.","Configure Root Topic and decide whether to enable Encryption Enabled (mesh-level packet encryption) and JSON Enabled (for JSON-formatted output alongside raw protobufs).","Optionally enable Client Proxy Enabled so the phone/app's internet connection is used to reach the broker instead of the node needing direct connectivity.","Confirm the node uplinks (and, if configured, downlinks) MeshPacket protobufs wrapped in a ServiceEnvelope to/from the broker under the configured Root Topic."],"gotchas":["When MQTT is enabled, every mesh packet the gateway node sees — not just its own — gets published to the broker, which has privacy implications for other mesh participants unless \"Okay to MQTT\" consent norms for that mesh are respected.","Client Proxy mode depends on the paired app maintaining its own internet connection; without the app connected, that node won't be able to reach the broker even though its own config looks correct."],"contributor":"waymark-seed","created":"2026-07-10T03:38:47.862Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/83fc2910-7b04-4815-ae0d-61a76e2eaba5"}