- Added '*.key' to .gitignore to prevent tracking of key files. - Changed the default database path in config.ini.example from 'bot_data.db' to 'meshcore_bot.db' for clarity. - Enhanced documentation files with front matter for better rendering and organization, including Discord Bridge, Feed Management, Map Uploader, Packet Capture, Path Command Configuration, Repeater Management Commands, and Weather Service.
MeshCore Bot
A Python bot that connects to MeshCore mesh networks via serial port, BLE, or TCP/IP. The bot responds to messages containing configured keywords, executes commands, and provides various data services including weather, solar conditions, and satellite pass information.
Features
- Connection Methods: Serial port, BLE (Bluetooth Low Energy), or TCP/IP
- Keyword Responses: Configurable keyword-response pairs with template variables
- Command System: Plugin-based command architecture with built-in commands
- Rate Limiting: Configurable rate limiting to prevent network spam
- User Management: Ban/unban users with persistent storage
- Scheduled Messages: Send messages at configured times
- Direct Message Support: Respond to private messages
- Logging: Console and file logging with configurable levels
Service Plugins
- Discord Bridge: One-way webhook bridge to post mesh messages to Discord (docs)
- Packet Capture: Capture and publish packets to MQTT brokers (docs)
- Map Uploader: Upload node adverts to map.meshcore.dev (docs)
- Weather Service: Scheduled forecasts, alerts, and lightning detection (docs)
Requirements
- Python 3.7+
- MeshCore-compatible device (Heltec V3, RAK Wireless, etc.)
- USB cable or BLE capability
Installation
Quick Start (Development)
- Clone the repository:
git clone <repository-url>
cd meshcore-bot
- Install dependencies:
pip install -r requirements.txt
- Copy and configure the bot:
Full Configuration Option: This config.ini example enables all bot commands and provides full configuration options.
cp config.ini.example config.ini
# Edit config.ini with your settings
Minimal Configuration Option: For users who only want core testing commands (ping, test, path, prefix, multitest), you can use the minimal configuration instead:
cp config.ini.minimal-example config.ini
# Edit config.ini with your connection and bot settings
- Run the bot:
python3 meshcore_bot.py
Production Installation (Systemd Service)
For production deployment as a system service:
- Install as systemd service:
sudo ./install-service.sh
- Configure the bot:
sudo nano /opt/meshcore-bot/config.ini
- Start the service:
sudo systemctl start meshcore-bot
- Check status:
sudo systemctl status meshcore-bot
See SERVICE-INSTALLATION.md for detailed service installation instructions.
Docker Deployment
For containerized deployment using Docker:
-
Create data directories and configuration:
mkdir -p data/{config,databases,logs,backups} cp config.ini.example data/config/config.ini # Edit data/config/config.ini with your settings -
Update paths in config.ini to use
/data/directories:[Bot] db_path = /data/databases/meshcore_bot.db [Logging] log_file = /data/logs/meshcore_bot.log -
Build and start with Docker Compose:
docker compose build docker compose up -dOr build and start in one command:
docker compose up -d --build -
View logs:
docker-compose logs -f
See DOCKER.md for detailed Docker deployment instructions, including serial port access, web viewer configuration, and troubleshooting.
NixOS
Use the Nix flake via flake.nix
meshcore-bot.url = "github:agessaman/meshcore-bot/";
And in your system config
{
imports = [inputs.meshcore-bot.nixosModules.default];
services.meshcore-bot = {
enable = true;
webviewer.enable = true;
settings = {
Connection.connection_type = "serial";
Connection.serial_port = "/dev/ttyUSB0";
Bot.bot_name = "MyBot";
};
};
}
Configuration
The bot uses config.ini for all settings. Key configuration sections:
Connection
[Connection]
connection_type = serial # serial, ble, or tcp
serial_port = /dev/ttyUSB0 # Serial port path (for serial)
#hostname = 192.168.1.60 # TCP hostname/IP (for TCP)
#tcp_port = 5000 # TCP port (for TCP)
#ble_device_name = MeshCore # BLE device name (for BLE)
timeout = 30 # Connection timeout
Bot Settings
[Bot]
bot_name = MeshCoreBot # Bot identification name
enabled = true # Enable/disable bot
rate_limit_seconds = 2 # Rate limiting interval
startup_advert = flood # Send advert on startup
Keywords
[Keywords]
# Format: keyword = response_template
# Variables: {sender}, {connection_info}, {snr}, {timestamp}, {path}
test = "Message received from {sender} | {connection_info}"
help = "Bot Help: test, ping, help, hello, cmd, wx, aqi, sun, moon, solar, hfcond, satpass, dice, roll, joke, dadjoke, sports, channels, path, prefix, repeater, stats, alert"
Channels
[Channels]
monitor_channels = general,test,emergency # Channels to monitor
respond_to_dms = true # Enable DM responses
External Data APIs
[External_Data]
# API keys for external services
n2yo_api_key = # Satellite pass data
airnow_api_key = # Air quality data
Alert Command
[Alert_Command]
alert_enabled = true # Enable/disable alert command
max_incident_age_hours = 24 # Maximum age for incidents (hours)
max_distance_km = 20.0 # Maximum distance for proximity queries (km)
agency.city.<city_name> = <agency_ids> # City-specific agency IDs (e.g., agency.city.seattle = 17D20,17M15)
agency.county.<county_name> = <agency_ids> # County-specific agency IDs (aggregates all city agencies)
Logging
[Logging]
log_level = INFO # DEBUG, INFO, WARNING, ERROR, CRITICAL
log_file = meshcore_bot.log # Log file path
colored_output = true # Enable colored console output
Usage
Running the Bot
python meshcore_bot.py
Available Commands
For a comprehensive list of all available commands with examples and detailed explanations, see COMMANDS.md.
Quick reference:
- Basic:
test,ping,help,hello,cmd - Information:
wx,gwx,aqi,sun,moon,solar,solarforecast,hfcond,satpass,channels - Emergency:
alert - Gaming:
dice,roll,magic8 - Entertainment:
joke,dadjoke,hacker,catfact - Sports:
sports - MeshCore Utility:
path,prefix,stats,multitest,webviewer - Management (DM only):
repeater,advert,feed,announcements,greeter
Message Response Templates
Keyword responses support these template variables:
{sender}- Sender's node ID{connection_info}- Connection details (direct/routed){snr}- Signal-to-noise ratio{timestamp}- Message timestamp{path}- Message routing path
Adding Newlines
To add newlines in keyword responses, use \n (single backslash + n):
[Keywords]
test = "Line 1\nLine 2\nLine 3"
This will output:
Line 1
Line 2
Line 3
To use a literal backslash + n, use \\n (double backslash + n).
Other escape sequences: \t (tab), \r (carriage return), \\ (literal backslash)
Example:
[Keywords]
test = "Message received from {sender} | {connection_info}"
ping = "Pong!"
help = "Bot Help: test, ping, help, hello, cmd, wx, gwx, aqi, sun, moon, solar, solarforecast, hfcond, satpass, dice, roll, joke, dadjoke, sports, channels, path, prefix, repeater, stats, multitest, alert, webviewer"
Hardware Setup
Serial Connection
- Flash MeshCore firmware to your device
- Connect via USB
- Configure serial port in
config.ini:[Connection] connection_type = serial serial_port = /dev/ttyUSB0 # Linux # serial_port = COM3 # Windows # serial_port = /dev/tty.usbserial-* # macOS
BLE Connection
- Ensure your MeshCore device supports BLE
- Configure BLE in
config.ini:[Connection] connection_type = ble ble_device_name = MeshCore
TCP Connection
- Ensure your MeshCore device has TCP/IP connectivity (e.g., via gateway or bridge)
- Configure TCP in
config.ini:[Connection] connection_type = tcp hostname = 192.168.1.60 # IP address or hostname tcp_port = 5000 # TCP port (default: 5000)
Troubleshooting
Common Issues
-
Serial Port Not Found:
- Check device connection
- Verify port name in config
- List available ports:
python -c "import serial.tools.list_ports; print([p.device for p in serial.tools.list_ports.comports()])"
-
BLE Connection Issues:
- Ensure device is discoverable
- Check device name in config
- Verify BLE permissions
-
TCP Connection Issues:
- Verify hostname/IP address is correct
- Check that TCP port is open and accessible
- Ensure network connectivity to the device
- Verify the MeshCore device supports TCP connections
- Check firewall settings if connection fails
-
Message Parsing Errors:
- Enable DEBUG logging for detailed information
- Check meshcore library documentation for protocol details
-
Rate Limiting:
- Adjust
rate_limit_secondsin config - Check logs for rate limiting messages
- Adjust
Debug Mode
Enable debug logging:
[Logging]
log_level = DEBUG
Architecture
The bot uses a modular plugin architecture:
- Core modules (
modules/): Shared utilities and core functionality - Command plugins (
modules/commands/): Individual command implementations - Service plugins (
modules/service_plugins/): Background services (Discord bridge, packet capture, etc.) - Plugin loaders: Dynamic discovery and loading of command and service plugins
- Message handler: Processes incoming messages and routes to appropriate handlers
Adding New Plugins
Command Plugin:
- Create a new file in
modules/commands/ - Inherit from
BaseCommand - Implement the
execute()method - The plugin loader will automatically discover and load it
from .base_command import BaseCommand
from ..models import MeshMessage
class MyCommand(BaseCommand):
name = "mycommand"
keywords = ['mycommand']
description = "My custom command"
async def execute(self, message: MeshMessage) -> bool:
await self.send_response(message, "Hello from my command!")
return True
Service Plugin:
- Create a new file in
modules/service_plugins/ - Inherit from
BaseServicePlugin - Implement
start()andstop()methods - Add configuration section to
config.ini.example
Contributing
- Fork the repository
- Create a feature branch
- Make your changes
- Submit a pull request against the dev branch
License
This project is licensed under the MIT License.
Acknowledgments
- MeshCore Project for the mesh networking protocol
- Some commands adapted from MeshingAround bot by K7MHI Kelly Keeton 2024
- Packet capture service based on meshcore-packet-capture by agessaman
- meshcore-decoder by Michael Hart for client-side packet decoding and decryption in the web viewer