Files
meshing-around/modules
SudoRand 097cae6e94 Allow chunker to consolidate lines when possible
This allows the chunker to consolidate lines into significantly
fewer messages in many cases without exceeding the max chunk size.

Without this change, the chunker will either emit all lines in
one message (if it fits in a single chunk) or else each line will be in
a separate message. This often creates a long series of short messages,
which doesn't transmit as quickly or display as compact.

Instead, this consolidates as many lines as possible into each
message, while being sure to stay within the chunk size limit.
This should reduce the load on the mesh, and it's also more readable.
2025-07-14 12:27:14 -06:00
..
2025-04-24 15:54:47 -07:00
2025-03-30 11:49:54 -07:00
2025-01-20 11:27:25 -08:00
2025-01-23 17:49:04 -08:00
2024-12-13 12:30:49 -08:00
2025-06-26 19:30:33 -07:00
2025-06-06 17:54:31 -07:00
2025-02-19 18:21:43 -08:00
2025-02-05 19:09:16 -08:00
2024-08-07 22:46:30 -07:00
2025-04-11 14:51:50 -07:00
2025-06-18 12:14:14 -07:00
2024-12-09 21:56:35 -08:00
2024-12-17 22:57:14 -08:00
2025-04-23 07:17:02 -07:00
2024-12-17 20:32:07 -08:00

Modules and Adding stuff

To help with code testing see etc/simulator.py to simulate a bot. I also enjoy meshtasticd(linux-native) in noradio with MQTT server and client to just emulate a mesh.

By following these steps, you can add a new bbs option to the bot.

  1. Define the Command Handler: Add a new function in mesh_bot.py to handle the new command. For example, if you want to add a command newcommand:

    def handle_newcommand(message, message_from_id, deviceID):
        return "This is a response from the new command."
    

    Additionally you can add a whole new module.py, I recommend doing this if you need to import more stuff, try and wedge it into similar spots if you can. You will need to import the file as well, look further at modules/system.py for more.

  2. Add the Command to the Auto Response: Update the auto_response function in mesh_bot.py to include the new command:

    def auto_response(message, snr, rssi, hop, pkiStatus, message_from_id, channel_number, deviceID, isDM):
        #...
        "newcommand": lambda: handle_newcommand(message, message_from_id, deviceID),
        #...
    
  3. Update the Trap List and Help: A quick way to do this is to edit the line 16/17 in modules/system.py to include the new command:

    #...
    trap_list = ("cmd", "cmd?", "newcommand")  # default trap list, with the new command added
    help_message = "Bot CMD?:newcommand, "
    #...
    

    If looking to merge the prefered way would be to update modules/system.py Adding this block below ping which ends around line 28:

    # newcommand Configuration
    newcommand_enabled = True  # settings.py handles the config.ini values; this is a placeholder
    if newcommand_enabled:
         trap_list_newcommand = ("newcommand",)
         trap_list = trap_list + trap_list_newcommand
         help_message = help_message + ", newcommand"
    
  4. Test the New Command: Run MeshBot and test the new command by sending a message with the command newcommand to ensure it responds correctly.

Running a Shell command

Using the above example and enabling the filemon module, you can make a command which calls a bash file to do things on the system.

def auto_response(message, snr, rssi, hop, pkiStatus, message_from_id, channel_number, deviceID, isDM):
    #...
    "switchON": lambda: call_external_script(message)

This would call the default script located in script/runShell.sh and return its output.