fix: use server timestamp for channel lastActivity, not device clock

WS messages from lincomatic bridge lack packet.timestamp, so the
code fell through to payload.sender_timestamp which reflects the
MeshCore device's clock (often wrong). Use current time as fallback.
This commit is contained in:
you
2026-03-21 21:50:18 +00:00
parent ddb6dcb113
commit 3c12690ccb
2 changed files with 2 additions and 2 deletions
+1 -1
View File
@@ -407,7 +407,7 @@
}
if (!sender) sender = 'Unknown';
var ts = m.data?.packet?.timestamp || payload.sender_timestamp || new Date().toISOString();
var ts = m.data?.packet?.timestamp || m.data?.timestamp || new Date().toISOString();
var pktHash = m.data?.hash || m.data?.packet?.hash || null;
var pktId = m.data?.id || null;
var snr = m.data?.snr ?? m.data?.packet?.snr ?? payload.SNR ?? null;
+1 -1
View File
@@ -86,7 +86,7 @@
<script src="home.js?v=1774042199"></script>
<script src="packets.js?v=1774127844"></script>
<script src="map.js?v=1774126708" onerror="console.error('Failed to load:', this.src)"></script>
<script src="channels.js?v=1774129290" onerror="console.error('Failed to load:', this.src)"></script>
<script src="channels.js?v=1774129818" onerror="console.error('Failed to load:', this.src)"></script>
<script src="nodes.js?v=1774126708" onerror="console.error('Failed to load:', this.src)"></script>
<script src="traces.js?v=1774350000" onerror="console.error('Failed to load:', this.src)"></script>
<script src="analytics.js?v=1774126708" onerror="console.error('Failed to load:', this.src)"></script>