Map: Node badges: Number of bytes shown sometimes depends on on-device path hash setting, for other nodes it is fixed. What is going on? | [Suggestion] Make this explicitly configurable and fixed in Map settings. #302

New Issue

2026-10-27T15:48:36+01:00

adam commented

2026-10-27 15:48:36 +01:00

I don't know what this is exactly, so I do not give it the Bug label.

I describe my findings:

Some badges on the map display 1 byte, 2 byte or 3 byte prefix depending on the own on-device-setting Mgmt → Advert → Path Hash Mode.
Others always display as 2 byte, or 1 byte, or 3 byte.
There is also a change of display depending on what is received (related was: #242) -- probably a received message with some path hash length does change what is displayed? -- Anyway, I observed that #242 in the narrow sense was solved, but when I came back after the night the badge of that affected repeater went back to 1 byte again.

So, maybe make it explicit how many bytes should be shown on the map node badges:

Add a setting in Map whether to show 1, 2 or 3 byte for a node badge,
if enough information is known, show that many bytes, otherwise show only what is known. (If we have a full advert, enough should be known anyway.)

Given that the length of the path hash of a message is not defined by a repeater anyway, but by the sending device, it makes not much sense in my opinion to have the repeater defining how it's badge is displayed.

Photographs:

Mgmt → Advert → Path Hash Mode set to 1-Byte:
Mgmt → Advert → Path Hash Mode set to 2-Byte:
Mgmt → Advert → Path Hash Mode set to 3-Byte:

Regards!

I don't know what this is exactly, so I do not give it the `Bug` label. I describe my findings: * Some badges on the map display 1 byte, 2 byte or 3 byte prefix depending on the _own_ on-device-setting `Mgmt` → `Advert` → `Path Hash Mode`. * Others always display as 2 byte, or 1 byte, or 3 byte. * There is also a change of display depending on what is received (related was: #242) -- probably a received message with some path hash length does change what is displayed? -- Anyway, I observed that #242 in the narrow sense was solved, but when I came back after the night the badge of that affected repeater went back to 1 byte again. So, maybe make it explicit how many bytes should be shown on the map node badges: * Add a setting in `Map` whether to show 1, 2 or 3 byte for a node badge, * if enough information is known, show that many bytes, otherwise show only what is known. (If we have a full advert, enough should be known anyway.) Given that the length of the path hash of a message is not defined by a repeater anyway, but by the _sending_ device, it makes not much sense in my opinion to have the repeater defining how it's badge is displayed. Photographs: * `Mgmt` → `Advert` → `Path Hash Mode` set to `1-Byte`: <img width="663" height="499" alt="Image" src="https://github.com/user-attachments/assets/9a93a3c9-08f5-45ec-8807-ca52a8915b11" /> * `Mgmt` → `Advert` → `Path Hash Mode` set to `2-Byte`: <img width="604" height="449" alt="Image" src="https://github.com/user-attachments/assets/b29da215-4f8f-4fce-a973-ecf6b5ba3725" /> * `Mgmt` → `Advert` → `Path Hash Mode` set to `3-Byte`: <img width="591" height="453" alt="Image" src="https://github.com/user-attachments/assets/b3e8cac2-e320-4538-8774-3cd00892d115" /> Regards!

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/meshcore#302

Map: Node badges: Number of bytes shown sometimes depends on on-device path hash setting, for other nodes it is fixed. What is going on? | [Suggestion] Make this explicitly configurable and fixed in Map settings. #302

Map: Node badges: Number of bytes shown sometimes depends on on-device path hash setting, for other nodes it is fixed. What is going on? | [Suggestion] Make this explicitly configurable and fixed in `Map` settings. #302