Node List App: the Nodes heard, and where they are #27

New Issue

2026-10-05T20:07:17Z

twisla commented

2026-10-05 20:07:17 +00:00

What

An App listing every Node the Mesh Service has heard (#25): names, when it was last heard, signal, hops away. With a GNSS Fix and a Node that shares its position: distance and bearing, the "radar" parked in M2 (Q60).

What's known

The data comes from the node database (#25); positions arrive in position packets, at whatever precision the sender chose.
Our own position comes from the GNSS Service; lib/gnss already has the formatting and the Maidenhead locator. Distance and bearing between two positions are pure maths, host-testable.
The Sky view's projection (direction and distance on a circle) could draw Nodes instead of satellites.
The Compass (#16) wants the same bearing-to-a-target arrow.

Questions

Sort by last heard, by signal, by distance, by name?
The radar: a view in this App, in the GNSS App, or in the Compass?
What's shown for a Node with no position, or an old one?
Details on Enter: hardware model, role, battery and other telemetry, if decoded?
Favourites, or hiding a Node?

## What An App listing every Node the Mesh Service has heard (#25): names, when it was last heard, signal, hops away. With a GNSS Fix and a Node that shares its position: distance and bearing, the "radar" parked in M2 (Q60). ## What's known - The data comes from the node database (#25); positions arrive in position packets, at whatever precision the sender chose. - Our own position comes from the GNSS Service; `lib/gnss` already has the formatting and the Maidenhead locator. Distance and bearing between two positions are pure maths, host-testable. - The Sky view's projection (direction and distance on a circle) could draw Nodes instead of satellites. - The Compass (#16) wants the same bearing-to-a-target arrow. ## Questions 1. Sort by last heard, by signal, by distance, by name? 2. The radar: a view in this App, in the GNSS App, or in the Compass? 3. What's shown for a Node with no position, or an old one? 4. Details on Enter: hardware model, role, battery and other telemetry, if decoded? 5. Favourites, or hiding a Node? ## Related `docs/milestones/M2.md` (Q60), `src/apps/gnss_app.cpp` (Sky view), #23, #25, #16.

twisla added this to the M4 Mesh receive milestone 2026-10-05 20:07:17 +00:00

twisla added the

kind

feature

area/apps area/gnss area/lora

labels 2026-10-05 20:07:17 +00:00

twisla added a new dependency 2026-10-05 20:07:17 +00:00

#25 Mesh Service: take part in the mesh, receive only