Release 10.14.0.422
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.14.0.413
Fixes
| Component | Description | Issue |
|---|---|---|
| Device management | On the Measurements tab of the device details, a tooltip has been added which shows the complete values in case of truncated values in the Y-axis. Moreover, the information is provided that you can see the complete values by hovering over the axis. | MTM-48603 |
| OPC UA | The application of OPC UA device protocols was unreliable when there were more than 1000 protocols. This is now fixed. | DM-2634 |
Release 10.14.0.402
Fixes
| Component | Description | Issue |
|---|---|---|
| OPC UA | In OPC UA device gateway nodes, expected but missing information prevented the completion of the address space scan operation. This is now fixed by skipping these nodes and adding an error message in the opcua-device-gateway log files. Additionally, the overall scanning speed has been improved for the full and partial address space scan operations. | DM-2365 |
Release 10.14.0.393
Fixes
| Component | Description | Issue |
|---|---|---|
| Connectivity | The performance of MQTT connections has been improved. MQTT devices can now connect or reconnect faster, especially if the platform already has a large number of MQTT devices connected. | MTM-53819 |
Release 10.14.0.383
Fixes
| Component | Description | Issue |
|---|---|---|
| Loriot | The memory limit for the Loriot microservice has been increased to 2Gi. | DM-2427 |
Release 10.14.0.372
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.14.0.370
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | In the SmartREST template editor, issues with the presentation of the External ID type field for inventory POST messages have been fixed. Under CSV preview, the generated "Template creation CSV" has been adjusted to include the "ID", "externalId" and "externalIdType" values. | DM-2093 |
| Device Management | In case of bad connectivity or network delay gateway devices could go to a state where they were disconnected. This resulted in operation execution being suspended. This issue is now resolved. | DM-2037 |
| Device Management | In the device grid, issues with applying filters have been fixed. | DM-2321 |
| OPC UA | If the namespace is not defined for a specific node, a missing error handler in the past prevented completion of the scan operation. This is now fixed by skipping nodes that cannot be read. The opcua-device-gateway logs include further details in such cases. The log level INFO contains the failure message and the log level DEBUG contains the stacktrace. | DM-1920 |
Release 10.14.0.348
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | SmartREST Inventory GET templates created in the UI did not generate responses when there was no external ID type declared in the template. This issue has been addressed for both existing and newly created templates. | DM-2126 |
| LWM2M | Multi-line LWM2M post-operations were not executed right after the LWM2M device's new registration when realtime was disabled for the tenant who owns the device. As a result the device might not receive these operations until the next LWM2M device's registration update. This issue is now resolved and LWM2M post-operations are executed right after the LWM2M device's new registration, no matter whether realtime is enabled or not for this kind of devices. | DM-2100 |
Release 10.14.0.338
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 |
| Device Management | In the advanced-software-mgmt microservice, creating or deleting a software package with special characters caused an error. This has been fixed by escaping them. | DM-2026 |
Release 10.14.0.330
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.14.0.324
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.14.0.315
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | On the Software tab in the device details, the Reload button now correctly updates the Installed software list. | DM-2005 |
Release 10.14.0.300
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.14.0.288
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | The Assign devices button is now disabled for users without the required permissions. | MTM-50928 |
Release 10.14.0.273
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | The "Groups" column in the device list used to display all groups higher in the hierarchy to which the device belonged directly or transitively. This has been fixed and now only the direct parent groups are displayed. | DM-1870 |
| 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 |
| Device Management | An issue with the filter functionality on the Groups page for smart groups has been fixed. Results now include devices belonging to the selected smart groups. | DM-1872 |
| 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.14.0.268
Improvements
| Component | Description | Issue |
|---|---|---|
| Device Management | The performance of the advanced-software-mgmt microservice has been improved. | DM-1251 |
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | The groups list on the Groups page now offers the option to filter by the grid's columns. | DM-1836 |
| 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.14.0.256
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | The option to copy the home page dashboard has been removed since it didn't provide useful functionality. | DM-1869 |
Release 10.14.0.250
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 |
| Device Management | In the Software repository page, sorting for the column "Device type" did not function properly. This issue is now fixed. | DM-1712 |
| 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.14.0.231
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 | 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 |
| OPCUA | Due to a change introduced in 10.14, the opcua-device-gateway, on OPC UA server connects or reconnects, did a full device type matching with a comparison of device types to the server's address space to find matched nodes and the application of these matched nodes. With this fix, the opcua-device-gateway directly applies the matched nodes settings if there was a matching done previously and no more recent updates to the device types were done. | DM-1651 |
Release 10.14.0.222
Fixes
| Component | Description | Issue |
|---|---|---|
| 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 | 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 theLoad more button does not load empty pages. | DM-1646 |
Release 10.14.0.213
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.14.0.204
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | The data type mapping for the "Asset properties" widget has been improved to ignore null values for properties created by default when using MQTT templates, which prevented users from saving widget data unless the mentioned properties were fixed manually. Affected properties: c8y_Firmware.url, c8y_Software.url, c8y_Mobile.imei, c8y_Mobile.imsi, c8y_Mobile.cellId, c8y_Mobile.lac, c8y_Mobile.mcc, c8y_Mobile.mnc. | MTM-48962 |
Release 10.14.0.182
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.14.0.172
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 |
| 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.14.0.153
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.14.0.143
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.14.0.141
Fixes
| Component | Description | Issue |
|---|---|---|
| OPC UA | 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 |
| OPC UA | Previously, when the autoReconnect property was enabled in the OPC UA server's client configuration, then on server connection drop, in addition to the Prosys client SDK auto-reconnect mechanism, the OPCUA device gateway did an additional reconnect. This led to issues with re-creating subscriptions to the server.
Now with autoReconnect enabled, only the Prosys client SDK does the auto-reconnect. If the autoReconnect property is disabled in the OPC UA server's client configuration, the OPCUA device gateway will do the reconnection itself by default. This OPC UA device gateway reconnect can also be disabled by setting the gateway configuration property triggerManualReconnectOnConnectionDrop to false. For details on the property, see OPCUA > Gateway configuration and registration in the Protocol integration guide. |
DM-1078 |
| 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 more details on how to enable them, see OPCUA > Troubleshooting in the Protocol integration guide. |
DM-1008 |
Release 10.14.0.117
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.14.0.68
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.14.0.45
Improvements
| Component | Description | Issue |
|---|---|---|
| Actility | The Application EUI parameter in the Actility agent has been moved from the provider settings tab in the Connectivity page to the Device registration page. | DM-246 |
| Device Management | On the Bulk operations overview page, the New bulk operation wizard displays a column with the software type of the listed software objects. Additionally, the Select software step offers a searchable dropdown to filter by software type. | MTM-42458 |
| Device Management | On 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 | The Service monitoring tab in the device details view and the Service monitoring overview page, which both display information about device availability derived from the number of critical alarms raised and cleared during a given time period, have both been renamed to Availability. | MTM-42188 |
| Device Management | A new tab called Services has been added to the device details view which provides an overview of the services running on that particular device. For details, see Device Management > Device details in the User guide. | MTM-42189 |
| Device Management | A new page for service details has been introduced which displays the data collected about the service on the Measurements, Alarms and Events tabs as known from the device details view. The new service context allows to implement further views and display them conditionally based on service capabilities. For details, see a href="https://cumulocity.com/guides/10.14.0/users-guide/device-management/#monitoring-device-services" class="no-ajaxy">Device Management > Monitoring device services in the User guide. | DM-379 |
| Device Management | In the Install software dialog, showing up on the Software tab of the device details view, you can search through software and select one for installation. Until now users could only filter by name. Now you can also filter by software type. | MTM-42185 |
| Device Management | In the device details view, the Measurements tab was only visible when the device had at least one measurement. Now the Measurements tab is always visible. | MTM-43891 |
| Device Management | In the Install software dialog on the Software tab of the device details view, if the device supports software types, the only software objects shown in the installation dialog will be those matching the defined software types for this device. | DM-382 |
| Device Management | The Shell tab in the device details now displays a full list of command operations providing realtime updates on operation status and device connectivity status.
Additionally, the Shell tab has been migrated as an Angular component. The AngularJS module c8y.deviceShell (@c8y/ng1-modules/devicemanagement-deviceShell/cumulocity.json) has been removed. |
DM-224 |
| Device Management | For devices supporting advanced software management, the Install software dialog lists all available software items matching the (pre)defined filter criteria (such as device type or software type). When a specific software version is selected the UI checks if the selected version is already present on the device. If the software item is already present on the device a warning is displayed to the user. The warning does not prevent the user from installing the software item again. It is up to the device agent to decide how to handle such operations. | DM-369 |
| Device Management | The "Asset properties" widget has been extended to display agent information with details on the agent version running on this device by default. | DM-663 |
| Device Management | For devices supporting advanced software management a new static SmartREST 2.0 template is available: 102,<serviceUniqueID>,<serviceType>,<serviceName>,<status> Devices may use this template to announce installed services to the Cumulocity IoT platform. | DM-275 |
| Loriot LoRa | The Loriot agent now stores the spreading factor information from the uplink message in the property c8y_SpreadingFactor in the device managed object. For details, see Loriot LoRa > Uplink message processing in the Protocol integration guide. |
DM-377 |
| 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 | MQTT | Additional MQTT static templates have been added: "SR template to set fragment hashcode" (130), "SR template to read fragment hashcode" (131) and "SR response template with fragment hashcode" (132). | MTM-42206 |
| OPC UA | The Swagger UI has been updated to the secure version 3.0.0 to address security vulnerabilities in the previous version. | MTM-43089 |
| 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 |
| SmartREST | For devices supporting advanced software management a new static SmartREST 2.0 template is available:
102,<serviceUniqueID>,<serviceType>,<serviceName>,<status>
Devices may use this template to announce installed services to the Cumulocity IoT platform. See also SmartREST 2.0 > MQTT static templates in the Reference guide. |
DM-275 |
| SmartREST | For devices supporting advanced software management a new static SmartREST 2.0 template is available:
104,<newServiceStatus>
Devices may publish such messages on topic s/us/<uniqueServiceID> to update the status of a service.
See also SmartREST 2.0 > MQTT static templates in the Reference guide. |
DM-413 |
| SmartREST | 3 Advanced Software SmartREST templates have been added:
140,softwareName,softwareVersion,softwareType,SoftwareUrl,...
141,softwareName,softwareVersion,softwareType,SoftwareUrl,...
142,softwareName,softwareVersion
140 overwrites the installed software of a device. 141 appends the provided software items to the current installed software. 142 removes the specified software items from the current installed software. These templates require the advanced-software-mgmt microservice to be subscribed. See also SmartREST 2.0 > MQTT static templates in the Reference guide. |
DM-389 |
| SmartREST | A new static SmartREST operation response template is available for the device to handle advanced software operations:
529,serial,softwareToBeUpdated1,version1,softwareType1,url1,action1,softwareToBeUpdated2,version2,softwareType2,url2,action2,...
See also SmartREST 2.0 > MQTT static templates in the Reference guide. |
DM-678 |
Fixes
| Component | Description | Issue |
|---|---|---|
| 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 | Fixed an issue where the UI was unresponsive after some measurement types had been deleted but were still considered as supported by the device, until the removal of the event had been fully processed by the server-side application. | MTM-41483 |
| Device Management | The layout of the Logs tab in the device details view has been improved, including icons and list styling. | MTM-41462 |
| Device Management | In the device profile details view, when opening the Install firmware dialog, the list of firmware items was not filtered correctly. This has been fixed by showing a filtered list with all firmware items that match the device type and the ones with undefined type as well. | DM-736 |
| Device Management | In the Logs tab of the device details, operations are now sorted descending by creation date, displaying newest operations on top. Scrolling down through the list allows to load and see older operations. | MTM-44461 |
| Device Management | A default device type c8y_DefaultDevice is now used if the type is not provided in the CSV file for full bulk device registration. |
MTM-45000 |
| Device Management | The scheduled device protocol update checks have been improved by querying based on recently changed device protocol items instead of retrieving all device protocols. | MTM-44024 |
| Device Management | For devices having the c8y_Firmware, c8y_Software/c8y_SoftwareList or c8y_Configuration fragment the device tabs Firmware, Software or Configuration are now displayed even if devices do not support the respective operations. In this case creating install/update operations is not possible via UI. |
MTM-45139 |
| Device Management | Fixed an issue with saving data in the "Device data" widget when the "LPWAN device" > "Provisioned" item was rendered as a text field. Now it's rendered as a checkbox and the data can be saved correctly. | MTM-45040 |
| 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. | MTM-44944 |
| LWM2M | The LWM2M post-registration operations are delivered for execution via the real-time channel. If the device is not internally subscribed yet, then the pending operations will now also be internally fetched by another process for execution. | MTM-42865 |
| LWM2M | When the protocol resource type is configured as a string it is not possible to receive numeric values which are expected to be processed as numeric data. The LWM2M agent only reads the data and logs a "Measurement creation is skipped for non-numeric value mapping:" message and creates an alarm. The values are not processed, because the agent doesn't expect the measurement as a string but only Boolean, integer or float.
This issue is now resolved. The 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 requirement won't be processed and an error message will be logged. See also LWM2M > 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 protocols 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 |
| 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. | DM-939 |
| LWM2M | 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 |
| 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 | 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 |
| OPC UA | Integer64 values below the range limits had been converted to double values when stored to the database. As a result the value lost precision because the last 4 digits were rounded. For event values and measurements we now support up to integer64 limits. Long values extending the long limit will be converted to double values with loss of precision (for example, 9223372036854775809 will be converted to 9.223372036854776E18). Due to several limitations the UI will still show rounded values, but the database includes the correct values. | MTM-38730 |
| OPC UA | The issue that static fragments, a property defined in the OPC UA device protocol for event/measurement/alarm creations, were not populated for measurements and events has been fixed. | MTM-45201 |
| SmartREST | Fixed Joda DateTime serialization for dates incoming to the platform as part of a custom SmartREST 2.0 request. | MTM-37812 |
| 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 |