HCM Network Tools

See what the local mesh is hearing.

Start with the live map. Use Health Check when you want to know whether participating observers heard a test message. Open the Analyzer only when you want packet-level detail.

Best place to start

Live Map

Explore recently observed nodes, paths, and regional MeshCore activity. Pan and zoom around the map, then select a node or path for the details available about it.

The map shows activity heard through participating systems. It is not a complete inventory of every node or a promise that your radio can reach each marker.

Open Live Map

Troubleshooting

Health Check

Health Check gives you a one-message test of whether participating observers can hear your node.

Open Health Check and generate a test code.
Send that exact code on the MeshCore #health-check channel.
Leave the page open while it reports which observers received it.

A result confirms that an observer heard that message. It does not by itself prove a reliable two-way path to every node on the mesh.

Open Health Check

Advanced and optional

Activity Analyzer

Use the Analyzer when the map does not provide enough detail. Search for a node by name or public key, then narrow the view according to what you are investigating.

Live: Watch current activity received by the service.
Packets: Inspect individual packets and available route details.
Nodes: Review known node information gathered from observed traffic.
Observers: See which participating receiving systems reported activity.

The Analyzer is useful for troubleshooting and network study, but it is not required for ordinary MeshCore messaging.

Open Activity Analyzer

For observer operators

Contribute Observer Data

MeshCore MQTT uplink uses meshcoretomqtt on a Raspberry Pi or similar Linux computer connected to a MeshCore observer. Add Hampden County Mesh as another broker to contribute the packet and status data your observer hears. No account is required.

Server: mqtt.hampdencountymesh.org
Port: 41313

Add this block to /etc/mctomqtt/config.d/99-user.toml:

[[broker]]
name = "hampden-county-mesh"
enabled = true
server = "mqtt.hampdencountymesh.org"
port = 41313
transport = "tcp"

[broker.tls]
enabled = false

[broker.auth]
method = "none"

Then restart the service:

sudo systemctl restart mctomqtt

This endpoint is upload-only. Anonymous connections cannot read broker traffic, and contributed data is not automatically forwarded to other regional brokers or mapping services.

Learn Before You Diagnose

Want to see why the tools report different things?

The simulator shows the difference between a flood and a learned direct path. MeshCore Basics explains node roles, adverts, channels, maps, and observed activity in plain language.