[Feature Request]: Triggering NodeInfo send from application

[phaseloop]

Contact Details

No response

Tell us your idea.

Meshtastic firmware allows to trigger sending NodeInfo packet (out of schedule) by fast pressing button twice.

It is convenient for testing radio propagation and connectivity to check online which MQTT nodes received our packet (without need to wait for scheduled NodeInfo which may happen 2-3h later).

It would be great to be able to trigger that from the application.

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct

[b8b8]

Actual nodeinfo can be sent as frequently as every 3 min should your node (or another node) get a packet from a node not yet on the node list. The 3 hour minimum for nodeinfo is only for automatic broadcast interval, not if the node is explicitly asked to produce said nodeinfo to identify an unknown node. Any unknown node packet will trigger this nodeinfo request up to 3 min in frequency.

[madeofstown]

I think this is a great idea. I would also like to see a way to send position data to the mesh triggered from the app (instead of requesting).

[b8b8]

I think this is a great idea. I would also like to see a way to send position data to the mesh triggered from the app (instead of requesting).

Request position is actually "exchange position" its named as such in the iOS app but it does the same thing in both apps.

Request user info works in the android app.

[madeofstown]

Request user info works in the android app.

Does "Request user info" function similarly to exchange position? If I request user info am I sending my user info out? This is the function that OP wants: transmit user info, initiated from the app.

[garthvh]

The double click functionality sends a position packet and falls back to a node info if a position is not available. The node info is sent out when necessary for DM's automatically, really no reason to impatiently request it manually.

[madeofstown]

Garthvh really hates node info broadcasts, lol.

It can be done from the physical device, it can be done from the python command. I think people were just hoping it might get implemented in the apps too. I guess we have our answer.

[Kealper]

Request user info works the same way as Request position in the app, it actually send out your data (user info packet or position packet) over the primary channel with the specified node as the target with a flag on it that basically tells the node at the other end "here's my data, please reply back with yours".

Personally, I wouldn't be opposed to renaming those to match the iOS app's names since it would make it a lot more apparent how they work under the hood that way.