0488f6e25d
Add a CAT integration so the station's current frequency and mode are
reported to each operator's personal Wavelog logbook via Wavelog's radio
API (POST <baseUrl>/index.php/api/radio).
- New plugin rms.wavelog.cat (capability logging.cat.publish): posts
{key, radio, frequency, mode}. Base URL / radio name come from plugin
settings or env (WAVELOG_BASE_URL, WAVELOG_RADIO_NAME); no secrets in repo.
- Core hook in the OpenWebRX band-select flow pushes centerFreqHz + startMod
for the active operator, best-effort (never breaks the band change).
- Per-user Wavelog API key stored on the user record; PUT /v1/me/wavelog-key
to set it, returned by GET /v1/me and the OpenWebRX session issue response.
- UI: Wavelog API key field in the OpenWebRX panel (visible when generating
the session link), with i18n (de/en).
- Docs, .env.example entries, and a unit test for the mode mapping.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
RMS Software
RMS Software is a generic remote-station control platform with a web UI, passwordless authentication, plugin-based hardware integration, and OpenWebRX+ orchestration.
This repository is intentionally station-agnostic. Site-specific deployment, host bindings, and operational overrides belong in a separate deployment repository.
Core Features
- Passwordless auth via email link and OTP methods
- JWT access/refresh session model with role-based permissions
- Plugin runtime with capability provider switching
- OpenWebRX+ session/ticket integration and managed band/profile support
- Station lifecycle controls (activate/deactivate, ownership, safety locks)
- Rotor, RF route, TX/PTT and VSWR integration via plugins
- Activity/audit logs and SSE event stream for live UI updates
Quick Start
- Copy
.env.exampleto.env. - Install dependencies:
npm ci
- Start development mode:
npm run dev
- Open
http://localhost:8080.
Plugin Overview
Core and plugin docs:
- Core:
docs/core-overview.md - Plugin index:
docs/plugins/README.md
Auth
rms.auth.smtp_relay: email link challenge delivery through SMTP relayrms.auth.otp_email: OTP challenge delivery through emailrms.auth.oauth: OAuth/OIDC authorization-code login (disabled by default; configurable authorize/token/userinfo/client settings)
Google example (plugin settings):
authorizeUrl:https://accounts.google.com/o/oauth2/v2/authtokenUrl:https://oauth2.googleapis.com/tokenuserInfoUrl:https://openidconnect.googleapis.com/v1/userinfoscope:openid email profileemailField:emailclientId:<google-client-id>.apps.googleusercontent.comclientSecret:<google-client-secret>redirectUri:<public-base-url>/v1/auth/oauth/callback(or leave empty to auto-derive)
Station & Access
rms.station.shell: station activation/deactivation command executionrms.station.access.policy: export effective access list for OpenWebRX policies- Hardware guide:
docs/hardware-station-shell-guide.md
OpenWebRX+
rms.openwebrx.bandmap: managed band/profile integrationrms.openwebrx.guard: OpenWebRX safety and consistency guard
TX/PTT/Audio
rms.tx.control.native: native TX on/off command providerrms.tx.state.file: file-based TX state providerrms.tx.audio.core: core TX audio session managementrms.microham: microHAM provider for PTT/audio related capabilities- Hardware guides:
docs/hardware-tx-control-guide.md,docs/hardware-microham-guide.md
RF/Hardware
rms.rfroute.shell: RF route switching via shell commandsrms.rotor.hamlib: rotor control via hamlib/rotctl- Hardware guides:
docs/hardware-rfroute-guide.md,docs/rotor-rot1prog-guide.md,docs/rotor-alfaspid-rak-rot1prog-manual-notes.md - Manufacturer PDF copy:
docs/RAK_Rot1Prog.pdf
VSWR
rms.vswr.native: native VSWR command providerrms.vswr.nanovna: NanoVNA-based VSWR providerrms.vswr.report_reader: reads and serves VSWR report artifacts- Hardware guide:
docs/hardware-vswr-nanovna-guide.md
Ops/Help
rms.debug.remote: remote debug snapshot/log providerrms.help.basic: basic UI help content provider
Repository Boundaries
This repository contains:
- generic software source (
server,public,plugins) - generic defaults (
.env.example)
This repository does not contain:
- station-specific hostnames, hardware paths, or production secrets
- deployment overlays for specific stations
Recommended layering for deployments:
- RMS Software defaults
- Station-specific overlay repository
- Server environment variables (highest priority)
License
GPL-3.0-only. See LICENSE.
x