No. MeshRank does not forward, relay, or complete mesh messages using the internet. All mesh communication still happens entirely over RF. MeshRank only observes what has already occurred and reports that information back to users.

No. The mesh remains fully autonomous and functional without MeshRank. If MeshRank disappeared tomorrow, the mesh would continue to operate exactly as it does today. MeshRank does not participate in routing decisions, message delivery, or network control - it provides visibility, not dependency.

Because feedback matters. In early and sparse networks, lack of feedback causes repeaters to be switched off, not improved. MeshRank uses off-mesh observation to help operators understand what’s happening without increasing RF traffic or adding test spam to the network. This strengthens the mesh - it doesn’t weaken it.

No. MeshRank is not in the message path. It cannot block, delay, or interfere with mesh traffic. If MeshRank goes offline, the mesh continues to operate unchanged. There is no reliance on MeshRank for delivery, routing, or authentication.

Quite the opposite. MeshRank encourages: better repeater placement, higher uptime, reduced test traffic, and faster identification of coverage gaps. All of these increase RF-only resilience, even when the internet is unavailable.

No. Observers do not inject traffic or control the network. They report limited metadata needed to understand propagation - not to monitor users. The goal is network health, not message content analysis.

Yes - intentionally. Visibility and motivation matter. Ranking makes contribution measurable, encourages operators to keep repeaters online, and helps the network grow during its most fragile phase. Strong networks are built by engaged operators.

MeshRank becomes less critical - and that’s a success. As density increases, confidence becomes self-sustaining. MeshRank’s role naturally shifts toward diagnostics, optimisation, and historical insight rather than reassurance.

MeshRank exists to answer one question early mesh networks struggle with: “Is this helping?” By giving honest, low-impact feedback, MeshRank helps good repeaters stay online long enough for the mesh to become truly resilient.

Two things have to be true: (1) your repeater must be advertising its GPS location in its self-adverts, and (2) at least one MeshRank observer must be in RF earshot to hear the advert. Quick checks:

• On the repeater, set name, lat, lon and enable the flooded advert (most builds expose advert send + advert flood). Confirm coordinates are non-zero.
• Send a flooded self-advert from the repeater (CLI: advert send 1) and wait 2–3 minutes for an observer to relay it.
• Open MeshMap with the right region selected. If still missing, check whether any observer near you reported any packets in the last 24 h on Static Observers.
• If there is no observer nearby, consider setting one up on the Become an Observer page — without an observer in earshot of your repeater, MeshRank can’t see it.

You can’t — by design. The Heltec V3 “Observer node” firmware is single-purpose: it boots, joins Wi-Fi, listens, and uploads. There’s no companion screen, no admin password, and no Bluetooth admin shell. All configuration (Wi-Fi, location, name) happens through the web flasher during step 3 of Become an Observer.

If you want a node you can also log into and manage, switch to the Repeater Observer or Direct MQTT options instead — those use the full MeshCore firmware with the MeshRank uplink on top.