You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: