MQTT Settings

MQTT (Message Queuing Telemetry Transport) allows a Meshtastic node with internet access to publish selected mesh traffic to an MQTT broker and optionally receive MQTT traffic and rebroadcast it onto the radio mesh.

MQTT is commonly used to connect separate RF areas, support web based maps, and allow limited communication when direct radio paths do not exist.

---

Caution:

Do not enable MQTT on solar or battery powered nodes unless you have confirmed reliable power and connectivity. MQTT requires maintaining an active internet connection and increases power draw.

When to Use MQTT

• Publishing node location and telemetry to maps
• Bridging separated RF areas together
• Supporting mobile users when RF coverage is limited

MQTT is optional. A healthy local mesh does not require MQTT to function.

Step 1: MQTT Module Configuration

MQTT settings are configured only on the node that has internet access. This node can use WiFi, Ethernet, or a phone connection.

• Enable MQTT: On

• Server Address: mqtt.nwimesh.net

• Username: meshdev

• Password: large4cats

• Root Topic: msh/US/IN/NWI

• TLS Enabled: Off

• MQTT Encryption: Optional. This is message level only

  • The “Encryption Enabled” option controls the “message-level” encryption – so the same encryption that’s used over LoRa is left in place when messages are uploaded to MQTT.

• JSON: Off unless required for integrations

Port and TLS

The relay listens on the standard MQTT port, 1883, as plain (non-TLS) MQTT. There is no TLS listener: port 8883 is closed, so TLS cannot work no matter how you configure it.

• Leave TLS Enabled switched off. This is the single most common reason a node silently never connects.
• Leave the server address as the bare hostname, with no port and no scheme: mqtt.nwimesh.net, not mqtt://mqtt.nwimesh.net or mqtt.nwimesh.net:1883. Meshtastic adds the port itself.
• If you turn TLS on against a plain broker the node fails with no useful error. That is the "TLS mismatch" listed under common failures below.

The credentials above are shared community credentials, published deliberately. They are not a secret and they do not protect anything: treat everything you uplink as public.

What the topics look like

Once your node is uplinking, its traffic appears under the root topic. Useful to know when you are debugging with a desktop MQTT client:

Topic	What it carries
msh/US/IN/NWI/2/e/LongFast/!<nodeid>	The normal protobuf-encoded mesh packets
msh/US/IN/NWI/2/json/LongFast/!<nodeid>	The optional JSON form, from nodes with JSON enabled
msh/US/IN/NWI/2/stat/<client>	Client status and last-will messages

!<nodeid> is the publishing node's hex ID. If you subscribe to msh/US/IN/NWI/# with any MQTT client using the credentials above, you should see traffic within a minute or two on a healthy mesh.

Connection behavior:

• WiFi or Ethernet nodes: Proxy to Client Off
• Phone connected nodes: Proxy to Client On

Step 2: Channel Uplink and Downlink

MQTT behavior is controlled per channel. Uplink and Downlink determine what traffic is published to MQTT and what traffic is rebroadcast onto RF.

• Uplink Enabled: Publishes radio traffic to MQTT
• Downlink Enabled: Subscribes to MQTT and rebroadcasts traffic on RF

Only enable Downlink if you have a very stable internet connection and intentionally want MQTT messages injected into your local radio mesh. Excess downlink traffic can overwhelm a small or dense mesh.

Recommended Baseline Configuration

This configuration is recommended for most users who want their node to appear on maps.

• MQTT Enabled
• Primary Channel Uplink Enabled
• Primary Channel Downlink Disabled
• OK to MQTT Enabled
• Ignore MQTT Disabled

Position Reporting for MQTT

MQTT maps rely on position reports. Position settings control how often and how accurately your node reports its location.

• Position Enabled: On
• Precise Location: Off
• Position Broadcast Interval: 1800 seconds for fixed nodes

Shorter intervals should only be used for mobile nodes when necessary.

Common Reasons MQTT Does Not Work

• MQTT module is disabled
• OK to MQTT is turned off
• Ignore MQTT is turned on
• Incorrect broker credentials
• TLS mismatch with the broker
• No internet connectivity

Summary

• MQTT is optional and not required for a working mesh
• Use MQTT on powered and stable nodes
• Enable Uplink cautiously and Downlink intentionally
• Protect credentials and use TLS when available

NWI Mesh Net: Community Network Terms & Legal Disclaimer

Important: By using the NWI Mesh Net MQTT relay (mqtt.nwimesh.net), you agree to the following terms. This service is provided as-is by volunteer hobbyists.

Experimental Nature of the Service NWI Mesh Net is a voluntary, non-commercial, experimental radio network. The MQTT relay is offered as a community resource for educational, testing, and emergency-preparedness purposes only. There are no guarantees of uptime, message delivery, privacy, or service availability.

User Responsibility and Liability You are the sole operator and controller of your Meshtastic node. You are fully responsible for all traffic, messages, and data originating from your Node ID.

• Liability: The volunteer administrators and coordinators of NWI Mesh Net are not liable for any damages, legal issues, hardware failures, privacy breaches, or other losses resulting from your use of this network.
• Indemnification: You agree to hold harmless NWI Mesh Net volunteers, administrators, and coordinators from any third-party claims, losses, or liabilities arising from your transmissions or use of the service.

Content and Section 230 Disclaimer This MQTT relay functions as a passive intermediary. Consistent with 47 U.S.C. § 230, the administrators do not monitor, curate, or assume any liability for the content of user messages. You are strictly prohibited from using this infrastructure for any illegal, harmful, or unlawful activities.

Regulatory Compliance You must ensure your node complies with all applicable laws and regulations, including:

• FCC Rules: Operation on 900 MHz ISM bands generally falls under FCC Part 15. If operating under an Amateur Radio license on amateur frequencies, you must comply with FCC Part 97.
• Encryption: On amateur radio frequencies (Part 97), you may not transmit messages encoded for the purpose of obscuring their meaning.
• Duty Cycle & Traffic: You are responsible for configuring Uplink/Downlink settings to prevent excessive traffic, channel congestion, or interference with other users.

Technical Management Administrators reserve the right to block any Node ID, user, or IP address that causes technical instability, traffic loops, broadcast storms, or malicious interference to the regional mesh.

Use of this MQTT service is entirely at your own risk. Always prioritize responsible operation, mesh health, and regulatory compliance.