/mesh) renders on the relay and receiver roles; Sources (/sources) renders on the receiver role only. On any other role the route shows Not available on this profile. Home shows the same panels for these roles.
Mesh (relay and receiver roles)
batman-adv role, gateway election, and partition state.
Below the fields, the neighbour list shows each neighbour’s MAC and link quality in percent (batman-adv TQ out of 255).
Mesh states
- “This node is not in a mesh.”: the agent answered 404 for the mesh state.
- “No current mesh snapshot. The mesh service is not reporting.”: the mesh service has published nothing.
- “No batman-adv neighbours discovered yet.”: the mesh is up but no neighbour is in range.
Mesh data source
GET /api/v1/ground-station/mesh, every 2 s. Also available, not used by this page: GET /api/v1/ground-station/mesh/neighbors, .../gateways and .../routes.
Sources (receiver role)
Per-relay aggregation and FEC dedup stats.
Below the fields, each contributing relay shows its MAC and fragment count. “No relay is contributing right now.” means the receiver hears no relay; “The receive loop is not reporting, so relay contributions are unknown.” means the receive loop published nothing.
Sources data source
GET /api/v1/ground-station/wfb/receiver/combined and GET /api/v1/ground-station/wfb/receiver/relays, every 2 s.
Troubleshooting
No neighbours or partition reads partitioned
No neighbours or partition reads partitioned
Check that every node runs the same mesh id and that the mesh radios are in range. See Mesh troubleshooting.
One relay contributes far fewer fragments
One relay contributes far fewer fragments
Compare the per-relay fragment counts. A relay well below the others has a weaker drone link; move it or check its antennas. A rising FEC repaired count with steady fragments means the relays together still cover the loss.
Next steps
Display and joystick
Kiosk display, gamepads and Bluetooth.
Mesh overview
How the relay and receiver roles fit together.