v0.8.2

- Added a version indicator to the bottom of the Web Viewer
- Added ability to filter by packet type in Packet Capture Service.
- Improved mesh graph efficiency, added documentation for how to configure mesh graph calculations (or disable it) on lightweight nodes like Raspberry Pi Zero 2s.
- Simplify contact removal logic. Occasional errors will still occur until race condition in meshcore_py 
- Improvements to documentation.

Author: agessaman

.github/workflows/docker-build.yml

@@ -57,13 +57,24 @@ jobs:
             type=sha,prefix=sha-
             type=raw,value=latest,enable=${{ github.ref == 'refs/heads/main' || github.ref == 'refs/heads/master' }}
 
+      - name: Set version for web viewer footer
+        id: version
+        run: |
+          if [[ "${{ github.ref }}" == refs/tags/* ]]; then
+            echo "version=${{ github.ref_name }}" >> $GITHUB_OUTPUT
+          else
+            echo "version=dev" >> $GITHUB_OUTPUT
+          fi
+
       - name: Build and push Docker image
         uses: docker/build-push-action@v5
         with:
           context: .
           push: ${{ github.event_name != 'pull_request' }}
           tags: ${{ steps.meta.outputs.tags }}
           labels: ${{ steps.meta.outputs.labels }}
+          build-args: |
+            MESHCORE_BOT_VERSION=${{ steps.version.outputs.version }}
           cache-from: type=gha
           cache-to: type=gha,mode=max
           platforms: linux/amd64,linux/arm64

Dockerfile

@@ -43,6 +43,10 @@ COPY --from=builder /root/.local /home/meshcore/.local
 # Set working directory
 WORKDIR /app
 
+# Version for web viewer footer (set at build time; e.g. --build-arg MESHCORE_BOT_VERSION=v1.2.3)
+ARG MESHCORE_BOT_VERSION
+ENV MESHCORE_BOT_VERSION=${MESHCORE_BOT_VERSION}
+
 # Copy application files
 COPY --chown=meshcore:meshcore . /app/
 

config.ini.example

@@ -801,11 +801,25 @@ graph_path_validation_max_bonus = 0.3
 # Lower values = stronger bonus from observation count. 50.0 means 50 observations = 0.15 bonus
 graph_path_validation_obs_divisor = 50.0
 
-# Load only recent edges on startup (days, 0 = load all)
-# Useful for large graphs. Set to 0 to load all edges, or N to load only edges seen in last N days.
-# For development with frequent restarts, 0 (load all) is recommended to maintain graph quality
+# Load only recent edges on startup (days, 0 = load all historical edges)
+# Edges older than this are skipped at startup to bound initial memory usage.
+# The in-code default is 14 days when this setting is absent from config.ini.
+# Recommended values:
+#   0  - Load all historical edges (servers with ample RAM, e.g. x86 VM)
+#   14 - Good balance of coverage vs. memory (default for unconfigured installs)
+#   7  - Reduced memory footprint for Raspberry Pi Zero 2 W
+# Note: edges older than graph_edge_expiration_days are never loaded regardless of this value.
 graph_startup_load_days = 0
 
+# Enable graph data capture from incoming packets (default: true)
+# When true, the bot observes routing paths from advertisements, messages, and trace
+# packets and stores edges in the mesh graph.
+# When false, NO new edge data is collected and the background batch writer thread is
+# not started — reducing both CPU and RAM overhead. Any edges already in the database
+# are still available for graph_based_validation if that is also enabled.
+# Set to false on devices that don't use the path command and want minimal overhead.
+graph_capture_enabled = true
+
 # Star bias multiplier for path command
 # When a contact is starred in the web viewer, multiply its selection score by this value
 # Higher values = stronger preference for starred repeaters
@@ -1224,6 +1238,7 @@ mqtt_enabled = true
 # mqttN_topic_packets =               # Packets topic template (uses placeholders below)
 # mqttN_topic_prefix =                # Legacy topic prefix (fallback if topic_status/topic_packets not set)
 # mqttN_client_id =                   # MQTT client ID (optional, auto-generated from bot name)
+# mqttN_upload_packet_types =         # Comma-separated packet types to upload (e.g. 2,4); empty = all
 #
 # Topic template placeholders:
 # {IATA} - Uppercase IATA code (e.g., SEA)
@@ -1243,6 +1258,7 @@ mqtt1_topic_status = meshcore/{IATA}/{PUBLIC_KEY}/status
 mqtt1_topic_packets = meshcore/{IATA}/{PUBLIC_KEY}/packets
 mqtt1_websocket_path = /mqtt
 mqtt1_client_id = 
+mqtt1_upload_packet_types = 
 
 # MQTT Broker 2 - Let's Mesh Analyzer (EU)
 mqtt2_enabled = true
@@ -1256,6 +1272,7 @@ mqtt2_topic_status = meshcore/{IATA}/{PUBLIC_KEY}/status
 mqtt2_topic_packets = meshcore/{IATA}/{PUBLIC_KEY}/packets
 mqtt2_websocket_path = /mqtt
 mqtt2_client_id = 
+mqtt2_upload_packet_types = 
 
 # Stats and status publishing
 # Enable stats in status messages

docs/faq.md

@@ -27,3 +27,52 @@ Without `--upgrade`, the script does *not* update the service file (systemd/laun
 ### How can I generate a custom command reference for my bot users?
 
 See [Custom command reference website](command-reference-website.md): it explains how to use `generate_website.py` to build a single-page HTML from your config (with optional styles) and upload it to your site.
+
+## Hardware and performance
+
+### How do I run meshcore-bot on a Raspberry Pi Zero 2 W?
+
+The Pi Zero 2 W has 512 MB of RAM. The bot and the web viewer are two separate
+Python processes; together they use roughly 300 MB on a busy mesh, which leaves
+little headroom. Follow the two steps below to keep things comfortable.
+
+#### Step 1 — Run the bot only (saves ~150 MB)
+
+The web viewer is optional. If you don't need the browser-based dashboard on
+the Pi itself, disable it and access it from another machine instead:
+
+```ini
+[Web_Viewer]
+enabled = false
+auto_start = false
+```
+
+The bot continues to work normally; the web viewer just won't start on the Pi.
+If you still want the dashboard, run the viewer on a desktop or server that
+shares the same database file (see [MeshCore Bot Data Viewer](web-viewer.md)).
+
+#### Step 2 — Tune the Mesh Graph (saves another 50–100 MB on busy meshes)
+
+Even with the web viewer off, the Mesh Graph can grow large. Add the following
+to the `[Path_Command]` section of your `config.ini`:
+
+```ini
+[Path_Command]
+# Limit startup memory: only load edges seen in the last 7 days.
+# Edges older than this have near-zero path confidence anyway.
+graph_startup_load_days = 7
+
+# Evict edges from RAM after 7 days without a new observation.
+graph_edge_expiration_days = 7
+
+# Write graph updates in batches rather than on every packet.
+graph_write_strategy = batched
+
+# If you don't use the !path command at all, disable graph capture
+# entirely to eliminate the background thread and all graph overhead.
+# graph_capture_enabled = false
+```
+
+These settings do not affect path prediction accuracy: edges older than a few
+days carry negligible confidence due to the 48-hour recency half-life used by
+the scoring algorithm.

docs/packet-capture.md

@@ -85,6 +85,37 @@ mqtt2_username = user
 mqtt2_password = pass
 ```
 
+#### Filtering by packet type
+
+You can limit which packet types are uploaded to each broker with `mqttN_upload_packet_types`. Use a comma-separated list of type numbers; if unset or empty, all packet types are uploaded.
+
+```ini
+# Only upload text messages and adverts to this broker
+mqtt1_upload_packet_types = 2, 4
+
+# Broker 2 gets everything (default)
+# mqtt2_upload_packet_types =
+```
+
+**Packet type reference:**
+
+| Type | Name       | Description        |
+|------|------------|--------------------|
+| 0    | REQ        | Request            |
+| 1    | RESPONSE   | Response           |
+| 2    | TXT_MSG    | Text message       |
+| 3    | ACK        | Acknowledgment     |
+| 4    | ADVERT     | Advertisement      |
+| 5    | GRP_TXT    | Group text         |
+| 6    | GRP_DATA   | Group data         |
+| 7    | ANON_REQ   | Anonymous request  |
+| 8    | PATH       | Path               |
+| 9    | TRACE      | Trace              |
+| 10   | MULTIPART  | Multipart          |
+| 11–15| Type11–RAW_CUSTOM | Other types |
+
+Packets that are excluded by this filter are still written to the output file (if configured) and still counted; they are only skipped for MQTT upload to that broker. Debug logs will show "Skipping" for those packets.
+
 ### Topic Templates
 
 Placeholders:
@@ -170,8 +201,9 @@ Common issues:
 ### No Packets Being Published
 
 1. **Verify MQTT connection** - Check logs for "Connected to MQTT broker"
-2. **Check packet count** - Service logs "Captured packet #N" for each packet
+2. **Check packet count** - Service logs "Captured packet #N" (or "Skipping packet #N" when filtered) for each packet
 3. **Verify topics** - Ensure topics match broker expectations
+4. **Check upload filter** - If `mqttN_upload_packet_types` is set, only those types are uploaded. DEBUG Logs show "packet type X not in [Y, Z]" when a packet is skipped
 
 ---
 

docs/path-command-config.md

@@ -201,8 +201,15 @@ These settings control how graph edges are stored in the database.
 
 **`graph_startup_load_days`** (days, 0 = load all)
 - Load only edges seen in last N days on startup
-- `0` = load all edges (recommended for development)
-- Default: `0`
+- `0` = load all edges (use on servers with ample RAM)
+- Default: `14` (set to `0` in `config.ini` to load all)
+
+**`graph_capture_enabled`** (boolean)
+- When `false`, no new edge data is collected from packets and the background
+  batch writer thread is not started — reducing CPU and RAM overhead
+- Edges already in the database are still used for path validation
+- Set to `false` on devices that don't use the path command
+- Default: `true`
 
 ## Preset Configurations
 

docs/web-viewer.md

@@ -147,9 +147,73 @@ You can keep or remove the old `bot_data.db` file after verifying the viewer wor
 
 ## Troubleshooting
 
+### Web viewer not accessible (e.g. Orange Pi / SBC)
+
+If the viewer does not load from another device (e.g. from your phone or PC while the bot runs on an Orange Pi), work through these steps on the Pi.
+
+1. **Confirm config**
+   - In `config.ini` under `[Web_Viewer]`:
+     - `enabled = true`
+     - `auto_start = true` (if you want it to start with the bot)
+     - `host = 0.0.0.0` (required for access from other devices; `127.0.0.1` is localhost only)
+     - `port = 8080` (or another port 1024–65535)
+   - Restart the bot after changing config.
+
+2. **Check that the viewer process is running**
+   ```bash
+   # From project root on the Pi
+   ss -tlnp | grep 8080
+   # or
+   netstat -tlnp | grep 8080
+   ```
+   If nothing listens on your port, the viewer did not start or has exited.
+
+3. **Inspect viewer logs**
+   - When run by the bot, the viewer writes to:
+     - `logs/web_viewer_stdout.log`
+     - `logs/web_viewer_stderr.log`
+   - Look for Python tracebacks, "Address already in use", or missing dependencies (e.g. Flask, flask-socketio).
+   - Optional: run the viewer manually to see errors in the terminal:
+     ```bash
+     cd /path/to/meshcore-bot
+     python3 modules/web_viewer/app.py --config config.ini --host 0.0.0.0 --port 8080
+     ```
+
+4. **Check integration startup**
+   - Bot logs may show: `Web viewer integration failed: ...` or `Web viewer integration initialized`.
+   - If integration failed, the viewer subprocess is never started; fix the error shown (e.g. invalid `host` or `port` in config).
+
+5. **Firewall**
+   - Many SBC images (e.g. Orange Pi, Armbian minimal) do **not** ship with a firewall; if `curl` to localhost works and `host = 0.0.0.0`, the blocker may be network (Wi‑Fi client isolation, different subnet, or router). Check from a device on the same LAN using `http://<PI_IP>:8080`.
+   - If your system uses **ufw**:
+     ```bash
+     sudo ufw status
+     sudo ufw allow 8080/tcp
+     sudo ufw reload
+     ```
+   - If `ufw` is not installed (e.g. `sudo: ufw: command not found`), you may have no host firewall—that’s common on embedded images. To allow the port with **iptables** (often available when ufw is not):
+     ```bash
+     sudo iptables -I INPUT -p tcp --dport 8080 -j ACCEPT
+     ```
+     (Rules may not persist across reboots unless you use a persistence method for your distro.)
+   - If you prefer ufw, install it (e.g. `sudo apt install ufw`) and use the ufw commands above.
+
+6. **Test from the Pi first**
+   ```bash
+   curl -s -o /dev/null -w "%{http_code}" http://127.0.0.1:8080/
+   ```
+   If this returns `200`, the viewer is running and the issue is binding or firewall. If you use `host = 0.0.0.0`, then try from another device: `http://<PI_IP>:8080`.
+
+7. **Standalone run (no bot)**
+   - To rule out bot integration issues, start the viewer by itself (same config path so it finds the DB):
+     ```bash
+     python3 modules/web_viewer/app.py --config config.ini --host 0.0.0.0 --port 8080
+     ```
+   - If `restart_viewer.sh` is used, note it binds to `127.0.0.1` by default; for network access run the command above with `--host 0.0.0.0` or edit the script.
+
 ### Flask Not Found
 ```bash
-pip3 install flask
+pip3 install flask flask-socketio
 ```
 
 ### Database Not Found
@@ -158,7 +222,7 @@ pip3 install flask
 
 ### Port Already in Use
 - Change the port in `config.ini` or stop the conflicting service
-- Use `lsof -i :5000` to find what's using the port
+- Use `ss -tlnp | grep 8080` or `lsof -i :8080` (if available) to find what's using the port
 
 ### Permission Denied
 ```bash

install-service.sh

@@ -405,6 +405,18 @@ copy_files_smart "$SCRIPT_DIR" "$INSTALL_DIR" || {
     exit 1
 }
 
+# Write .version_info at install dir so web viewer and packet_capture show version after install
+if command -v git &>/dev/null && [ -d "$SCRIPT_DIR/.git" ]; then
+    GIT_HASH="$(git -C "$SCRIPT_DIR" rev-parse --short HEAD 2>/dev/null || echo "unknown")"
+    if VERSION="$(git -C "$SCRIPT_DIR" describe --exact-match HEAD 2>/dev/null)"; then
+        INSTALLER_VER="$VERSION"
+    else
+        INSTALLER_VER="dev-${GIT_HASH}"
+    fi
+    printf '%s\n' "{\"installer_version\": \"${INSTALLER_VER}\", \"git_hash\": \"${GIT_HASH}\"}" > "$INSTALL_DIR/.version_info"
+    print_success "Wrote version info (${INSTALLER_VER}) to $INSTALL_DIR/.version_info"
+fi
+
 # If no config.ini in install dir, create it from config.ini.example
 if [ ! -f "$INSTALL_DIR/config.ini" ]; then
     if [ -f "$INSTALL_DIR/config.ini.example" ]; then

modules/commands/repeater_command.py

@@ -280,11 +280,7 @@ async def _handle_purge(self, args: List[str]) -> str:
                 # Force a complete refresh of contacts from device after purging
                 self.logger.info("Forcing contact list refresh from device to ensure persistence...")
                 try:
-                    from meshcore_cli.meshcore_cli import next_cmd
-                    await asyncio.wait_for(
-                        next_cmd(self.bot.meshcore, ["contacts"]),
-                        timeout=30.0
-                    )
+                    await self.bot.meshcore.commands.get_contacts()
                     self.logger.info("Contact list refreshed from device")
                 except Exception as e:
                     self.logger.warning(f"Failed to refresh contact list: {e}")
@@ -314,21 +310,16 @@ async def _handle_purge(self, args: List[str]) -> str:
                 # Final verification: Check if contacts were actually removed from device
                 self.logger.info("Performing final verification of contact removal...")
                 try:
-                    from meshcore_cli.meshcore_cli import next_cmd
-                    await asyncio.wait_for(
-                        next_cmd(self.bot.meshcore, ["contacts"]),
-                        timeout=30.0
-                    )
-                    
+                    await self.bot.meshcore.commands.get_contacts()
+
                     # Count remaining repeaters on device
-                    remaining_repeaters = 0
-                    if hasattr(self.bot.meshcore, 'contacts'):
-                        for contact_key, contact_data in self.bot.meshcore.contacts.items():
-                            if self.bot.repeater_manager._is_repeater_device(contact_data):
-                                remaining_repeaters += 1
-                    
+                    remaining_repeaters = sum(
+                        1 for contact_data in self.bot.meshcore.contacts.values()
+                        if self.bot.repeater_manager._is_repeater_device(contact_data)
+                    )
+
                     self.logger.info(f"Final verification: {remaining_repeaters} repeaters still on device")
-                    
+
                 except Exception as e:
                     self.logger.warning(f"Final verification failed: {e}")
 

modules/core.py

@@ -43,6 +43,22 @@
 from .utils import resolve_path
 
 
+class _DuplicateAwareConfigParser(configparser.ConfigParser):
+    """ConfigParser that allows duplicate options (last value wins) and logs ERROR when seen."""
+
+    def __init__(self, *args, **kwargs):
+        kwargs['strict'] = False
+        super().__init__(*args, **kwargs)
+
+    def _handle_option(self, st, line, fpname):
+        if st.optname in st.options:
+            logging.getLogger(__name__).error(
+                "Duplicate option in config file: section [%s], option '%s' (file %s, line %s). Using last value.",
+                st.sectname, st.optname, fpname, getattr(st, 'lineno', '?'),
+            )
+        st.options[st.optname] = st.optvalue
+
+
 class MeshCoreBot:
     """MeshCore Bot using official meshcore package.
     
@@ -52,7 +68,7 @@ class MeshCoreBot:
 
     def __init__(self, config_file: str = "config.ini"):
         self.config_file = config_file
-        self.config = configparser.ConfigParser()
+        self.config = _DuplicateAwareConfigParser()
         self.load_config()
 
         # Setup logging