PIGWay Device Agent is a lightweight local monitoring service for Raspberry Pi and Linux. It monitors CPU, memory, temperature, disk, networking, services, processes, system health alerts, and journal events. It has no embedded Web UI and does not require a hardware plugin or Device Console.

Installation

sudo ./install.sh
# Explicitly enable the API:
sudo ./install.sh --enable-api
# Keep the API disabled:
sudo ./install.sh --disable-api

Interactive installation asks whether to enable the remote API and defaults to no. Non-interactive installation also keeps it disabled unless explicitly enabled. --no-start only updates files and configuration; it does not change the current service state.

The configuration file is /etc/pigway-pi-control.conf. Restart the Agent after changing monitoring settings:

sudo systemctl restart pigway-pi-control.service

Optional API

The default is [api] enabled = false, with no network listener. To use centralized management, enable it and configure the bind address and port, then run:

sudo systemctl enable --now pigway-pi-control-api.service
sudo cat /etc/pigway-pi-control-api.token

The default port is 6001. Every read and write request requires Authorization: Bearer <token>. The token belongs only to this device and is not printed directly by the installer. The API exposes health, status, logs, configuration, services, plugins, and plugin configuration under /api/v1. It does not serve a Web UI, register multiple machines, or proxy remote requests.

Console and hardware plugins

PIGWay Device Console can run on a NAS or remote server for dashboards, configuration, and batch synchronization.
PIGWay Yahboom Cooling HAT independently provides local telemetry, OLED, fan control, and RGB effects.

The remote API and local plugin integration are independent. After enabling plugin integration, register yahboom-cooling-hat = /run/pigway-plugins/yahboom-cooling-hat/api.sock under [plugins] and restart the Agent, or attach it through the Console. Discovery never binds a plugin automatically. Pausing or disconnecting integration does not stop the plugin's local functions.

Operations

sudo /usr/local/sbin/pigway-pi-control --diagnose
sudo journalctl -u pigway-pi-control.service -f

Logs follow the system journal retention policy; no additional database is created. Uninstalling one project never uninstalls either of the others. See Plugin API v1.