Skip to main content
COMMUNITY INFRASTRUCTURE • RADIO OBSERVATIONS • OPTIONAL INTERNET CONNECTIVITY

Northern Michigan Mesh MQTT

An independent MQTT broker for Meshtastic packet integrations and MeshCore observer reporting. Both technologies can contribute data, but their message formats, radio protocols and reasons for using MQTT are different.

FULL MQTT SERVER URL · MESHCORE OBSERVERmqtts://mqtt.northernmichmesh.org:8883Copy the whole value, including mqtts:// and :8883.
MQTT PORT8883
CONNECTIONTCP + TLS

Both community MQTT logins are intentionally public. This page does not provide live uptime monitoring or guarantee that credentials remain unchanged; broker-side permissions determine which topics each account may publish or subscribe to. Administrator credentials are private.

Public community MQTT accounts

These are the shared credentials provided for the Northern Michigan Mesh broker. Choose the account corresponding to your application.

ApplicationUsernamePassword
Meshtastic gatewaymeshpublicrogueregion
MeshCore observermeshobserverrogueregion

Both accounts are public by design; they are not server-administrator accounts. Broker topic permissions and rate limits are separate from knowing the password.

Other brokers use different credentials. The official Meshtastic public MQTT broker and MichMesh document meshdev / large4cats for their own servers. These credentials are not automatically valid for Northern Michigan Mesh. Use the Northern Michigan Mesh account associated with the service you are connecting.

Important — the two apps use different address formats: For the MeshCore MQTT Observer Server field, paste mqtts://mqtt.northernmichmesh.org:8883 in full. For the Meshtastic MQTT Server Address field, use mqtt.northernmichmesh.org and enable TLS separately (port 8883). Do not assume the same field format applies to both clients. Meshtastic settings reference.

What does the broker actually do?

MQTT is a publish/subscribe service running over an IP connection. A radio gateway or observer connects to it, publishes information to a named topic, and authorized subscribers can read that topic. The broker itself is not a radio repeater.

MESHTASTIC

Optional Internet bridging

Meshtastic gateways can uplink radio packets to MQTT and, if explicitly configured, downlink selected broker traffic into a local LoRa network. Online delivery between distant radio groups does not prove an RF path.

Learn how Meshtastic MQTT works →
MESHCORE

Observer and monitoring feeds

MQTT-capable MeshCore observers can publish packets heard at their location, station status and other supported observations for tools such as CoreScope. This does not automatically route messages between MeshCore radio networks.

Understanding MeshCore observers →
SETUP GUIDE 01

Meshtastic: connect a gateway

These are the settings for this broker. You need a Meshtastic device with supported Internet access (Wi-Fi, Ethernet or a compatible phone-client proxy), the community-shared meshpublic / rogueregion login, and at least one channel you control. These credentials belong to Northern Michigan Mesh, not another project's MQTT server.

SettingValueWhat it means
Server address (Meshtastic app)mqtt.northernmichmesh.orgMeshtastic config generally uses the hostname; enable TLS separately. The full mqtts:// URL is for observer-style Server URL fields.
Port and security8883 · TLS enabledMQTT over TCP/TLS. Verify the server certificate.
Public Meshtastic usernamemeshpublicCommunity-shared Meshtastic MQTT login, separate from the observer publishing account.
Public Meshtastic passwordrogueregionShared community password supplied by the broker operator; permissions depend on broker access controls.
Root topicmsh/US/MI/NMIPreviously verified namespace on this broker; not an RF region or radio channel.
MQTT moduleEnabledOnly on the gateway node you want to connect.
Channel uplinkOn for chosen private channelSends selected RF packets to MQTT. Start with uplink only.
Channel downlinkOff initiallyAvoid flooding shared RF airtime with Internet-origin packets.
MQTT encryptionEnabled for private-channel packetsDo not send unencrypted channel data without a clear reason and consent.
MQTT JSON / Map ReportingOff initiallyCan reveal message data, node identities and location; enable only deliberately.

Setup steps

  1. First verify local RF messaging with MQTT disabled. Your radio region, frequency slot, LoRa preset and chosen channel must already work.
  2. In the Meshtastic app, open Settings → MQTT on Android, Settings → Module Configuration → MQTT on Apple, or Config → Module Config → MQTT in the Web client.
  3. Enable MQTT and set the hostname mqtt.northernmichmesh.org. Turn TLS on (the service uses port 8883) and enter username meshpublic and password rogueregion. If your client exposes a port field, set it to 8883.
  4. Set the root topic to msh/US/MI/NMI. This is an MQTT namespace—not a LoRa modem preset, not a radio frequency, and not a guarantee of Michigan-only reception.
  5. Prefer MQTT encryption on and leave optional JSON and public map reporting off until you understand the exposure. On supported ESP32 hardware, JSON can be enabled for specific integrations, but it is not encrypted.
  6. Open Settings → Channels (or the corresponding channel editor). On a private channel with an intentionally configured key, enable Uplink but keep Downlink disabled initially. Merely enabling the MQTT module does not turn on a channel's uplink.
  7. Give the gateway an IP connection through supported Wi-Fi/Ethernet or phone proxy. Check broker connection and publish a permitted test packet.
  8. Only consider downlink later if a controlled Internet-to-radio path is desired and permitted. It can add traffic to a shared RF channel. Do not blindly inject public-broker traffic.

Phone proxy: on supported mobile apps, MQTT Client Proxy can use the phone's Internet connection. It must remain connected and online; the Meshtastic Web client's proxy option may be visible but not functional. Don't confuse a Bluetooth-connected radio with a broker-connected gateway.

Meshtastic CLI example — private-channel uplink

# Example: Meshtastic Python CLI on an authorized gateway.
# Community-shared MQTT credentials for the Northern Michigan Mesh broker.
# Confirm which radio/channel is selected before applying.
meshtastic --set mqtt.address mqtt.northernmichmesh.org \
  --set mqtt.username meshpublic \
  --set mqtt.password rogueregion \
  --set mqtt.tls_enabled true \
  --set mqtt.root msh/US/MI/NMI \
  --set mqtt.encryption_enabled true \
  --set mqtt.json_enabled false \
  --set mqtt.map_reporting_enabled false \
  --set mqtt.enabled true

# On your intended PRIVATE channel (index 0 is only an example):
meshtastic --ch-index 0 --ch-set uplink_enabled true
meshtastic --ch-index 0 --ch-set downlink_enabled false

Commands are examples for supported firmware versions. Both MQTT logins shown here are public community credentials, but never expose private, personal, Wi-Fi or administrator passwords. Terminals can retain commands you type.

Important: A private broker should not be used to mirror the public default LongFast channel indiscriminately. The Meshtastic project's public service has controls that a custom broker may not have. Read the Meshtastic MQTT integration and private-broker guidance before allowing downlink.

More explanations: MQTT and off-grid limits, environmental telemetry, GPS/location privacy, and the official MQTT module guide.

SETUP GUIDE 02

MeshCore: connect an MQTT observer

Use supported MeshCore MQTT observer or another build with MQTT publication features. A normal companion or repeater does not necessarily contain the observer firmware. The radio must be tuned to the mesh it is intended to observe. The shared meshobserver account is intentionally published for observer contributions, unlike a private administrator login.

SettingValueWhat it means
Full Server URL — requiredmqtts://mqtt.northernmichmesh.org:8883Copy the ENTIRE value: mqtts:// scheme, hostname, and :8883. Do not use hostname alone.
TransportMQTT TCP + TLSNot a documented WebSocket endpoint. Verify server certificates.
Public observer usernamemeshobserverShared MQTT observer publishing account; not a server administrator account.
Public observer passwordrogueregionCommunity-shared observer password. Publishing permissions remain controlled by broker ACLs.
Observer reporting code (IATA field)Choose from county list belowSelect the three-letter region matching the county where your observer is installed.
MQTT topic patternmeshcore/<REGION>/<observer-id>/REGION is your selected county-based reporting code; this is not a MeshCore RF scope.
Packet / status reportingEnable on supported firmwareRequires actual LoRa reception, compatible radio parameters and publish access.
FirmwareMeshCore MQTT Observer or compatible MQTT-enabled buildA standard companion or repeater does not necessarily have this functionality.

Which region code should I enter?

Choose the county where your observer is physically installed. The three-letter code is for observer MQTT reporting, not a MeshCore radio region scope. HTL is retired; do not use it for Northern Michigan Mesh observer reporting. Choose from the list or view our regional map.

Select a county above to see the exact code and generate the CLI command below. If your county is not listed, check the region map or ask us before choosing a code.

Region codeIncluded counties
GDWIsabella, Clare, Gladwin, Arenac, Ogemaw, Roscommon
CADOceana, Newaygo, Mecosta, Osceola, Lake, Mason, Manistee, Wexford, Missaukee
TVCBenzie, Grand Traverse, Kalkaska, Crawford, Otsego, Antrim, Leelanau, Charlevoix, Emmet, Cheboygan
APNIosco, Alcona, Oscoda, Montmorency, Alpena, Presque Isle
CIUMackinac, Chippewa, Luce
MQTSchoolcraft, Alger, Delta, Menominee, Dickinson, Marquette
CMXIron, Baraga, Gogebic, Ontonagon, Houghton, Keweenaw

Open the color-coded county map and GeoJSON downloads → · Why observer regions are different from RF forwarding scopes →

Setup steps

  1. Flash supported MeshCore MQTT Observer firmware for your exact device if you don't already have an MQTT-capable build. Know whether the device is intended to listen only or also operate as a radio repeater.
  2. Configure the local LoRa parameters (frequency, bandwidth, spreading factor and coding rate) to match the actual RF traffic in your area. MQTT does not repair a radio mismatch.
  3. Connect the observer to Wi-Fi/IP. The Gessaman observer firmware offers a first-boot setup hotspot and a web configuration panel.
  4. Choose an unused custom MQTT slot. Paste the entire mqtts://mqtt.northernmichmesh.org:8883 string into its Server URL field, including the mqtts:// prefix and :8883 port. Enter the published meshobserver / rogueregion credentials in their respective fields. This is raw MQTT/TLS, not a WebSocket URL. Hostname-only is not the working observer configuration.
  5. Set Observer location / IATA to the three-letter code shown by the county selector above. For example, an observer in Clare County uses GDW. It controls MQTT reporting organization, not radio forwarding scopes.
  6. Enable supported received-packet and status publication, then verify the broker connection and the appearance of new observations.

Choose your observer's county above to display a CLI example with the correct region code. We don't supply a default because the wrong code would mislabel observations.

Choose an unused broker slot rather than overwriting an existing destination. The working observer's Server field needs the whole mqtts://mqtt.northernmichmesh.org:8883 value. This example does not set a separate port override. If your particular firmware offers different fields, consult its version-specific help rather than entering a hostname-only value.

After setting up a reporting observer, you can explore our CoreScope observations dashboard ↗ or visit the Network Maps directory →. Dashboard reports reflect the data received by contributing observers, not guaranteed end-to-end RF coverage.

For a detailed version of this walkthrough, topic examples, and troubleshooting see MeshCore MQTT observer setup →. The location codes and scoping guide explains why observer labels and RF region scopes are different.

MQTT topic namespaces and payloads

Both systems can publish through the same broker, but they do not understand one another's radio packets simply because they share an MQTT server. Each ecosystem has its own message structure and consumers.

NetworkTopic exampleWhat it carries
Meshtasticmsh/US/MI/NMI/2/e/CHANNEL/!nodeidProtobuf/ServiceEnvelope-style mesh packet (depending on channel and encryption settings)
Meshtastic optional JSONmsh/US/MI/NMI/2/json/CHANNEL/!nodeidStructured, unencrypted JSON for supported packet types; don't turn it on casually
MeshCore observer statusmeshcore/REGION/<observer-id>/statusObserver availability/health/status information
MeshCore observed packetsmeshcore/REGION/<observer-id>/packetsRF packet observations received by that observer, for tools such as CoreScope

Subscribers with the appropriate permissions may use topic filters such as msh/US/MI/NMI/# or meshcore/REGION/# (replace REGION with the actual county-based reporting code). These are MQTT subscription filters, not radio frequencies or region-scope settings. Select a county in the region lookup to see examples update.

Verify your connection

There are three distinct things to test: reachability (the network and TLS endpoint respond), authentication (your account is accepted), and data flow (authorized messages are published to and received from expected topics).

  1. Check DNS/TLS: from a Linux system, run the command below. This tests the TLS handshake, not MQTT login or topic permissions.
  2. Connect an MQTT client: an application such as MQTTX or an authorized diagnostic client can use hostname mqtt.northernmichmesh.org, port 8883, TLS on, certificate verification on, and your own credentials.
  3. Subscribe only where permitted: for Meshtastic try the namespace you're authorized to view; for MeshCore use the observer's actual IATA/topic prefix. A successful connect without fresh packets does not prove an RF node is receiving anything.
  4. Compare to local RF: make a controlled radio-only test, then enable MQTT uplink and compare. Remote Internet delivery isn't a substitute for antenna or repeater coverage.

TLS reachability test (does not authenticate to MQTT)

openssl s_client -connect mqtt.northernmichmesh.org:8883 -servername mqtt.northernmichmesh.org -brief

Public broker status: this page isn't a live monitoring dashboard. A past successful connection doesn't guarantee the broker, a particular account, or every topic permission is available right now. The broker and its surrounding Internet/VPS/transport may also be down even while the local radio mesh still works.

Security, privacy and off-grid expectations

Public logins versus private admin credentials

Both meshobserver and meshpublic credentials are intentionally public community logins. TLS still protects the connection in transit; the broker's topic permissions determine what clients can do. Never disclose administrator or personal passwords, private keys or exact home coordinates. Use the account intended for your client's function.

Know what MQTT does not replace

Meshtastic can operate locally over LoRa with MQTT disabled. MeshCore observers can stop publishing without stopping all independent MeshCore radio traffic. Any route relying on an Internet broker will fail when that IP path fails unless another route exists.

The meshobserver / rogueregion and meshpublic / rogueregion pairs above are intentionally community-shared. For access questions, account rotation and topic permissions, ask in the Northern Michigan Mesh forum. The site does not publish private administrator credentials or claim anonymous publishing is permitted.

More about Meshtastic Internet dependency → · More about MeshCore reporting →