Skip to main content

MeshCore MQTT observer: set up Northern Michigan Mesh reporting

Start here: copy the entire server URL, including mqtts:// and :8883.

mqtts://mqtt.northernmichmesh.org:8883

This is the complete value for the MQTT observer's Server field when using the custom-broker URL configuration. Do not enter only mqtt.northernmichmesh.org: that omits the TLS scheme and port required by the working observer configuration.

This applies to supported MeshCore MQTT Observer firmware. It does not mean that every MeshCore companion or standard repeater has this MQTT functionality. For a quick comparison with Meshtastic's different server-address fields, see the main MQTT setup page.

What does an observer do?​

An observer listens for MeshCore LoRa transmissions at its location and, when configured, publishes heard packets and status to an MQTT broker. Mapping/monitoring systems may subscribe to those reports.

Where to explore reported data: Northern Michigan Mesh CoreScope is the project's public-facing MeshCore observation link. The dashboard's availability and what it displays may change independently of the broker. A successful MQTT login or packet publication is not a guarantee that the dashboard will immediately show a node.

An observer does not become a radio repeater by publishing to MQTT, nor does MQTT create an over-the-air connection between separate MeshCore RF networks. It still needs a suitable antenna, radio settings, power and an Internet/IP connection.

Connection settings​

SettingValue or action
Server URL (copy exactly)mqtts://mqtt.northernmichmesh.org:8883
Connection typeMQTT over TCP with TLS, not http://, https://, or WebSockets
Broker slotSelect an available custom MQTT slot; avoid overwriting a working destination
Public observer usernamemeshobserver
Public observer passwordrogueregion
Account permissionsCommunity-shared observer publishing login; broker ACLs still determine topic permissions
Observer location / IATA fieldSelect GDW, CAD, TVC, APN, CIU, MQT or CMX using the county lookup below
ReportingEnable received-packet and status messages as supported by your firmware
TLS certificatesVerify the broker certificate when your client provides that control

HTL is retired and is not a current Northern Michigan Mesh observer reporting region. Do not copy it from older examples.

The meshobserver / rogueregion pair is intentionally community-shared for supported observer reporting. It is not a server administrator account. The broker's topic ACLs still determine permitted actions, and public credentials can be rotated if abused. Don't publish private administrator, Wi-Fi or personal credentials.

Choose the reporting region for your county​

Use the code covering the county where the observer is installed, not necessarily the nearest airport. Our regional codes group reports geographically; they are not MeshCore RF forwarding scopes and do not change which radio messages a repeater forwards.

CodeCounties
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

Visual option: View the Northern Michigan Mesh regional map. The main MQTT page also provides a county selector that generates the region code and CLI command. If your county isn't in this list, don't choose a random code; ask for guidance.

Option A: setup in the observer's web configuration interface​

  1. Flash the compatible MeshCore MQTT Observer image for the exact supported board if necessary.

  2. For first setup, connect to the MeshCore-Setup Wi-Fi network and open http://192.168.4.1 if the setup page does not appear. The board needs your local Wi-Fi/IP connection to publish MQTT reports.

  3. Configure the observer's radio frequency, bandwidth, spreading factor and coding rate to match the MeshCore network you intend to hear. These are radio settings, not MQTT settings.

  4. Open MQTT, choose an unused Custom broker destination, and paste the entire address below into the Server field:

    mqtts://mqtt.northernmichmesh.org:8883
  5. Enter the shared username meshobserver and password rogueregion in their respective MQTT fields. Enable TLS certificate verification when available.

  6. Set the observer's IATA / reporting location to the correct three-letter code from the county table. For example, an observer physically in Clare County uses GDW.

  7. Enable supported received-packet and status publishing, save and reboot. Check both Wi-Fi and the per-broker MQTT connection state.

See the firmware maintainer's configuration panel instructions. Depending on firmware version, the settings may be in an initial setup wizard or a separate web configuration panel.

Option B: observer CLI setup​

Commands below follow a Gessaman-style MQTT-capable observer build. Check your actual firmware's supported get and set commands and unused broker slot first. The observer credentials in this example are intentionally shared for public use; they are not administrator credentials.

get mqtt.presets
get mqtt.enabled
get mqtt.status

# Example assumes unused broker slot 1.
set mqtt1.preset custom
set mqtt1.server mqtts://mqtt.northernmichmesh.org:8883
set mqtt1.username meshobserver
set mqtt1.password rogueregion

# EXAMPLE ONLY for an observer in a GDW county such as Clare:
# Choose the real code for your own county from the table above.
set mqtt.iata GDW

set mqtt.enabled on
set mqtt.rx on
set mqtt.packets on
set mqtt.status on
reboot

The entire mqtts://... URL belongs in mqtt1.server. Don't strip the scheme or port. This example does not set a separate port override. If your firmware exposes distinct host/TLS/port controls instead of a URL field, follow its version-specific help; don't guess or mix conflicting settings.

The shared MeshCore observer account is public, and the separate Meshtastic community MQTT account is public as well. Use meshobserver for supported MeshCore observers and meshpublic for Meshtastic; both currently use the shared password rogueregion. Administrator accounts, private channel keys and Wi-Fi passwords must remain private. CLI commands can be recorded in terminal history or device logs, so prefer the observer's web form where available.

Check that the observer is actually reporting​

After reboot, inspect the commands supported by your firmware:

get wifi.status
get mqtt.enabled
get mqtt.running
get mqtt.status
get mqtt1.diag

A firmware version may have different diagnostic commands. Confirm Wi-Fi connected, MQTT connected, and new reports published as separate checks. Broker login alone does not prove that the LoRa receiver has heard any packets.

With the correct region chosen, observer topics follow patterns like:

meshcore/<REGION>/<observer-id>/status
meshcore/<REGION>/<observer-id>/packets

For an observer in Clare County, for example, those use meshcore/GDW/. Topic prefixes depend on your actual configured code and firmware format. Authorized MQTT subscribers may use a filter like meshcore/GDW/#. That filter is not a MeshCore radio region scope.

Troubleshooting​

SymptomFirst thing to verify
MQTT won't connectEntire Server URL, TLS certificate verification, Wi-Fi/DNS, outbound 8883, username/password
Connected but no new packet reportsRF tuning, antenna, actual traffic, packet publishing settings, topic ACL permissions
Reports appear in unexpected regionCheck mqtt.iata against your observer's actual county
CoreScope shows nothingIts own subscribed topics, filters and ingestion settings; broker delivery and application ingestion are separate
Public map shows traffic you can't hearThe observation may have reached the map through MQTT/IP, not a direct radio link

Learn more​

Ask for observer help on our forum. The shared observer account above is public; don't post administrator credentials, private keys or exact private station coordinates.