| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Ensures that automatic replies are sent back on the same channel index the message was received on. Previously, all replies defaulted to the primary channel (0), even if the incoming message arrived on a secondary channel. Additionally it ensures incoming messages match the specified channel index. E.g: meshtastic --ch-index 1 --reply . Modified the `onReceive` handler to extract the `channel` index from received packets. This ensures `interface.sendText` targets the originating channel rather than always defaulting to the primary channel. Added a filter to ensure that only the specified channel index is being replied to.
|
Thanks for the pull request! I've merged it and also added a bit of a note to the --reply command line help noting the behavior when --ch-index is provided. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes an issue where automatic replies generated by the --reply flag were incorrectly routed and unfiltered.
Changes
Channel Routing: Responses are now explicitly sent back on the same channel index the message was received on, rather than defaulting to the primary channel (0).
Channel Filtering: The --reply action now respects the --ch-index flag. It will only trigger a response if the incoming message matches the user-specified channel.
Behavior Comparison
Command: meshtastic --ch-index 1 --reply
Technical Implementation
The onReceive handler now casts args.ch_index to an integer and performs a comparison against the channel field in the incoming packet before calling interface.sendText().