Release 10.13.0.432
Fixes
| Component | Description | Issue |
|---|---|---|
| Connectivity | Due to a compatibility error of the connectivity microservice with the Kite provider, an error occurred on the metrics page, when the monthly consumption data was an out-of-scope integer. This has been fixed by changing the data type. | DM-1566 |
Release 10.13.0.405
Fixes
| Component | Description | Issue |
|---|---|---|
| Loriot | Events created by the Loriot agent when sending uplink requests are now considered device requests and provide connectivity status and availability monitoring. | DM-2139 |
Release 10.13.0.402
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.13.0.390
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.13.0.389
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.13.0.384
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | Fixed an issue in the Tracking tab where the position marker on the map did not render. | MTM-50978 |
| Device Management | The Assign devices button is now disabled for users without the required permissions. | MTM-50928 |
Release 10.13.0.376
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | By adding or removing an external identifier of type c8y_Serial to/from the monitored device, the device connection monitoring is notified accordingly to start or stop with the specified external identifier. |
MTM-50025 |
| MQTT | The MQTT storage is now properly cleared by removing not needed data after device disconnection. This may result in performance improvements, especially in terms of MQTT connect and subscribe operations. | MTM-49888 |
Release 10.13.0.370
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.13.0.361
Fixes
| Component | Description | Issue |
|---|---|---|
| LWM2M | By default, the LWM2M object-resource mappings of the Management tenant that are configured using the LWM2M device protocols were not inherited by the subtenants. With this change, the LWM2M object-resource mappings defined in the Management tenant are applied to all its subtenants by default. The default mappings from the Management tenant can also be overwritten by uploading the LWM2M device protocol for the LWM2M object on the subtenant level as described in LWM2M > LWM2M device protocols in the Protocol integration guide. | DM-1778 |
| LWM2M | While updating the security info for PSK devices in the database, the LWM2M agent internally deleted the old security managed object and created a new one. Due to the asynchronous deletion of managed objects in the Cumulocity IoT platform, the agent intermittently failed to update the security info. With the current changes, the LWM2M agent updates the required security details in the same managed object instead of removing it first. | DM-1671 |
| LWM2M | The LWM2M agent now allows users to write binary data to a resource on a device using a shell operation. For more details about the shell command, refer to LWM2M > Handling LWM2M shell commands in the Protocol integration guide. | DM-1241 |
Release 10.13.0.354
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | In the Software repository page, the Add software dialog accepted a software without software type although the field Software type is mandatory. This has been fixed and the Add software button is now active only when the mandatory Software type field is filled. | DM-1713 |
Release 10.13.0.349
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | In the Software repository page, sorting for the column "Device type" did not function properly. This issue is now fixed. | DM-1712 |
Release 10.13.0.342
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | Fixed an issue where users could not find a location on the map based on the address they entered. | MTM-49644 |
| Device Management | In case of many active alarms of different severities, in the "Active critical alarms" widget users might have needed to press the Load more button several times on an empty list in order to see their active critical alarms. This is now fixed - the widget always initially shows active critical alarms if available and the Load more button does not load empty pages. | DM-1646 |
| Device Management | On the Location tab in the device details, you can now again change the location of the device on the map by dragging the position marker. | DM-1565 |
| Device Management | The Submit button in the "Device data" widgets editor is now always enabled. The validation on fields is still present, but validation errors no longer prevent users from committing manual changes. | DM-1623 |
| LWM2M |
- The LWM2M agent always retrieved the external decoder events from one month back only. So if an event remained unprocessed over a month, then it wasn't processed anymore. The time period is now configurable from the agent's configuration.
- Events, measurements, and alarms created by the LWM2M agent are flushed every 10 mins. If a high number of devices connects concurrently or in a short time period, the size of the queue can increase significantly, which in turn leads to high memory usage until all elements are flushed. The flush time interval can now be configured from the agent's properties. |
DM-1602 |
| LWM2M | If thousands of decoder events were pending to be processed, the LWM2M agent tried to process the same event twice in certain cases. As a result, the log file showed confusing SDK exceptions. This has now been fixed. | DM-1621 |
| LWM2M | The external decoder service was using a single thread per event to parallelize the decoder event processing. Those threads were created from another execution thread which can lead to a deadlock on a tenant. To avoid such deadlocks, the processing of the decoder events is done in batches for each tenant. Additionally, a fail-safe mechanism has been introduced, so that the agent is able to release a tenant after a certain period of a deadlock. | DM-1519 |
| LWM2M | The LWM2M agent now fetches a limited number of pending operations if a LWM2M device sends a registration or a registration update. This prevents the LWM2M agent to do a high number of requests to the platform if devices have accumulated lots of pending operations. The limit is defined with a property in the LWM2M agent. | DM-1474 |
Release 10.13.0.321
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.13.0.309
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.13.0.299
Fixes
| Component | Description | Issue |
|---|---|---|
| Cloud Remote Access | Fixed an issue that prevented copying the Cloud Remote Access credentials when the Management tenant was not subscribed to the microservice. | MTM-46818 |
Release 10.13.0.292
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | In the Device Management application, for example in the Info tab or the Location tab, the latitude position is now consistently displayed as first position value, followed by longitude. | MTM-41052 |
Release 10.13.0.281
Fixes
| Component | Description | Issue |
|---|---|---|
| LWM2M | The LWM2M agent now fetches a limited number of pending operations if a LWM2M device sends a registration or a registration update. | DM-1474 |
Release 10.13.0.260
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | The OPCUA device gateway creates an application identity certificate to identify itself with the OPCUA server. During the upgrade of the OPCUA gateway from version 10.11 or earlier to 10.13 and later, the private key of this application identity is encrypted internally and saved. The encryption of the old identity was faulty in the earlier releases of 10.13 and later, which led to issues with the server connection using Sign or SignAndEncrypt security mode after the upgrade. This issue is now resolved. Users who configured the OPCUA server after the upgrade, or did a new configuration with 10.13 or later versions are unaffected by the issue. The issue was only during the encryption of old identities. | DM-1246 |
Release 10.13.0.230
Fixes
| Component | Description | Issue |
|---|---|---|
| OPC UA | The nodes of the OPC UA server address space contain hierarchical references that are used by the opcua-device-gateway to traverse the address space tree during the address space scans. The partial address space scans used to require the inverse hierarchical direction for the start node and its parent nodes. Now partial scan also works when the start node or its parent nodes do not contain the inverse hierarchical references.
Moreover, for better troubleshooting during scans, debug/trace logs have been added to all opcua-device-gateway address space scanners. For details on how to enable them, see OPCUA > Troubleshooting in the Protocol integration guide. | DM-1008 |
Release 10.13.0.187
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.13.0.167
Fixes
| Component | Description | Issue |
|---|---|---|
| Cloud Remote Access | Fixed an issue that prevented copying the Cloud Remote Access credentials when the Management tenant was not subscribed to the microservice. | MTM-46115 |
| Device Management | The count for alarms shown on the Alarms tab in the device details did not include child devices. This is now fixed and the count of the different alarm types is calculated correctly. | DM-875 |
| LWM2M | Cumulocity IoT LWM2M now ignores invalid FOTA status reports when they're not expected to be sent by the device. Corresponding FOTA operations are not failed anymore. | MTM-45956 |
| DEPRECATED - Core product | The LWM2M agent now accepts the resources of type TIME for creating measurements if the resource's value can be converted to an integer value. | DM-913 |
Release 10.13.0.125
Improvements
| Component | Description | Issue |
|---|---|---|
| Actility | The Connectivity settings page has been enhanced to allow the user to configure the Actility ThingPark URL at the tenant level. This is an optional field. If the URL is not specified, then the default value from the agent properties is considered. | MTM-41853 |
| Actility | A LPWAN tab for actility devices has been added to the device details page to be able to change the device type after the device registration. | MTM-34439 |
| Bulk Operations | With the introduction of the new bulk operations functionality (see Device Management > Monitoring and controlling devices in the User guide) the Bulk operations tab in the groups view became obsolete and has been removed. | MTM-41264 |
| Cloud Remote Access | The vulnerable third party library bcprov-jdk15on-1.66.jar has been upgraded to the secure 1.69 version. | MTM-43148 |
| Device Management | Updated the layout for the Device network, Measurements and Modbus tabs for an improved user experience and consistent look & feel. | MTM-38920 |
| Device Management | When creating or editing a group, the Name field now correctly enforces the limit of 254 characters. This update does not change the existing behaviour as the limit existed but was not enforced, which meant users could use names exceeding the limit and then experience problems when trying to use the group. | MTM-42285 |
| Device Management | A new required field Software type has been introduced when creating a new software item in the software repository. The new field is a filterable dropdown list presenting the software types to select from. This additional field improves the software management capabilities, allowing software to be managed by type. | MTM-42177 |
| Device Management | In the device details view, the Software tab now offers better navigation through large lists. Users can easily locate a software item to be updated or removed by filtering the list by the software name. | MTM-42182 |
| Device Management | In the Software tab, the Installed software view displays a Filter by software type dropdown box allowing the software list to be filtered by the type of the software object. In the list, if a software object has a software type defined it is displayed as a label next to its name. | MTM-42183 |
| Device Management | In the Software repository overview, the list group layout has been replaced by a data grid. This allows for better navigation through large software lists, enables filtering by different properties, and adds sorting options. Additionally, a new column displaying the software type of a software object has been added. | MTM-42181 |
| Device Management | On searches in pages with software and firmware lists, the name, description and type now are highlighted when matching the searched string. | MTM-42700 |
| Device Management | On smaller screens, the configuration preview box used to hide the Save to repository and Download buttons on the Configuration tab of the device details view. The layout of the view has been adjusted so that the preview box does not extend too much on smaller screens. | MTM-42949 |
| Device Monitoring | A new log file related to devices availability monitoring has been created. The log file is by default disabled. The purpose of the log file is to trace communication between the device and the Cumulocity IoT platform. For details, see Log files in the Cumulocity IoT Core - Operations guide. | MTM-36556 |
| LWM2M | The supported LWM2M version has been added to the documentation, see LWM2M in the Protocol integration guide. | MTM-40609 |
| LWM2M | A description of the "execute" operation with optional parameters has been added to the documentation, see LWM2M > LWM2M device details in the Protocol integration guide. | MTM-40590 |
| MQTT | The processing of the MQTT "last will" message is now done asynchronously. This improves the performance of "device disconnected" events and the concurrency of handling new MQTT connections. | MTM-44058 |
Fixes
| Component | Description | Issue |
|---|---|---|
| Bulk operations | The bulk operation progress bar on the bulk operations overview tab used to round the percentage value to the nearest whole number. For bulk operations with at least hundred devices this led to the progress bar showing a completed bulk operation (100%) even though the single operations had not yet been completed on all devices (<0.5%). The percentage value in the progress bar is now rounded down to the nearest whole number ensuring that a bulk operation will only be shown as completed if all single operations have been completed. | MTM-41363 |
| Connectivity | The check if a mobile device is managed by the currently configured SIM provider is now only done on opening the Connectivity tab of a device. This puts eventual errors in a logical context and reduces the number of checks. | MTM-40958 |
| Connectivity | In the Administration application, the Connectivity menu entry had been displayed in the navigator even when there were no connectivity providers to be displayed resulting in navigating to an empty page. The Connectivity entry is now only displayed if there are accessible connectivity providers. | MTM-41798 |
| Connectivity | An issue with the Connectivity tab has been fixed, which prevented that users with read-only access to a given device could load the device details. | DM-627 |
| Device Management | An issue has been fixed with translations which caused some words in specific languages to be incorrectly presented with upper/lowercase. | MTM-40802 |
| Device Management | Fixed an issue in device registration, that caused devices to receive incorrect device credentials via MQTT if its ClientID (e.g. serial) - entered on creating a new device request - contained language-specific characters. | MTM-39667 |
| Device Management | In the Cockpit and Device Management application, Load more in the navigator menu is now disabled, while the assets load request is in progress, after clicking the button. Previously it was possible to click the Load more button multiple times before the browser had a response, and that resulted in getting duplicated groups in the list. | MTM-41681 |
| Device Management | When adding or editing a new configuration snapshot, the Configuration type field is now limited to 254 characters and the Use a URL field is limited to 2048 characters. | MTM-41906 |
| Device Management | Previously it was possible to select the wrong date range while filtering bulk operations. This issue has been fixed. | MTM-41622 |
| Device Management | An issue has been fixed where the "more" dropdown (for example on the Control or Firmware tab) was empty or non-clickable on switching views. | MTM-41222 |
| Device Management | Fixed and issue where searching by description was not working. | MTM-42617 |
| Device Management | An empty box was shown at the top of the Measurements tab in the device details view. This has been fixed. | MTM-43086 |
| Device Management | An issue has been fixed where the simulated device name was not displayed in its details tabs. | MTM-43052 |
| Device Management | An issue has been fixed which led to the same devices showing up repeatedly in the search result view. Now the results are correctly paged. | MTM-44398 |
| Device Management | A missing tooltip has been added with information on how to provide a file path when adding a new configuration object to the configuration repository. | MTM-44752 |
| Device Management | In the Logs tab of the device details, operations are now displayed sorted descending by creation date, displaying the newest operations on top. Scrolling down through the list allows to load and see older operations. | MTM-44461 |
| Device Management | For devices having the c8y_Firmware, c8y_Software/c8y_SoftwareList or c8y_Configuration fragments the device details tabs Firmware, Software or respectively Configuration are now displayed even if devices do not support the respective operations. In this case creating install/update operations is not possible via the UI. |
MTM-45139 |
| LWM2M | The attribute C8Y.lwm2m.enableBootstrapPSKFragmentFallback has been added to the agent's default configuration. If enabled, the LWM2M agent will find the bootstrap PSK ID from the fragments ("bootstrap psk_id") if it cannot be found from the external IDs. See Registration of PSK-secured devices in the Protocol integration guide for more information on the fields required for a bootstrap PSK connection. |
MTM-40632 |
| LWM2M | When a LWM2M device registration update comes with a different port or address than the previous registration, for example the LWM2M registration update comes with a new COAP port due to the load balancer's idle timeout being exceeded, all ongoing operations that are not finished meanwhile will be set back to PENDING state, instead of directly canceling them. | MTM-41981 |
| LWM2M | The resourceValue fragment added to events and alarms now works with opaque resources. Measurements cannot be created with opaque resource values. If enabled, it will create a warning alarm if non-numeric/non-Boolean values are received. Additionally, the type for no-mapping-known alarms has been improved by including the object ID. See also LWM2M device protocols in the Protocol integration guide. | MTM-41682 |
| LWM2M | The failure response of a LWM2M operation has been improved when failing on the device side. The message now states that it failed on the device side along with the error code and response returned from the client. | MTM-41999 |
| LWM2M | The LWM2M compatibility with certain Java 8 JRE versions has been improved. However, we recommend you to use Java 11 for executing LWM2M. | MTM-42596 |
| LWM2M | String resources can now again be mapped into measurement values, that is the LWM2M agent accepts numeric (integer and float) values sent as a string. In addition also the following strings will be treated as numeric values:
- Any positive or negative numeric sequence with leading 0 (zero) will be interpreted as octal value, but will be transformed and stored as a decimal number. - Any positive or negative alphanumeric sequence containing letters from A to F, starting with 0x will be interpreted as hex value, but will be transformed and stored as a decimal number. Strings which do not meet these requirements won't be processed and an error message will be logged. See also Overview in the Protocol integration guide. |
MTM-43661 |
| LWM2M | The LWM2M agent operation handler now handles a Californium library's connector error by setting the operation back to pending state to process the operation later on. This kind of error can happen when sending an operation to a device and there is no longer a DTLS connection with the URI that is used. | MTM-43663 |
| LWM2M | In the custom actions of the device protocol details, LWM2M now only returns decoder microservices which are subscribed to the current tenant. Prior to this change, decoder microservices not subscribed to the tenant were shown as well. | MTM-41435 |
| LWM2M | A subscribed LWM2M decoder microservice was still visible under LWM2M Resource > Custom actions after the microservice had been unsubscribed but not deleted. This issue is now resolved. When you unsubscribe the LWM2M decoder microservice, it is no longer accessible as a custom action until you subscribe to this service again. | DM-580 |
| MQTT | Fixed a race condition, where TCP packets were received in wrong order, resulting in the operation status reverting back to PENDING state on a delivery update. | MTM-39815 |
| OPC UA | The processing mode set in the OPC UA device protocol is now also applied to the mappings created due to historic read operations with tag type TAG. | MTM-40524 |
| OPC UA | To achieve higher security, the encryption method for the private key, which is used in the opcua-device-gateway to identify the application, has been changed. As a result, downgrading to previous versions of the opcua-device-gateway is not directly supported and manual steps must be taken. For details, see the downgrade instructions described in OPCUA > Gateway configuration and registration in the Protocol integration guide. | MTM-40343 |
| OPC UA | The creation of alarms is no longer prevented in case a HTTP post action is resulting in an error. | MTM-40496 |
| OPC UA | The management microservice now better handles malformed device type JSON and returns a proper HTTP error response (400 bad request). | MTM-41988 |
| OPC UA | When searching matches for all device types for a server address space, the opcua-device-gateway used to iterate if multiple device types existed that returned the same result. This situation is prevented now to run only once for the server. | MTM-43595 |
| SmartREST | In custom SmartREST 2.0 response templates that parse array parameters, only the first element was escaped when control characters were used. We now ensure that all returned array elements are escaped when necessary. | DM-679 |