adam/Remote-Terminal-for-MeshCore
1
0 Fork 0
mirror of https://github.com/jkingsman/Remote-Terminal-for-MeshCore.git synced 2026-11-03 08:02:19 +01:00
Code Issues 26 Packages Projects Releases Wiki Activity

Add per-packet parse breakdown in raw packet view. #43

New Issue
Closed
opened 2026-10-05 01:54:45 +02:00 by adam · 6 comments
adam commented 2026-10-05 01:54:45 +02:00
Owner
Copy link
Copy source
No description provided.
<!-- github-sync-id:4091345590 -->
adam closed this issue 2026-10-05 01:54:45 +02:00
adam commented 2026-10-05 01:54:46 +02:00
Author
Owner
Copy link
Copy source

This sounds nice. Maybe some other metrics as well (doesn't have to be graphs could be packets/hr, packets last 24h or something).

While on the topic of packet feed, eventually it would be nice to have some more info in addition to just the raw packet. I find myself doing most my troubleshooting in letsmesh due to the breakdown of the packet but all 2-byte/3-byte stuff is broken over there right now.

This sounds nice. Maybe some other metrics as well (doesn't have to be graphs could be packets/hr, packets last 24h or something). While on the topic of packet feed, eventually it would be nice to have some more info in addition to just the raw packet. I find myself doing most my troubleshooting in letsmesh due to the breakdown of the packet but all 2-byte/3-byte stuff is broken over there right now. <!-- github-comment-id:4087767873 -->
adam commented 2026-10-05 01:54:47 +02:00
Author
Owner
Copy link
Copy source

Oooh I was gonna close this due to my last commit but having frontend packet parsing could be cool. I'll think on that.

Oooh I was gonna close this due to my last commit but having frontend packet parsing could be cool. I'll think on that. <!-- github-comment-id:4087843739 -->
adam commented 2026-10-05 01:54:47 +02:00
Author
Owner
Copy link
Copy source

Probably gonna make this a click-to-modal so that we don't have to get funky with packet feed scroll. I think we can do it all pretty simply with our contact linkages + meshcore-decoder breakdown on our fork like letsmesh does.

Probably gonna make this a click-to-modal so that we don't have to get funky with packet feed scroll. I think we can do it all pretty simply with our contact linkages + meshcore-decoder breakdown on our fork like letsmesh does. <!-- github-comment-id:4087884136 -->
adam commented 2026-10-05 01:54:48 +02:00
Author
Owner
Copy link
Copy source

LOL, some funny wrapping going on
Image

LOL, some funny wrapping going on <img width="516" height="68" alt="Image" src="https://github.com/user-attachments/assets/8de2adee-a974-4ef5-a117-7fb35b3da2a3" /> <!-- github-comment-id:4093200755 -->
adam commented 2026-10-05 01:54:49 +02:00
Author
Owner
Copy link
Copy source

Haha yes this was a little half-baked. Will add some wrapping guards there.

Haha yes this was a little half-baked. Will add some wrapping guards there. <!-- github-comment-id:4093212866 -->
adam commented 2026-10-05 01:54:50 +02:00
Author
Owner
Copy link
Copy source

Created #93.

Created #93. <!-- github-comment-id:4093216395 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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