[Feature Request] Show packet timestamp for direct messages in Packet Analyzer #173

New Issue

2026-10-05T02:01:49+02:00

adam commented

2026-10-05 02:01:49 +02:00

Currently, in Packet Analyzer for a given message the timestamp embedded in the packet can only be seen in decoded form for group messages, but not direct messages.

=> would be great so see both timestamps - packet-embedded aka "sent timestamp" and received timestamp - for all received and decoded messages.

Currently, in Packet Analyzer for a given message the timestamp embedded in the packet can only be seen in decoded form for group messages, but not direct messages. => would be great so see both timestamps - packet-embedded aka "sent timestamp" and received timestamp - for all received and decoded messages.

adam closed this issue

2026-10-05 02:01:50 +02:00

adam commented

2026-10-05 02:01:50 +02:00

Recieved timestamp in system time is the header 🙂

<img width="425" height="249" alt="Image" src="https://github.com/user-attachments/assets/c5bb94a8-a415-4e43-a184-ef23e1a4a7db" /> Recieved timestamp in system time is the header 🙂

adam commented

2026-10-05 02:01:51 +02:00

Not for me....

Only for group message:

But not for a direct message:

For some reason it doesn't decrypt the message, although I can read it in the chat window.

Not for me.... Only for group message: <img width="1621" height="741" alt="Image" src="https://github.com/user-attachments/assets/a3fac753-2420-4f5f-b856-b43670eb194d" /> But not for a direct message: <img width="1642" height="847" alt="Image" src="https://github.com/user-attachments/assets/9a7135cc-80bf-4f67-aba7-11b9be752337" /> For some reason it doesn't decrypt the message, although I can read it in the chat window.

adam commented

2026-10-05 02:01:52 +02:00

Hm, are you updated? The fact you're not seeing Sent (packet) seems like you're not on latest. If you run from python, you will need to rebuild your front end with npm run build.

Hm, are you updated? The fact you're not seeing `Sent (packet)` seems like you're not on latest. If you run from python, you will need to rebuild your front end with `npm run build`.

adam commented

2026-10-05 02:01:52 +02:00

I was on v3.12.2 and didn't see the need to update because nothing related was mentioned in the commit history.

Now I've updated to v3.13.0 and yes: sent timestamp + decrypted message is being displayed now for DMs too 👍

I was on v3.12.2 and didn't see the need to update because nothing related was mentioned in the commit history. Now I've updated to v3.13.0 and yes: sent timestamp + decrypted message is being displayed now for DMs too 👍

adam commented

2026-10-05 02:01:53 +02:00

But it's odd because you even mentioned related commit in this ticket but I can swear this wasnt shown in my Gitlab session. Either a glitch in Gitlab or a glitch in my brain getting old 🙈

But it's odd because you even mentioned related commit in this ticket but I can swear this wasnt shown in my Gitlab session. Either a glitch in Gitlab or a glitch in my brain getting old 🙈

adam commented

2026-10-05 02:01:54 +02:00

Yay glad it's working!

Yay glad it's working!

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#173