Before submitting

• I have searched existing issues to make sure this bug hasn't already been reported
• I have updated to the latest version of the software to verify the issue still exists

Firmware Version

2.6.11.60ec05e

What did you do?

Make sure Range Test is completely disabled on your connected node, then, using a secondary node on the same mesh, enable Range Test with a non-zero interval (say, 30).

Expected Behavior

Since the firmware still forwards those packets to the connected app, if the app sees the module is disabled, it should suppress displaying those received packets from other nodes.

Current Behavior

If the Range Test module is disabled in the connected node's settings, the app still shows received "seq" packets on the channel that the packet was received in if another nearby node has the module enabled and beaconing.

Participation

• I am willing to submit a pull request for this issue.

Additional comments

No response

Code of Conduct

• I agree to follow this project's Code of Conduct