meshtastic / protobufs

Protobuf definitions for the Meshtastic project
https://meshtastic.org
GNU General Public License v3.0
73 stars 107 forks source link

Add via_mqtt and hops_away to NodeInfo/Lite #456

Closed thebentern closed 4 months ago

thebentern commented 4 months ago

The intent of these changes is to reveal some insights to the user about how the delivery is happening over the mesh per node. Clients should be able to inform users if a node was seen over the internet via MQTT, if it's a direct neighbor, or witnessed over one of more hops from other nodes in the mesh.

thebentern commented 4 months ago

Looks good. Only thing is that for now a value of 0 for hops_away may mean direct neighbor or unknown (meaning firmware of the original transmitter is too old).

We could do a nested message if we wanted to handle this like the Channel's module settings for position precision. Transport { via_mqtt = 1, hops_away = 2 } I believe that incurs a slight penalty in the total protobuf size.

mc-hamster commented 4 months ago

this has come up a few times! very exciting!