Benjamin Faershtein
Benjamin Faershtein
Its not a firmware bug but rather client side
This should not be allowed. That position packet should be sent without a want response.
Sample code ```c++ if (p->want_ack && p->to == NODENUM_BROADCAST && !IS_ONE_OF(p->decoded.portnum,meshtastic_PortNum_ATAK_PLUGIN,meshtastic_PortNum_ATAK_FORWARDER,meshtastic_PortNum_TRACEROUTE_APP)) { LOG_WARN("Broadcast packet requested ACK, ignoring!"); p->want_ack = false; // Can't ACK broadcast packets } ```
Sorry I meant want response. I don't believe that want response broadcast packets should be sent at all.
Nodes should decide when to reply to a unknown nodes node info without a want response. In large meshes these sorts of packets create tons of traffic. I think that...
They send out their own node info and other nodes will automatically initiate exchange since it's unknown
I don't think that this is a common thing. Someone who resets their node db should understand that.
Wait for the nodes to advertise their node info
Hello, are there any updates on this?