Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: Admin message to request a refresh of the nodedb #4564

Open
garthvh opened this issue Aug 27, 2024 · 3 comments
Open

[Feature Request]: Admin message to request a refresh of the nodedb #4564

garthvh opened this issue Aug 27, 2024 · 3 comments
Labels
enhancement New feature or request high-priority Issues that affect core functionality or are "show stoppers" pinned Exclude from stale processing

Comments

@garthvh
Copy link
Member

garthvh commented Aug 27, 2024

Platform

NRF52, ESP32, RP2040, Linux Native

Description

Now that we have this in place #3740

We need to add a admin message that will refresh the node db, so that apps can separate connecting and the nodedb refresh, which takes a long time with 100 nodes.

@garthvh garthvh added the enhancement New feature or request label Aug 27, 2024
@caveman99 caveman99 added high-priority Issues that affect core functionality or are "show stoppers" pinned Exclude from stale processing labels Oct 30, 2024
@gjelsoe
Copy link
Contributor

gjelsoe commented Nov 20, 2024

@garthvh Is this a NodeDB::cleanupMeshDB() call you had in mind ?

@ianmcorvidae
Copy link
Contributor

I believe this issue is for adding an admin message that sets off the connection/want_config stage of sending all the nodes in NodeDB up to the phone via the API. That way the clients can connect with the nodeless wantconfig (and thus not require anyone to wait for all 80/100/possibly more to come through on initial connect), and then send the admin message after connection to get any updated node information to update their local datastores with. So basically an admin message to set off the stuff within the case STATE_SEND_OTHER_NODEINFOS block in PhoneAPI::available() I think

@gjelsoe
Copy link
Contributor

gjelsoe commented Nov 20, 2024

Oh I see....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request high-priority Issues that affect core functionality or are "show stoppers" pinned Exclude from stale processing
Projects
None yet
Development

No branches or pull requests

4 participants