Closed asjmcguire closed 6 months ago
I think the RSSI and SNR readings in those cases still can be useful--they just need to be somehow linked to the neighbor that repeated the packet.
I think the RSSI and SNR readings in those cases still can be useful--they just need to be somehow linked to the neighbor that repeated the packet.
Which if I understand correctly from the firmware channel on discord, is not information that is available. The only node information is the original sender, nothing from any node the packet has passed through. Maybe V3 will change this, but there is nothing in V2.
EDIT: In fact the discussion was in the firmware github - https://github.com/meshtastic/firmware/issues/3239#issuecomment-1950227484 this message specifically
So many features we are missing out compared the iOS version
and more
For info I'm very very slowly working through this. Bear in mind I don't have any android experience and I'm using it as a learning example, so I can't say if what I'm doing will work.
After fiddling around for the past few days, I've finally worked out how to get the data. I'll tidy everything up and make UI elements for it.
Good result. One of the other devs has also added the info to the python cli --nodes table
The Android app currently lacks the display of how many hops away nodes are. The thing that would would make the most sense is to only display RSSI and SNR when hops away is zero, or missing. Because obviously since when it is 1 or more hops away, then the signal strength no longer makes sense, people think they have an excellent connection to a node, but really they only have an excellent connection to the 1st hop, the connection between the 1st hop and the destination node, or just the next hop, might be terrible, but that information is never communicated (or available) to the sender.
It makes more sense to show the number of hops in place of the RSSI and SNR when the hop is higher than zero.