Feature Request
On the MeshCore Nodes page, the Last Heard timestamp displayed under each node name currently always shows a time (e.g. 14:32). For nodes last heard on a previous day, this time is ambiguous — the user cannot tell which day it refers to.
Proposed Behavior
Apply a date/time cutoff based on the MeshMonitor instance's configured timezone:
- If the node was last heard today: display the time as-is (current behavior)
- If the node was last heard before today: display the date instead of the time, formatted according to the user's Date Format setting (under Units & Formats)
Current Behavior
Always shows the time regardless of how long ago the node was last heard.
Benefit
Eliminates ambiguity for nodes that haven't been heard recently, while keeping the time display for fresh nodes where it's most relevant.
Authored by NodeZero 0️⃣
Feature Request
On the MeshCore Nodes page, the Last Heard timestamp displayed under each node name currently always shows a time (e.g.
14:32). For nodes last heard on a previous day, this time is ambiguous — the user cannot tell which day it refers to.Proposed Behavior
Apply a date/time cutoff based on the MeshMonitor instance's configured timezone:
Current Behavior
Always shows the time regardless of how long ago the node was last heard.
Benefit
Eliminates ambiguity for nodes that haven't been heard recently, while keeping the time display for fresh nodes where it's most relevant.
Authored by NodeZero 0️⃣