Skip to content

Configuration

MeshSat is configured via environment variables. See the Environment Variables reference for the complete list.

Core Settings

VariableDefaultDescription
MESHSAT_MODEcubeosSet to direct for standalone USB access
MESHSAT_PORT6050HTTP port for dashboard and API
MESHSAT_DB_PATH/cubeos/data/meshsat.dbSQLite database path
MESHSAT_RETENTION_DAYS30Days to keep historical data

Serial Ports

All default to auto — USB VID:PID tables and protocol probing detect devices automatically.

VariableDescription
MESHSAT_MESHTASTIC_PORTMeshtastic radio
MESHSAT_IRIDIUM_PORTIridium 9603N (SBD)
MESHSAT_IMT_PORTRockBLOCK 9704 (IMT/JSPR)
MESHSAT_CELLULAR_PORTCellular modem
MESHSAT_ZIGBEE_PORTZigBee coordinator

Deployment modes

MESHSAT_MODE picks how the bridge reaches serial hardware.

StandaloneCubeOS
Set byMESHSAT_MODE=directMESHSAT_MODE=cubeos (default)
Serial accessDirect to /dev/ttyACM0, /dev/ttyUSB0Through the HAL REST API
Deploy withdocker-compose.standalone.ymlCubeOS orchestrator
Who it is forAny Linux machineCubeOS installations

Standalone is what a self-hosted install uses, and what the quick start sets up. It needs the container to reach USB devices, which is why the compose file is privileged and mounts /dev.

Everything else

The tables above are the settings most people touch. The Environment Variables reference lists all of them, grouped by subsystem, including the satellite GPIO pins, the SMS bundle counter, out of band management, the Hub uplink fallback and the compression sidecars.

Made by MeshSat