|
| 1 | +# v2025.5.0 |
| 2 | + |
| 3 | +Previous version: [v2025.4.0](./v2025.4.0.md) |
| 4 | + |
| 5 | +## Features |
| 6 | + |
| 7 | +**Reference device selection in FOTA configuration** |
| 8 | + |
| 9 | +Added a step to select a reference device for multi-component FOTA configuration. Users can filter compatible devices, and the available components are displayed upon selection. |
| 10 | + |
| 11 | +**New FOTA campaign sidebar details** |
| 12 | + |
| 13 | +The FOTA campaign sidebar now displays additional details, including campaign type, target version, and the version before the update. Alerts highlight version mismatches, and a new navigation button provides quick access to detailed information. |
| 14 | + |
| 15 | +**FOTA approval preview with components** |
| 16 | + |
| 17 | +The FOTA approval window for multi-component FOTA now includes a detailed preview of multi-component configurations. This allows users to review all components before approving a campaign, ensuring greater control over the update process. |
| 18 | + |
| 19 | +## Enhancements |
| 20 | + |
| 21 | +**Improved error logging for Kafka messages** |
| 22 | + |
| 23 | +Increased the maximum message size limit for error logs from Kafka to provide complete error details. If an error message exceeds 200 characters, a "Show more" button is now available to display the full message. |
| 24 | + |
| 25 | +**Configurable automatic refresh in UpdateRequest** |
| 26 | + |
| 27 | +Added a new dialect flag allowing users to enable or disable automatic READ and DISCOVER operations when a device sends an UpdateRequest with new objects. By default, this behavior remains enabled, but it can now be turned off to reduce unnecessary load on resource-constrained devices. |
| 28 | + |
| 29 | +**Disabled irrelevant task parameters for *Discard report* option** |
| 30 | + |
| 31 | +When the *Discard report* option is enabled in task configuration, the fields that are not applicable are now disabled and set to predefined values. This improves clarity by ensuring only relevant settings are available. |
| 32 | + |
| 33 | +**Improved task domain handling** |
| 34 | + |
| 35 | +Enhanced task creation rules to ensure tasks created from templates inherit the selected user domain. Group task reports now remain in their original domain when a device moves providing better domain consistency and clearer data visibility. |
| 36 | + |
| 37 | +**Improved error handling for REST API `POST /users`** |
| 38 | + |
| 39 | +The API now returns a 403 error instead of 400 when a user lacks IAM permissions and a 409 error for duplicate usernames. Custom error messages have been added for password policy violations and invalid emails. |
| 40 | + |
| 41 | +**Improved FOTA session handling** |
| 42 | + |
| 43 | +Enhanced FOTA execution by ensuring observation resets properly, preventing timeouts during the resetting state machine step. If no notifications are received, the system now falls back to a read request to maintain progress. |
| 44 | + |
| 45 | +**Expanded permissions for *iottenantadmin* role** |
| 46 | + |
| 47 | +The *iottenantadmin* role now includes permissions to modify the device connectivity domain property and export devices to a CSV file, improving administrative capabilities. |
| 48 | + |
| 49 | +**Improved group management rules** |
| 50 | + |
| 51 | +Updated the group assignment process to display only valid groups based on domain hierarchy. This ensures a more structured and consistent approach to managing device groups. |
| 52 | + |
| 53 | + |
| 54 | +## Bug Fixes |
| 55 | + |
| 56 | +**Bootstrap security mode correction** |
| 57 | + |
| 58 | +Fixed an issue where the bootstrap security mode was randomly changing from CERT to PSK, causing re-bootstrap failures. The system now ensures that security mode changes are handled correctly, preventing unintended reconfigurations. |
| 59 | + |
| 60 | +**Fixed domain creation conflicts** |
| 61 | + |
| 62 | +Resolved an issue where automatically created user domains could conflict with existing domain groups. Now, when a new user logs in for the first time and their domain needs to be generated based on predefined settings, the system detects potential conflicts and prevents them, providing relevant guidance. |
| 63 | + |
0 commit comments