[Feature Request]: Range Test - User Selectable Channel

[elliottkopp]

Platform

Cross-Platform

Description

It would be nice if we could select the channel we'd like to broadcast range test packets on.

Justification:

• Reduces mesh noise. The current behavior is to use the primary channel. In most cases this is LongFast. This will spam everyone in that channel with range test packets unnecessarily.
• Reduces MQTT noise. In addition to above, if MQTT uplink is enabled on any device that receives a range test packet, it gets forwarded to MQTT causing noise there as well. (Probably a separate issue limiting range test to LoRa for that since MQTT is not useful for range test anyway).

How this manifests itself in the various client apps can be left up to those client apps. As long as the firmware supports it that's the most important part.

Thank you!

[github-actions]

@elliottkopp, Welcome to Meshtastic! 👋

Thanks for opening your first issue. If it's helpful, an easy way
to get logs is the "Open Serial Monitor" button on the Web Flasher.

If you have ideas for features, note that we often debate big ideas
in the discussions tab
first. This tracker tends to be for ideas that have community
consensus and a clear implementation.

We're very active on discord,
especially the #firmware and #alphanauts-testing channels. If you'll
be around for a while, we'd love to see you there!

Welcome to the community! ❤️

[domusonline]

A couple of comments:

• Avoiding RangeTest to enter MQTT is an obvious idea. And from what I've seen in the code recently it should be really easy to implement. Once I have time I could take that...
• Specifying the channel should be applicable to any module. So agreed on this one also
• It puzzles me why a user without the module active sees the "Seq" messages. A few weeks ago this only happened on iOS. Now it also happens on Android. But to be honest I don't understand why this should depend on the application... The firmware should not send it to the app if the module is off. The drawback of doing this is that it may go unnoticed (this also applies to the first observation...)