(feature) Filter to show only reachable nodes #76

Closed
opened 2026-10-05 03:19:40 +02:00 by adam · 6 comments
Owner

I have many many nodes in my list as I have been traveling with my device for a long time. This means that the list of nodes is long.
It would be great if the app could toggle a filter to only show nodes that a within reach (via the current mesh).

I have many many nodes in my list as I have been traveling with my device for a long time. This means that the list of nodes is long. It would be great if the app could toggle a filter to only show nodes that a within reach (via the current mesh). <!-- github-sync-id:3833355970 -->
adam closed this issue 2026-10-05 03:19:40 +02:00
Author
Owner

We can't be sure nodes are within reach but we can tell if we've heard a packet from them recently

We can't be sure nodes are within reach but we can tell if we've heard a packet from them recently <!-- github-comment-id:3775190042 -->
Author
Owner

We can't be sure nodes are within reach but we can tell if we've heard a packet from them recently

I guess that is enough. It is possible for the official android app so I would expect it to be possible here as well.

> We can't be sure nodes are within reach but we can tell if we've heard a packet from them recently I guess that is enough. It is possible for the official android app so I would expect it to be possible here as well. <!-- github-comment-id:3775226604 -->
Author
Owner

It is possible for the official android app

I don't see how, could you send a screenshot?

> It is possible for the official android app I don't see how, could you send a screenshot? <!-- github-comment-id:3775356964 -->
Author
Owner
Image
<img width="1080" height="2410" alt="Image" src="https://github.com/user-attachments/assets/362df15b-d47e-421a-9c1e-cda5676b05ec" /> <!-- github-comment-id:3776175767 -->
Author
Owner

I checked the Android code to be sure and: "offline nodes" is determined by the time we last heard from those nodes. If it's been over two hours, they are considered "offline".

https://github.com/meshtastic/Meshtastic-Android/blob/cf59033c49177eeb27d48b68b674756065223dc8/core/model/src/main/kotlin/org/meshtastic/core/model/util/DateTimeUtils.kt#L66

https://github.com/meshtastic/Meshtastic-Android/blob/cf59033c49177eeb27d48b68b674756065223dc8/core/database/src/androidTest/kotlin/org/meshtastic/core/database/dao/NodeInfoDaoTest.kt#L309

I will eventually attempt to implement a "hide offline nodes" feature which hides nodes we haven't heard from in two hours.

I checked the Android code to be sure and: "offline nodes" is determined by the time we last heard from those nodes. If it's been over two hours, they are considered "offline". https://github.com/meshtastic/Meshtastic-Android/blob/cf59033c49177eeb27d48b68b674756065223dc8/core/model/src/main/kotlin/org/meshtastic/core/model/util/DateTimeUtils.kt#L66 https://github.com/meshtastic/Meshtastic-Android/blob/cf59033c49177eeb27d48b68b674756065223dc8/core/database/src/androidTest/kotlin/org/meshtastic/core/database/dao/NodeInfoDaoTest.kt#L309 I will eventually attempt to implement a "hide offline nodes" feature which hides nodes we haven't heard from in two hours. <!-- github-comment-id:3781615270 -->
Author
Owner

Thank you.

Thank you. <!-- github-comment-id:3782689032 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/contact#76