Feature Request: in the received message box show the Hash size mode it was sent in #235

New Issue

2026-10-05T02:05:18+02:00

adam commented

2026-10-05 02:05:18 +02:00

📝 Problem Description

Feature Request: in the message box where there is the sender name, date/time and paths (link) show also the hash mode the message was sent with (1B, 2B, 3B), even thou we can see this after clicking the path link and validate the RPT identity Bytes it was soo much better to have this on the conversation window so we save some clicks.

🚦 Current Behavior

There is no information on the msg hash mode in the message box.

🎯 Expected Behavior

In the message box, aligned with the name, date/time and path show 1B, 2B or 3B to inform the user on what is the hash mode the message was sent with.
Without having to click the paths link.

📋 Steps to Reproduce

na

📡 Radio Node

Firmware version: Meshcore-Dev 06-Jun-2026/v1.16.0-07a3ca9
Hardware / board type: Xiao S3 WIO

🔌 Connection to the Radio

Connected directly to the radio, or through an intermediary? Directly
Transport: Serial (USB)

💻 Environment Information

OS: Windows 11 x64
Browser / Version: MS Edge Version 150.0.4078.48 (Official build) (64-bit)
RemoteTerm Version: v3.16.0·560538a "wrapped" HA add-on/app

📸 Screenshots / Debug Logs

## 📝 Problem Description Feature Request: in the message box where there is the sender name, date/time and paths (link) show also the hash mode the message was sent with (1B, 2B, 3B), even thou we can see this after clicking the path link and validate the RPT identity Bytes it was soo much better to have this on the conversation window so we save some clicks. ## 🚦 Current Behavior There is no information on the msg hash mode in the message box. ## 🎯 Expected Behavior In the message box, aligned with the name, date/time and path show 1B, 2B or 3B to inform the user on what is the hash mode the message was sent with. Without having to click the paths link. ## 📋 Steps to Reproduce na ## 📡 Radio Node - **Firmware version:** Meshcore-Dev 06-Jun-2026/v1.16.0-07a3ca9 - **Hardware / board type:** Xiao S3 WIO ## 🔌 Connection to the Radio - **Connected directly to the radio, or through an intermediary?** Directly - **Transport:** Serial (USB) ## 💻 Environment Information - **OS:** Windows 11 x64 - **Browser / Version:** MS Edge Version 150.0.4078.48 (Official build) (64-bit) - **RemoteTerm Version:** v3.16.0·560538a "wrapped" HA add-on/app ## 📸 Screenshots / Debug Logs <img width="312" height="91" alt="Image" src="https://github.com/user-attachments/assets/428831a8-32b9-428d-857f-44fe9e928eb4" />

adam closed this issue

2026-10-05 02:05:19 +02:00

adam commented

2026-10-05 02:05:19 +02:00

Hmmm pathing width doesn't really feel to me like something's super useful to see on every single message. Things that are surfaced on every message need to have really high value for all users, in my opinion; I don't feel like this quite fits the bill. What's helpful in seeing width on all messages in every context?

Hmmm pathing width doesn't really feel to me like something's super useful to see on every single message. Things that are surfaced on every message need to have really high value for all users, in my opinion; I don't feel like this quite fits the bill. What's helpful in seeing width on all messages in every context?

adam commented

2026-10-05 02:05:20 +02:00

Hmmm pathing width doesn't really feel to me like something's super useful to see on every single message. Things that are surfaced on every message need to have really high value for all users, in my opinion; I don't feel like this quite fits the bill. What's helpful in seeing width on all messages in every context?

MeshCore is growing at fast passe all over the world, and 2B hash path is important in terms of observability and health (in terms of looking for geografic blind spots or RPT that need to be updated).
At least here in portugal we had a 2B day campaign (https://www.meshcore.pt/en/docs/tutorials/migration-to-2-byte) and we are trying to onboard people to change their clients and RPT to be configured with 2B.
So for us is of some value to have this front and center in the message so we can talk to the user and bring them to the 2B.

It doesn't occupies much space and is a nice to have info, even if it is going to duplicated every time the user sends a message.

> Hmmm pathing width doesn't really feel to me like something's super useful to see on every single message. Things that are surfaced on every message need to have really high value for all users, in my opinion; I don't feel like this quite fits the bill. What's helpful in seeing width on all messages in every context? MeshCore is growing at fast passe all over the world, and 2B hash path is important in terms of observability and health (in terms of looking for geografic blind spots or RPT that need to be updated). At least here in portugal we had a 2B day campaign (https://www.meshcore.pt/en/docs/tutorials/migration-to-2-byte) and we are trying to onboard people to change their clients and RPT to be configured with 2B. So for us is of some value to have this front and center in the message so we can talk to the user and bring them to the 2B. <img width="1001" height="110" alt="Image" src="https://github.com/user-attachments/assets/baacd513-989b-4cc7-a4b4-4682f75cf27b" /> It doesn't occupies much space and is a nice to have info, even if it is going to duplicated every time the user sends a message.

adam commented

2026-10-05 02:05:21 +02:00

Optional —

Optional — <img width="830" height="102" alt="Image" src="https://github.com/user-attachments/assets/f469e4f3-4b81-447e-9aa5-a26a3c14654c" />

adam commented

2026-10-05 02:05:22 +02:00

is it in the 3.16.2 image build?

is it in the 3.16.2 image build?

adam commented

2026-10-05 02:05:22 +02:00

No, haven't made a build for it yet. Will hopefully get to that tomorrow (Mon). Been pretty sick the last couple days and kinda overdid it today. Sorry

No, haven't made a build for it yet. Will hopefully get to that tomorrow (Mon). Been pretty sick the last couple days and kinda overdid it today. Sorry

adam commented

2026-10-05 02:05:23 +02:00

No, haven't made a build for it yet. Will hopefully get to that tomorrow (Mon). Been pretty sick the last couple days and kinda overdid it today. Sorry

Again, no sorry.
You have been doing a wonderfull job and your project is one of my favorites, excelent work.
Just protect yourself, this is not a life saving project with a deadline, do it at your own pace.
My only ask is when answering the issues, just give some feedback on if it is on the dev queue or already in the main image build to leverage expectations.

Thanks again, rest and drink plenty of water (in Portugal our soups do wonders :D ).

> No, haven't made a build for it yet. Will hopefully get to that tomorrow (Mon). Been pretty sick the last couple days and kinda overdid it today. Sorry Again, no sorry. You have been doing a wonderfull job and your project is one of my favorites, excelent work. Just protect yourself, this is not a life saving project with a deadline, do it at your own pace. My only ask is when answering the issues, just give some feedback on if it is on the dev queue or already in the main image build to leverage expectations. Thanks again, rest and drink plenty of water (in Portugal our soups do wonders :D ).

adam commented

2026-10-05 02:05:23 +02:00

Yes, it is working as expected.

Yes, it is working as expected. <img width="367" height="560" alt="Image" src="https://github.com/user-attachments/assets/85d4f5fd-e86d-4df1-9cb0-298fd80a8011" />

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#235