Checklist
Contact Details
domusonline
Feature or improvement you want
There's a pending PR for the firmware ( meshtastic/firmware#10046 ) that hopes to end the ambiguity of showing 0.0dB on traceroutes for MQTT (and UDP) hops.
It was suggested, and agreed by the PR author (me), that it would be better to implement the application side changes also to minimize the confusion that could be caused by changing the firmware without changing the APP(s).
The proposed change for the firmware will save specific SNR for each of the currently known situations:
-128 for unknown hops (already in the firmware and addressed in the APP also)
-127 for signaling MQTT hop
127 for sigaling UDP hop
Ideally the APP should also adapt the display to the two new values showing "MQTT" for -127 and "UDP" for 127.
This is a simple change which I have tested myself. I believe I can propose a PR assuming there isn't any negative decision on this request. To get a graphic idea of the objective you can check the screenshot below
Why should this be added?
The current implementation will show 0.0dB which in fact is a very "normal" RF level, so the displayed information is ambiguous.
Note that with the zero hop policy in the default MQTT server this is probably not an issue, but different local meshes tend to use customized MQTT servers which may allow being transversed by Traceroutes.
Also note that with the change in the firmware PR, if there is no change in the APP we will start to see traces that show -31.75dB (for MQTT) and 31.75dB (for UDP). Although these are not reasonable values (much less reasonable than 0.0dB at least), these values may cause confusion to users, thus this request attempts to minimize that.
Screenshots / Drawings / Technical details
Checklist
I have used the search function for OPEN ISSUES to see if someone else has already submitted the same feature request.
I have also used the search function for CLOSED ISSUES to see if the feature was already implemented and is just waiting to be released, or if the feature was rejected.
I will describe the request with as much detail as possible.
This request contains only one single feature, not a list of multiple (related) features.
I have read and understood the Contribution Guidelines.
I agree to follow this project's Code of Conduct
Contact Details
domusonline
Feature or improvement you want
There's a pending PR for the firmware ( meshtastic/firmware#10046 ) that hopes to end the ambiguity of showing 0.0dB on traceroutes for MQTT (and UDP) hops.
It was suggested, and agreed by the PR author (me), that it would be better to implement the application side changes also to minimize the confusion that could be caused by changing the firmware without changing the APP(s).
The proposed change for the firmware will save specific SNR for each of the currently known situations:
-128 for unknown hops (already in the firmware and addressed in the APP also)
-127 for signaling MQTT hop
127 for sigaling UDP hop
Ideally the APP should also adapt the display to the two new values showing "MQTT" for -127 and "UDP" for 127.
This is a simple change which I have tested myself. I believe I can propose a PR assuming there isn't any negative decision on this request. To get a graphic idea of the objective you can check the screenshot below
Why should this be added?
The current implementation will show 0.0dB which in fact is a very "normal" RF level, so the displayed information is ambiguous.
Note that with the zero hop policy in the default MQTT server this is probably not an issue, but different local meshes tend to use customized MQTT servers which may allow being transversed by Traceroutes.
Also note that with the change in the firmware PR, if there is no change in the APP we will start to see traces that show -31.75dB (for MQTT) and 31.75dB (for UDP). Although these are not reasonable values (much less reasonable than 0.0dB at least), these values may cause confusion to users, thus this request attempts to minimize that.
Screenshots / Drawings / Technical details