v2025.24.0#
Previous version: v2025.23.0
Features#
New Alert rules for monitoring device connectivity
A new alerting system has been introduced to help users detect and respond to device connectivity issues. The alert rules feature, available in the Monitoring & Reporting → Alert rules panel, allows users to define when a device is considered connected or disconnected based on the types of uplinks. The system scans device pools at configurable intervals, and rules can apply to a domain or include its subdomains, supporting multi-tenant environments.
Once an alert rule is created, it can be used as a trigger in the Data Integration Center to define a Kafka event handler. This enables users to forward alerts to external systems, using configurable payload formats and delivery options such as Kafka topics and custom headers.
For more information, see the Create alert rule guide in User Documentation.
New resource management panel
Introduced a refreshed version of interface for managing internal and external resources, accessible under Administration > Resources. The view includes updated layout and allows users to add, edit, delete, and download resources with improved control and visibility.
Serial number column added to Device Inventory
A new default column showing the serial number is now available in the Device Inventory table. It supports search functionality and helps users quickly identify and filter devices using this key hardware identifier.
Enhancements#
Improved Firmware version read flow
The firmware version check after update is now an optional step used only for UI refresh. This improves reliability by ensuring the overall FOTA result reflects the true update status, even if the version read step fails.
Bug Fixes#
Fixed error when device log level was set to OFF
Resolved an issue that caused an error when entering the device Advanced setting logs view with logging disabled. The view now loads correctly and allows log level to be updated if needed.
Fixed domain selector in user creation view
Corrected a problem where the wrong default domain appeared in the user creation form. The domain selector now properly reflects the selected domain context and validates as expected.