From 3c12690ccb41e7ecd7fa43dedf78283e7154583f Mon Sep 17 00:00:00 2001 From: you Date: Sat, 21 Mar 2026 21:50:18 +0000 Subject: [PATCH] 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. --- public/channels.js | 2 +- public/index.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/public/channels.js b/public/channels.js index 2dfe36a5..7b58cdea 100644 --- a/public/channels.js +++ b/public/channels.js @@ -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; diff --git a/public/index.html b/public/index.html index 9317455a..160c17c3 100644 --- a/public/index.html +++ b/public/index.html @@ -86,7 +86,7 @@ - +