Thinline-Dynamic-Solutions/ThinLineRadio v26.10.25

ThinLine Radio v26.10.25

on GitHub

Version 26.10.25 - Released October 25, 2026

Added

• Shared call classifications
  • Admin → Call Natures can Update from ThinLine to download the shared category list. Categories you added on this server, such as local 10-codes, are kept, and map expire times are not changed. Clear local classifications removes the whole list.
• Correct Pin address search
  • Type an address and choose Find. One match moves the pin. Several matches are shown as A, B, C, D dots on the map and as a list. Pick one, then save.

Changed

• Alerts
  • Dispatch cards are grouped by channel, with the call label, transcript, and a map when the call is pinned. The map and label fill in on the open card when mapping finishes.
  • All lists every radio-transmission alert the account can hear. Mine stays limited to alert preferences. System stays health alerts only.
  • The recent-alerts rail shows on the Transmissions tab only.
• Stats
  • Ranges are today, 24 hours, 7 days, and 30 days. The board shows call volume, incidents, tone-outs, channels, and call natures.

Fixed

• Alert sounds
  • Saving Alerts → Preferences no longer clears custom notification sounds or pager playback.
• Unspecified alarms
  • When the radio does not say fire or burglary, the channel tag decides. A commercial alarm on a fire channel is a fire alarm.

Version 26.10.20 - Released October 20, 2026

This version was committed earlier and is included here. It did not have its own GitHub release.

Added

• Remote settings management (Central Management)

  • GET /api/admin/options returns the current options plus the server version. Credentials (API keys, passwords, secrets, tokens) are never returned; they appear as {"set": true|false}.
  • PATCH /api/admin/options?compact=1 applies a partial update exactly as before but responds with only {ok, version, options} instead of the entire config (no users or systems in the response).
  • Central Management uses these with its existing admin-token handshake to view and edit settings on one server or push them to many servers at once. Behavior for local admins is unchanged.

• Config backup to Central Management

  • A server paired with Central Management now sends its full configuration (the same document config sync writes and the admin export contains) to Central Management after every configuration change, so CM can keep versioned snapshots and restore one.
  • Changes are coalesced: the push waits 30 seconds after the last change (never more than 5 minutes after the first) and is skipped when nothing differs from the last copy CM accepted. A baseline copy is also sent about 2 minutes after startup. The push is gzip-compressed and independent of the file-based Config sync setting.
  • Failures retry with backoff (1 to 15 minutes) and log at most every 15 minutes. A Central Management that does not support backups yet is rechecked hourly.
  • The export includes password hashes and credentials, exactly like config sync, so the Central Management database should be treated as sensitive.

• Per-instance time zone

  • New Time Zone option (Admin > Config > Options > General, IANA name such as America/Chicago). Call times in the web app (console, search, alerts, incident map), the time in tone/pre-alert push notifications, and the prune time use it. Empty keeps the old behavior (browser time zone in the web app, server time zone elsewhere).
  • Zone names are validated in the admin, over the options API and on import; an unknown name is rejected. The zone database is embedded in the binary, so it works on minimal hosts and containers.

• Prune at a set time of day

  • New Prune Time option (24-hour HH:MM, in the instance time zone). When set, the database prune runs once a day at that time instead of at startup and every hour. Instances that share a host can be given different times so they do not all prune together.
  • A restart does not trigger a catch-up prune outside the slot. Two prunes never overlap. Leave the option empty to keep the previous behavior.
  • Both options can be pushed from Central Management with no restart.