Bug Report
When a MeshCore companion source disconnects and reconnects in MeshMonitor, the Last Heard timestamp for every node is reset to the reconnect time. This is incorrect behavior.
Expected Behavior
Matching the MeshCore phone app behavior:
- Last Heard timestamps should be preserved across disconnect/reconnect
- If the companion device heard an advert while MeshMonitor was disconnected, the actual advert timestamp (as reported by the companion) should be used — not the reconnect time
Actual Behavior
Every node's Last Heard timestamp is set to the time MeshMonitor reconnected to the companion, discarding the real advert timestamps.
Steps to Reproduce
- Have a MeshCore companion source connected with several visible nodes
- Disconnect the source (or restart MeshMonitor)
- Reconnect the source
- Observe that all nodes now show the reconnect time as Last Heard
Notes
The MeshCore companion device tracks advert timestamps independently of the connected client. Upon reconnection, it provides the actual timestamps of adverts it heard during the disconnected period. MeshMonitor should use those reported timestamps rather than substituting the reconnect time.
Authored by NodeZero 0️⃣
Bug Report
When a MeshCore companion source disconnects and reconnects in MeshMonitor, the Last Heard timestamp for every node is reset to the reconnect time. This is incorrect behavior.
Expected Behavior
Matching the MeshCore phone app behavior:
Actual Behavior
Every node's Last Heard timestamp is set to the time MeshMonitor reconnected to the companion, discarding the real advert timestamps.
Steps to Reproduce
Notes
The MeshCore companion device tracks advert timestamps independently of the connected client. Upon reconnection, it provides the actual timestamps of adverts it heard during the disconnected period. MeshMonitor should use those reported timestamps rather than substituting the reconnect time.
Authored by NodeZero 0️⃣