Scan Neighbor Repeaters: Can neither add nor view details of repeaters discovered via discovery protocol. #171

New Issue

2026-10-27T15:42:12+01:00

adam commented

2026-10-27 15:42:12 +01:00

(This is an issue initially reported in "Collected issues for firmware version 0.9.11.", which I now split up into individual reports to be able to track them better.)

Describe the bug

Mgmt → Advert → Scan Rpts:
According to release notes:

Mgmt → Advert → Scan Neighbor Repeaters now shows an Add button only for repeaters not yet in Contacts, and tapping a repeater row opens Contact Detail instead of adding on name/row tap.

For repeaters which were discovered via the "scan" feature, only the 1-byte prefix of the hash is known (no full advert is sent out by the repeater via this functionality).

In firmware version 0.9.10, those repeaters could be added with an "Add" button. Now they cannot. It is not clear weather they cannot because there is at least one repeater with the same prefix already in the contacts list or not; when I tap a so-discovered repeater it only says "no key" and not a more verbose message like "repeater(s) with that prefix already in contact list: [list of multiple repeaters with that prefix]".

Which device are you using

LilyGO T-Deck Plus

Which Firmware are you using

"MC-Term", version 0.9.11.

To Reproduce

Go to Mgmt → Advert → Scan Rpts.
If not already scanning, tap Scan.
See some repeaters with 1-byte has prefix coming up.
Miss an add button, and tapping on them also miss detailed information (only see a "No key" pupup).

Expected behaviour

Able to either add those repeaters, or see information about already known repeaters with the same has prefix.

Regards!

*(This is an issue initially reported in "[Collected issues for firmware version 0.9.11.](https://github.com/dabeani/meshcoreterm/issues/147)", which I now split up into individual reports to be able to track them better.)* ### Describe the bug `Mgmt` → `Advert` → `Scan Rpts`: According to [release notes](https://github.com/dabeani/meshcore/releases/tag/v0.9.11): > *`Mgmt` → `Advert` → `Scan Neighbor Repeaters` now shows an Add button only for repeaters not yet in Contacts, and tapping a repeater row opens Contact Detail instead of adding on name/row tap.* For repeaters which were discovered via the "scan" feature, only the 1-byte prefix of the hash is known (no full advert is sent out by the repeater via this functionality). In firmware version 0.9.10, those repeaters could be added with an "Add" button. Now they cannot. It is not clear weather they cannot because there is at least one repeater with the same prefix already in the contacts list or not; when I tap a so-discovered repeater it only says "*no key*" and not a more verbose message like "*repeater(s) with that prefix already in contact list: \[list of multiple repeaters with that prefix\]*". ### Which device are you using LilyGO T-Deck Plus ### Which Firmware are you using ["MC-Term", version 0.9.11](https://github.com/dabeani/meshcoreterm/releases/tag/v0.9.11). ### To Reproduce 1. Go to `Mgmt` → `Advert` → `Scan Rpts`. 2. If not already scanning, tap `Scan`. 3. See some repeaters with 1-byte has prefix coming up. 4. Miss an add button, and tapping on them also miss detailed information (only see a "`No key`" pupup). ### Expected behaviour Able to either add those repeaters, or see information about already known repeaters with the same has prefix. Regards!

adam closed this issue

2026-10-27 15:42:12 +01:00

adam commented

2026-10-27 15:42:13 +01:00

improved in v0.9.12

Mgmt/Advert Scan Rpts now handles prefix-only repeater matches correctly
- Known repeaters discovered by scan now show their saved contact names and open contact detail on row tap
- When only a short prefix is known and multiple contacts share it, the UI now explains the ambiguity instead of showing a generic key-missing message
- Repeaters that are not yet in Contacts can now be added directly when a unique full identity can be resolved from recent scan results

improved in v0.9.12 - **Mgmt/Advert Scan Rpts now handles prefix-only repeater matches correctly** - Known repeaters discovered by scan now show their saved contact names and open contact detail on row tap - When only a short prefix is known and multiple contacts share it, the UI now explains the ambiguity instead of showing a generic key-missing message - Repeaters that are not yet in Contacts can now be added directly when a unique full identity can be resolved from recent scan results

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/meshcore#171