How to Build an OpenClaw Ham Radio Digital Modes Agent on Raspberry Pi

Most Raspberry Pi ham radio setups stop at installation. You get WSJT-X decoding FT8 signals and Direwolf handling APRS packets, but the station still needs a human watching the screen, picking which calls to answer, and deciding when band conditions favor one frequency over another.

An OpenClaw agent adds a decision layer on top of these tools. Instead of passively decoding, the agent reads decoded FT8 output, decides whether a station is worth calling based on distance, grid square rarity, or band opening patterns, and can trigger a transmission at the right moment. For APRS, the agent manages beacon timing, adjusts position reports based on movement speed, and routes incoming messages to your phone or a shared workspace.

The key insight is that both WSJT-X (via its jt9 decoder) and Direwolf run as command-line processes with text-based input and output. OpenClaw's Python scripting capabilities can wrap these tools, parse their output streams, and make decisions about what to do next. FT8 accounts for over 80% of HF digital contacts worldwide, making it the single highest-value mode to automate.

This is not about replacing the operator. It is about keeping the station productive during the hours you are not sitting at the desk, catching DX openings that would otherwise pass unnoticed, and maintaining APRS infrastructure without manual intervention.

The hardware splits into three categories: the Pi itself, the radio interface, and the radio.

Raspberry Pi:

• Raspberry Pi 5 (8 GB RAM) recommended for running OpenClaw plus decoding software simultaneously
• Raspberry Pi 4 (4 GB) works but may struggle under heavy decode load during contest weekends
• High-endurance microSD card (32 GB minimum) or USB SSD for reliability in always-on operation
• Adequate power supply: 5V/5A for Pi 5, 5V/3A for Pi 4

Radio interface options:

• DigiPi HAT: purpose-built for ham radio digital modes on the Pi, supports FT8, FT4, APRS, and Winlink. Includes a DB-9 connector for rig cables, onboard TFT LCD, and optional environmental sensors for APRS weather beacons
• SignaLink USB: external sound card interface with adjustable audio levels, works with nearly any radio
• Digirig Mobile: compact USB audio and CAT control interface, popular for portable operation

Radio:

Any HF transceiver with a data or accessory port works for FT8. For APRS on VHF, a handheld or mobile radio with a 3.5mm audio jack is sufficient. The interface handles audio in and out between the Pi and the radio, while CAT control (if supported) lets the agent change frequencies without manual tuning.

Optional additions:

• GPS module (for precise timing and APRS coordinates)
• RTL-SDR dongle (for receive-only band monitoring without tying up the main radio)

Total cost excluding the radio ranges from $75 (Pi 4 + SignaLink) to $200 (Pi 5 + DigiPi HAT + GPS + SSD).

The software stack has three layers: the radio applications, OpenClaw as the agent runtime, and supporting services for timing and logging.

Install WSJT-X for FT8/FT4 decoding:

WSJT-X is the standard application for weak-signal digital modes. On Raspberry Pi OS, install it from the official .deb package. The critical component for automation is jt9, the command-line decoder bundled with WSJT-X. It accepts WAV audio input and outputs decoded messages as text, which is exactly what an agent needs.

For fully headless FT8 operation, ft8modem is a lightweight alternative that wraps jt9 into a text-based pipeline. Received decodes come out as lines prefixed with "D:" and transmitted frames go in as lines prefixed with "E:", making the entire FT8 workflow scriptable from a shell or Python process. Companion tools ft8cat (CAT radio control), ft8qso (QSO sequencing), and ft8report (PSKreporter upload) extend the automation further.

Install Direwolf for APRS:

Direwolf is a software TNC (terminal node controller) that handles AX.25 packet encoding and decoding. It runs as a daemon and can operate as an APRS tracker, digipeater, or internet gateway (iGate) simultaneously. Build from source on the Pi for the latest version with all features enabled.

Direwolf's configuration file (direwolf.conf) controls audio device selection, callsign, SSID, beacon text, digipeater paths, and iGate connection to APRS-IS servers. Once configured, it runs unattended and outputs decoded packets to stdout or a log file.

Install OpenClaw:

OpenClaw runs on Raspberry Pi 5 (8 GB recommended) or Pi 4 (4 GB minimum). It provides the agent runtime, skill system, and cron scheduler that ties the radio software together. The agent can execute Python scripts, parse command output, and make decisions using LLM reasoning about what the radio tools report.

Timing services:

FT8 requires clock accuracy within one second (0.5 seconds recommended for reliable decoding). Install chrony with a GPS reference or use NTP with multiple servers. A drifting Pi clock breaks FT8 synchronization entirely.

Systemd services:

Configure Direwolf and the ft8modem (or WSJT-X in headless mode) as systemd services so they start automatically on boot and restart on failure. The OpenClaw agent then connects to their output streams rather than managing their lifecycle directly.

Store your station logs and propagation data in one place

Fast.io gives ham radio agents 50 GB of free workspace storage with built-in search and sharing. Upload QSO logs, band condition reports, and APRS captures through the MCP server, no credit card required.

Sign Up Free

The FT8 agent monitors decoded signals and makes decisions about which stations to call, when to transmit, and how to log completed contacts.

Parsing decoded output:

The jt9 decoder (or ft8modem) outputs lines like:

D: 2116 -14  0.3 1423 ~ CQ DX JA1ABC PM95

Each line contains the UTC time, signal-to-noise ratio, time offset, frequency, and the message content. The agent parses these fields and evaluates each decode against its rules.

Decision logic the agent can implement:

• Filter CQ calls by prefix, grid square, or continent to target specific DX
• Track signal strength over multiple decoding periods to identify band openings
• Avoid calling stations already in QSO (the message field shows who is talking to whom)
• Respect FCC Part 97 rules: the agent should only transmit when an operator is present unless operating under specific unattended provisions
• Log all decodes to a database for later band condition analysis

Band condition awareness:

The agent can maintain a rolling window of decoded stations, tracking which bands are open to which regions. When 20 meters goes long to Japan at sunset, the agent notices the cluster of JA prefixes appearing and can alert you or, if configured for semi-automated operation, begin calling CQ on that band.

An RTL-SDR dongle adds receive-only monitoring on additional bands without tying up the transmitter. The agent watches multiple bands simultaneously and recommends (or switches to) whichever band shows the best propagation for your target region.

QSO logging:

Completed contacts get logged in ADIF format (the standard ham radio log format). The agent writes these locally and can push them to cloud storage for backup, sharing with contest logging services, or long-term propagation analysis.

APRS automation is simpler than FT8 in some ways because it is primarily a one-way broadcast system for position and telemetry, but the agent adds value through intelligent beacon management and message routing.

Intelligent beaconing:

Standard APRS trackers beacon at fixed intervals regardless of whether the station is moving. The SmartBeaconing algorithm adjusts rate based on speed and heading changes, but it is still reactive. An OpenClaw agent can implement more sophisticated logic: beacon more frequently when approaching an event location, reduce beaconing when stationary for extended periods, or increase rate during severe weather to maintain network visibility.

Weather station integration:

The DigiPi HAT includes optional temperature and humidity sensors. Combined with a barometric pressure sensor, the agent can format and transmit complete APRS weather reports on schedule. Direwolf handles the packet encoding, but the agent decides when conditions have changed enough to warrant an update and formats the telemetry data.

iGate and digipeater management:

Running Direwolf as an iGate forwards local RF APRS packets to the internet (APRS-IS). As a digipeater, it retransmits packets to extend network coverage. The agent monitors packet flow, tracks which stations are being heard, and can generate daily or weekly reports on local APRS network health.

Message routing:

APRS supports two-way messaging. When someone sends an APRS message to your station, the agent can forward it to a messaging service, store it in a shared workspace for later review, or auto-reply with a status message. This turns a basic Pi-based iGate into a communication hub that stays responsive even when you are away from the shack.

Logging and storage:

All received and transmitted packets get timestamped and stored. For stations running as infrastructure (iGates, digipeaters), this log becomes valuable for troubleshooting network issues and proving coverage claims to local emergency communications groups.

A ham radio agent generates substantial data: decoded FT8 contacts, APRS packet logs, band condition reports, and propagation analysis summaries. Local microSD storage works for the raw capture, but sharing and long-term archiving benefit from cloud workspace storage.

What to store:

• ADIF log files from completed FT8/FT4 QSOs
• Band condition reports (which bands were open, to where, at what times)
• APRS packet captures for network analysis
• Agent decision logs showing why certain calls were answered or skipped

Why cloud storage matters for ham radio agents:

Running an always-on station means data accumulates continuously. A Pi's microSD card is a single point of failure, and a corrupted card means lost contest logs or APRS records. Cloud backup protects against hardware failure while making logs accessible from any device.

Fast.io provides workspace storage for agents with a free tier that includes 50 GB of storage, 5,000 monthly API credits, and 5 workspaces, enough to run a ham radio logging agent indefinitely without cost. The MCP server gives agents programmatic access to upload files, organize them into workspaces, and share specific logs with other operators or club members.

Practical workflow:

The agent writes QSO logs locally in real time. On a scheduled interval (daily or after each operating session), it uploads the latest ADIF file to a Fast.io workspace. Band condition summaries get generated as markdown reports and stored alongside the logs. If you are part of a radio club, you can share a workspace with other members so everyone can see which bands are producing contacts from your area.

Intelligence Mode indexes uploaded documents automatically, so you can later ask questions like "which weekends had the best 20-meter openings to Europe" and get answers drawn from months of accumulated log data without writing custom queries.

For contest operations, the agent can push log updates every few hours so a remote coach or team captain can monitor progress through the Fast.io web interface without needing direct access to the station computer.

A ham radio agent is most useful when it runs continuously, catching band openings at odd hours and maintaining APRS infrastructure around the clock.

OpenClaw cron scheduling:

OpenClaw's built-in scheduler supports three timing modes: one-shot (at), interval (every), and standard cron expressions. For ham radio, common schedules include:

• Every 15 seconds: check for new FT8 decodes and evaluate calling decisions
• Every 5 minutes: update APRS beacon with current telemetry
• Every hour: generate a band condition summary from accumulated decodes
• Daily at sunrise and sunset: increase monitoring intensity during gray-line propagation windows
• Weekly: compile a propagation report and upload to cloud storage

Reliability for unattended operation:

The Pi needs to handle power outages, network drops, and software crashes gracefully. Use a UPS or battery backup for the Pi (a small USB power bank works for short outages). Configure systemd services with automatic restart. The OpenClaw gateway persists job definitions to disk, so scheduled tasks survive reboots.

GPS timing ensures FT8 stays synchronized even if the network drops. Without GPS, chrony with multiple NTP sources provides redundancy, but extended network outages will eventually drift the clock out of FT8 tolerance.

Monitoring the agent:

The agent itself needs monitoring. Set up a health check that verifies Direwolf is receiving packets, the FT8 decoder is producing output, and the Pi's temperature stays within safe limits. If something fails, the agent can send an alert through APRS messaging (if the radio path is still working) or through an internet notification channel.

Legal considerations:

Automated transmission in amateur radio has specific regulatory requirements that vary by country. In the US, FCC Part 97 allows auxiliary station operation and certain automated modes, but the control operator must be able to shut down the station promptly. Your agent should have a kill switch: a way to immediately halt all transmissions via a remote command, APRS message, or web interface. Log all transmissions with timestamps and your callsign for compliance records.