how it works
13 posts
-
How LoRa Mesh Routing Works
How LoRa mesh routing works in MeshCore: first contact floods through repeaters, recording each hop, then all later messages travel the cached direct path.
Read → -
v1.4.0: Walk the Path
Waev v1.4.0 ships path-walk for MeshCore paths, a packet archive explorer, a live packet globe, and a topology engine that proves what it draws.
Read → -
How Waev Names Meshes: The MeshBuilder Logic
Waev clusters nodes into meshes and names them using geographic boundaries, IATA codes, and reverse geocoding, backed by hysteresis to prevent naming churn.
Read → -
Can Waev Write to Your Broker?
Waev subscribes to your MQTT broker with read-only credentials. Writing to your broker is structurally impossible. Your ACL file enforces that limit.
Read → -
Dedicated MeshCore Gateway or Shared?
Should your MeshCore MQTT gateway be a dedicated node or shared with a repeater? The answer depends on where your gateway needs to be, not on how many devices you own.
Read → -
How MeshCore Packets Become a Live Map
How a raw MeshCore packet turns into a verified edge on Waev's Live Map: MQTT ingest, hop record parsing, and topology drawing explained.
Read → -
How MeshCore Repeaters Earn Their Place
How MeshCore uses public-key identity and access control to authenticate repeaters, and why Waev only draws topology edges from repeaters it can verify.
Read → -
Seeing Your First MeshCore Packet
See your first MeshCore packet in Waev's Live Packets view: what each field means, why ADVERT packets usually arrive first, and what the numbers tell you.
Read → -
Setting Up Mosquitto for MeshCore
A practical guide to Mosquitto MQTT broker setup for MeshCore: TLS on port 8883, password authentication, and an ACL that limits Waev to read-only access.
Read → -
Spoofed Node Prefix on a Mesh Map
What happens when a spoofed node prefix appears on a MeshCore mesh map, and why Waev's evidence-based topology rejects inferred edges rather than drawing them.
Read → -
What Is a Mesh Network Observer?
A mesh network observer is an enrolled MeshCore node bridging the radio mesh to your MQTT broker. Waev's only verified window into your network's traffic.
Read → -
What Data a Mesh Analytics Tool Stores
What a mesh analytics tool stores from your MeshCore network: SNR, hop count, and timing metadata only. Identity and location never enter the database.
Read → -
From Radio to Map
The pipeline from a radio broadcast to a verified edge on Waev's Live Map: how enrolled observers, your MQTT broker, and the ingest edge work together.
Read →