From 5e3dc897ba61940e90cdede209356f51f12bab97 Mon Sep 17 00:00:00 2001 From: zjs81 Date: Sun, 25 Oct 2026 11:26:15 -0700 Subject: [PATCH] Document map location requests, telemetry positions and the contact row Explain Update location, which nodes include a position and why, when a newer advert replaces a telemetry position, and the new contact row. --- documentation/contacts.md | 17 ++++++++++------- documentation/map-and-location.md | 19 +++++++++++++++++-- 2 files changed, 27 insertions(+), 9 deletions(-) diff --git a/documentation/contacts.md b/documentation/contacts.md index 00fc01e5..69559665 100644 --- a/documentation/contacts.md +++ b/documentation/contacts.md @@ -23,15 +23,18 @@ The Contacts screen is the primary hub for managing mesh nodes your radio has a Each contact is displayed as a list tile showing: - **Avatar**: Color-coded circle with type icon (or first emoji of the contact's name if it starts with one) -- **Name**: Contact name (single line) +- **Name**: Contact name on its own line, wrapping to a second line if it's long +- **Favorite star**: Amber star icon after the name if favorited +- **Location pin**: Grey pin icon after the name if the contact has GPS coordinates +- **Key prefix**: The contact's routing hash (public-key prefix) in a small badge, for matching against hops in paths - **Path label**: "Direct", "N hops", or "Flood" (with forced variants if a path override is active) -- **Public key**: Shortened hex format `` -- **Unread badge**: Red pill with count (if unread messages exist) -- **Last seen**: Relative timestamp ("Now", "5 mins ago", "2 hours ago", "3 days ago"). For chat contacts, this shows whichever is more recent: the last advertisement time or the last message time -- **Favorite star**: Amber star icon if favorited -- **Location pin**: Grey pin icon if the contact has GPS coordinates +- **Last seen**: Relative time at the end of the second line ("recently", "~ 5 min.", "~ 2 hours", "~ 3 days"). It shows whichever is most recent: the last advertisement or telemetry location update, or for chat contacts the last message +- **Unread badge**: Red pill with count at the right edge (if unread messages exist) +- **Manage button**: Shield icon at the right edge for repeaters and rooms -Pull-to-refresh re-fetches the full contact list from the device. +The **Discovered nearby** row at the top of the list opens the Discovery screen and scrolls with the list. + +Pull-to-refresh re-fetches the full contact list from the device. Telemetry locations survive the refresh until the node sends a newer advert. ## Search and Filter diff --git a/documentation/map-and-location.md b/documentation/map-and-location.md index 634235ef..ca3acfa4 100644 --- a/documentation/map-and-location.md +++ b/documentation/map-and-location.md @@ -79,10 +79,24 @@ In a mesh network, every message hops through one or more repeaters on its way t Standard pinch-to-zoom (range 2–18). Initial camera position is calculated from the statistical spread of all plotted points. ### Tap on a Node Marker -Opens a dialog showing: type, path (hop chain), coordinates, last-seen time, and public key. Action buttons vary by type: +Opens a card at the bottom of the map showing the node's status, type, last-seen time, path, node ID, and coordinates, with buttons to center on the node or close the card. Action buttons vary by type: - **Chat nodes**: "Open Chat" - **Repeaters**: "Manage Repeater" -- **Rooms**: "Join Room" +- **Rooms**: "Join Room" and "Manage Server" +- **Chat nodes and sensors in your contacts**: "Update location" (see below) +- **All nodes**: "Details" opens the full node info sheet + +### Update Location +**Update location** asks the node for its telemetry. If the reply includes a GPS position, the marker moves there right away and the last-seen time updates; a snackbar confirms it. You can also refresh a node's position from its Telemetry screen: any telemetry reply with a GPS position updates the map the same way. + +The node decides whether to include its position: +- **Companion radios** only include a position if they have a working GPS module and their owner allows location in telemetry, for everyone or only for favourites (**Settings → Privacy → Telemetry Location Mode**). A companion without GPS hardware never sends one, even if its adverts carry a manually set location. The app then says the node replied without a location. +- **Sensors** include their position (if they have GPS) for any client they accept, including guests. A sensor only answers clients it knows, so you may need to log in to it first. +- **Repeaters and rooms** only send their position to logged-in admins, so the button isn't shown for them. Their position normally comes from their adverts. + +If the node doesn't answer before the request times out, the app says there was no reply. The node has to be in your contacts (not only discovered) for the button to appear. + +A telemetry position stays on the map until the node sends a newer advert, which then replaces it. Refreshing or re-syncing the contact list from the radio keeps it. ### Long-Press on Empty Map Area Shows a bottom sheet with: @@ -201,6 +215,7 @@ The phone's own GPS is **never used**. All location data comes from the mesh: 1. **Device self-location**: Read from firmware device-info response. Set manually in Settings → Location, or updated automatically if the device has a GPS module. 2. **Remote node locations**: Extracted from advertisement packets received over the mesh. Encoded as integer lat/lon × 1,000,000. +3. **Telemetry replies**: A GPS position in a node's telemetry (from **Update location** or the Telemetry screen) replaces its advert position until the node adverts again. Telemetry positions have about 11 m precision (Cayenne LPP). ## Regions and offline use