mirror of
https://github.com/jkingsman/Remote-Terminal-for-MeshCore.git
synced 2026-11-03 08:02:19 +01:00
New Feature: Add repeater neighbors remove / discover #103
Assignees
adam (Adam Wojcieszonek)
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: adam/Remote-Terminal-for-MeshCore#103
Reference in new issue
Block a user
Add new features added to repeaters with 1.14.0. Button to delete the neighbor list and a button to have the repeater send out a discovery request.
Hm interesting. I assume this is also exposed via CLI? I tried to balance the "things you do a lot" (advertise, etc.) with buttons and allow the rest of repeater admin to be CLI based using the CLI panel.
Also means I don't need to worry about repeater feature detection as new versions roll out; I'd prefer to not do the back and forth to get firmware info before exposing UI elements, and if it's doable via the CLI, all the better.
So the query you already have via the 'refresh button' is 'neighbors' command.
New ones that would be nice to have at the top of the panel are 'discover.neighbors' which sends out a discovery request to proactively obtain neighbors and 'neighbors.remove ' (with two spaces instead of a prefix) which removes all neighbors from the list.
Remove a neighbor
Usage: - neighbor.remove <pubkey_prefix>
Parameters: - pubkey_prefix: The public key of the node to remove from the neighbors list. This can be a short prefix or the full key. All neighbors matching the provided prefix will be removed.
Note: You can remove all neighbors by sending a space character as the prefix. The space indicates an empty prefix, which matches all existing neighbors.
Hm, I'm trying to think of a situation this would be used in that's common enough for justifying interface clutter or mis-clicks, and I'm having trouble. Help me with a compelling argument for why this should be a new button instead of just a CLI command?
I can't speak for everybody but I use the RemoteTerm interface a lot for
repeater management. Why have the neighbor screen at all in the interface
if you can't easily manipulate it without having to remember the console
commands? This feature request would also match the interface capability in
RemoteTerm to that of the meshcore apps which don't require you to use the
console commands.
On Thu, Apr 2, 2026 at 1:29 PM Jack Kingsman @.***>
wrote:
Up until this issue I had no idea that you could flush that out; I just liked to look at it lmao 😂
I'm not sure I feel like this is something the average user would be doing frequently enough that it merits two new buttons. I will think on this.
Okay after some research, the neighbors list isn't actually used for anything -- it's just a metadata store for you to see who you've heard. It doesn't drive any routing decisions or do anything meaningful. As such, I'm going to keep this a CLI-only command for now, which are simple to execute with the CLI interface we expose at the bottom. I don't think this functionality is common/vital enough to justify a standalone button, sorry!