Hi!
Running a node-red instance here and made a python parser to decode the protobufs with the help of your library and the one of meshtastic-mqtt.
There is a huge difference in snr readings (i know that they are differing each time) depending on type of message is arriving and wanted to ask you to have a look on that.
On a node-info message I see two types where the snr reading in my case is very low with -16 for example and in another message there is no snr reading which I replace with a zero reading:
"{"from_nodenr": "3215539008","via_gw": "!bfa93b40","nodeid": "!bfa93b40", "longname": "OE1KFR", "shortname": "KFR55", "hw": "HELTEC_V1","snr": "0.0"}"
"{"from_nodenr": "3294249800","via_gw": "!bfa93b40","nodeid": "!c45a4348", "longname": "OE6KCH-8", "shortname": "KCH", "hw": "HELTEC_V1","snr": "-15.0"}"
But those snr reading are not presented in the meshtastic-python cli when using meshtastic–nodes. In the position app there is sometimes also either no snr reading or ther is one. It seems like that those snr readings are presented in meshtastic-python cli are always from the next hop node, but what are the other readings? How I receive my next hop? Seems like that.
"{"from_nodenr": "3215540984","via_gw": "!bfa93b40","latitude": "0.0","longitude": "0.0","snr": "10.25"}"
"{"from_nodenr": "2475140972","via_gw": "!bfa93b40","latitude": "47.0806854","longitude": "15.4181099","snr": "-15.25"}"
thx for clearing me up
Rainer