Skip to content

V3.1.0

Release Notes – Version 3.1.0

Pre-Release Version

This version is currently in development and not yet available for public release.

New Features

  • Radio User Assignment (RUA) Added comprehensive RUA functionality for managing radio user assignments. For detailed configuration and usage instructions, see the RUA Module Documentation.

  • Radio Message Player (RMP) Introduced RMP capabilities for playback and management of radio messages. Refer to the RMP Module Documentation for complete feature details.

  • Heatmap Visualization Added heatmap visualization to display spatial data density and patterns on the map. See the Heatmap Module Documentation for configuration options. Note: This feature is not available when using the Terminal Gateway.

  • Radio Signal Information Display Enhanced tracked object monitoring with uplink RSSI (Received Signal Strength Indicator) and uplink node information, enabling real-time signal quality tracking and radio connectivity status. Note: This feature is not available when using the Terminal Gateway.

  • TrackedObject Properties System Tracked objects now support custom properties that can be configured through the edit dialog or modified dynamically via rule engine actions.

  • Automatic TrackedObject Name Synchronization Added configuration option to automatically synchronize tracked object names with subscriber descriptions from the TETRA system. When enabled, tracked object names update automatically whenever the corresponding subscriber description changes.

  • Rule Engine Geofence Condition Extended the rule engine with a new condition type to check whether a specific tracked object is located within a defined geofence. For more information on rule configuration, see the Configuration Documentation.

  • Service Management Controls Enhanced the Manager interface with dedicated controls to start and stop all services simultaneously. Services that are disabled via their configuration settings are displayed in a disabled state and excluded from bulk operations.

Improvements

  • EventLog Filtering: Extended filter options to include Action_Log, Rule_Log, and Custom_Event categories for more granular event monitoring.
  • Rule Grouping: Rules can now be organized using the "Label" field, with collapsible groups for improved rule management in complex configurations.
  • Rule Activation Control: Rules can be disabled to temporarily prevent execution without deletion.
  • TrackedObject Creation: Subscriber descriptions from the TETRA system are now pre-populated as the default name when creating new tracked objects.
  • TETRA Gateway Management: Added manual reconnect button and explicit primary gateway selection to improve connection reliability.
  • EventLog Filtering Enhancement: Improved clarity and specificity of source and tracked object filters to reduce ambiguity.
  • Location History Visualization: Added signal strength-based color coding option for data points, complementing the existing age-based coloring.
  • Terminal Gateway Performance: Optimized performance under high-load conditions for improved throughput and stability.
  • Enhanced Logging: TETRA status codes are now logged with human-readable text descriptions, and inter-process communication logging has been enhanced for better diagnostics and troubleshooting.
  • Navigation Enhancement: Active page is now highlighted in the navigation bar for improved user orientation.

Bug Fixes

  • Resolved an issue where users could not be edited due to an invisible form requirement.
  • Fixed missing severity icons in the EventLog display.
  • Corrected application freeze occurring when loading the subscriber register.
  • Resolved snackbar visibility issues to ensure notifications are always displayed correctly.
  • Fixed service dependency issues that prevented the Web-Service from starting when other services were unavailable.
  • Corrected TETRA gateway behavior to properly activate the primary gateway when the primary gateway configuration is changed.
  • Resolved autocomplete functionality issues in certain rule engine condition fields.

Breaking Changes

Database Schema Update Required

This version includes database schema changes. Migration procedure:

  1. Start the Web-Service individually
  2. Wait for the schema migration to complete (approximately 10-30 seconds)
  3. Start the remaining services

For detailed upgrade instructions, see the Installation Guide.

Additional Resources