Feature Request: Implement a text search filter feature for the "Raw Packed Feed" window #233

Closed
opened 2026-10-05 02:05:08 +02:00 by adam · 3 comments
Owner

📝 Description

In the "Raw Packet Feed" area implementing a search input box so the user can search for strings inside the packet and filter them for view, like contact identities, RPT, etc...

🚦 Current Behavior

There is no search capability

🎯 Expected Behavior

The "Raw Packet Feed" should have a search input box so we can search for strings inside the packets and filter them in based on that text string filter.

📋 Steps to Reproduce

NA

📸 Screenshots / Logs

NA

💻 Environment Information

  • OS: Windows 11
  • Browser/Version: Edge 150.0.4078.48 (Official build) (64-bit)
  • Project Version: v3.15.2 wrapped has an app in HomeAssistant OS

💡 Possible Solution


Additional context
Add any other context about the problem here.

## 📝 Description In the "Raw Packet Feed" area implementing a search input box so the user can search for strings inside the packet and filter them for view, like contact identities, RPT, etc... ## 🚦 Current Behavior There is no search capability ## 🎯 Expected Behavior The "Raw Packet Feed" should have a search input box so we can search for strings inside the packets and filter them in based on that text string filter. ## 📋 Steps to Reproduce NA ## 📸 Screenshots / Logs NA ## 💻 Environment Information - **OS:** Windows 11 - **Browser/Version:** Edge 150.0.4078.48 (Official build) (64-bit) - **Project Version:** v3.15.2 wrapped has an app in HomeAssistant OS ## 💡 Possible Solution --- **Additional context** Add any other context about the problem here. <!-- github-sync-id:4828264516 -->
adam closed this issue 2026-10-05 02:05:08 +02:00
Author
Owner

so you're meaning raw hex search? or in the whole decoded packet payload if we can (regions, etc.) -- the latter may be more of pain, so I hope it's the first one haha

so you're meaning raw hex search? or in the whole decoded packet payload if we can (regions, etc.) -- the latter may be more of pain, so I hope it's the first one haha <!-- github-comment-id:4920031010 -->
Author
Owner

Just raw hex search,:

  1. because its simpler and gives the possibility to search hex identifiers
  2. decoded packet search yes is more tricky, and only works if the we have the secret in the DB. Its a nice to have but not for this fase
Just raw hex search,: 1. because its simpler and gives the possibility to search hex identifiers 2. decoded packet search yes is more tricky, and only works if the we have the secret in the DB. Its a nice to have but not for this fase <!-- github-comment-id:4922844440 -->
Author
Owner
Image
<img width="835" height="425" alt="Image" src="https://github.com/user-attachments/assets/58b6519e-14c3-41eb-b353-8bf4fb2e2e2a" /> <!-- github-comment-id:4929915722 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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