Device management & connectivity

Release 10.15.0.536

Improvements

Component Description Issue
LWM2M The LWM2M agent realtime subscription for device operations now has a configurable limited time-to-live (TTL). The default TTL duration is 3 minutes. This setting may be configured on platform level. DM-3067

Release 10.15.0.526

Improvements

Component Description Issue
LWM2M Fixed an issue in the realtime API where a subscription marked as "non-retriable" could still be re-subscribed after re-establishing the underlying connection to the server, for example, after a Cumulocity core restart or network outage. MTM-56910
LWM2M The LWM2M agent's registration cleaner reads all the persisted LWM2M client registrations, then filters the registrations which are no longer valid and deletes them. In case of a huge number of LWM2M client registrations the registration cleaner consumes significant amount of memory, which can affect the LWM2M agent performance. With the current improvement, the registration cleaner only reads the LWM2M client registrations for which the registration time exceeds the timeout period. DM-3070

Release 10.15.0.519

Fixes

Component Description Issue
LWM2M Under certain rare conditions LWM2M devices were not able to connect due to an internal 409 conflict. The LWM2M agent is now more robust for such scenarios. DM-3044

Release 10.15.0.514

Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.

Release 10.15.0.513

Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.

Release 10.15.0.510

Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.

Release 10.15.0.505

Fixes

Component Description Issue
Device management The availability calculations in the "Availability" overview and for individual devices were not correct. Percentages were calculated for the respective time (24 hours, last 7 days and last 30 days) plus an additional 24 hours. The time interval has now been corrected. DM-2737

Release 10.15.0.496

Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.

Release 10.15.0.488

Fixes

Component Description Issue
Cloud Fieldbus Previously, the CAN bus protocol limited the representation of numeric values in the maximum value field, which posed limitations when dealing with exceptionally large numbers. To address this limitation, we have implemented a transformation mechanism that allows numeric fields to be defined using textual representations. DM-2691
LWM2M Setting up LWM2M agent DTLS connections by DTLS Connection IDs (CID) is now supported. By default this functionality is enabled. If you use LWM2M devices that support connection IDs, contact your platform administrator to apply additional settings or check if this feature is enabled. DM-2701

Release 10.15.0.458

Fixes

Component Description Issue
LWM2M A fail-safe mechanism to regularly get pending LWM2M device connector operations from the platform has been added in addition to the real-time mechanism in the LWM2M agent. This mechanism is beneficial when real-time connections between the LWM2M agent and the platform are unstable. DM-2652

Release 10.15.0.455

Fixes

Component Description Issue
Device management In the Device profiles page, when adding a repository item (software, firmware, configuration) if the device profile has a device type defined, the items shown either correspond to this device type or they don't have a device type specified. In some cases, repository items without a filter were not visualized in the window for adding an item. These items are now correctly shown. DM-2547
LWM2M During a large number of parallel LWM2M DTLS device connection requests, used for devices using PSK secured mode, the LWM2M agent was not able to handle all connections at the same time. This caused connection failures for these devices to the platform. In the LWM2M agent, the default settings for this part have been adjusted and made configurable to serve large parallel connections. DM-2651
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-2659

Release 10.15.0.452

Fixes

Component Description Issue
Device management On the Measurements tab in 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
LWM2M When reading an entire LWM2M object, which contains multiple object instances, in a simple read, observer or send operation, the LWM2M agent processed and stored only one of the resources of these object instances. This is now resolved and the LWM2M agent processes and stores all resource data from multiple object instances correctly. DM-2426
LWM2M If the LWM2M device observation frequency is high, for example, a few milliseconds, the LWM2M agent processed the same message multiple times, occupying a lot of resources. This is now resolved. The LWM2M agent no longer reprocesses the same observation request. DM-1823
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.15.0.434

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
LWM2M The LWM2M agent now correctly persists all registration update parameters. Previously, the LWM2M agent did not store changes of registration parameters, for example, updated registration lifetimes. This is now fixed. DM-2503
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.15.0.418

Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.

Release 10.15.0.412

Fixes

Component Description Issue
Device management In smart groups which are configured with sorting but without a filter, devices were not shown correctly. This has been addressed by correctly generating the required query. DM-2243
Device management Issues with flashing the device availability connection status have been fixed. MTM-51541
Loriot The memory limit for the Loriot microservice has been increased to 2Gi. DM-2427

Release 10.15.0.393

Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.

Release 10.15.0.386

Fixes

Component Description Issue
Device Management In the SmartREST templates 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 the device grid, issues with applying filters have been fixed. DM-2321
LWM2M Bulk device registrations and other operations being executed on the LWM2M connector device now show the status FAILED if a problem occurs. Prior to this change, partial failures were reported as SUCCESSFUL. DM-1951
LWM2M The LWM2M agent now ignores trailing commas at the end of object links in the registration request of a LWM2M client. DM-2342
LWM2M In certain cases, the registration couldn't be associated with a LWM2M 1.1 SEND request, leading to a 4.04 CoAP response. This is now fixed. DM-2270
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.15.0.377

Fixes

Component Description Issue
LWM2M Custom actions were not always executed if a LWM2M device used a SEND operation to report the whole LWM2M object data. This issue is now resolved and the custom actions are always executed for the resource instances for which they are defined. DM-2188
LWM2M The LWM2M agent is now able to properly convert the timestamps from the SenML data reported by the LWM2M client to a platform compatible date-time format for performing respective resource actions. DM-2150

Release 10.15.0.368

Fixes

Component Description Issue
OPC UA In case of bad connectivity or network delay it could happen that a gateway device went to the state of being disconnected. This resulted in operation execution being suspended. This issue is now resolved. DM-2037

Release 10.15.0.358

Improvements

Component Description Issue
LWM2M The performance of the migrateLwm2mDevices operation has been improved. New command line arguments have been introduced with the operation. A list of legacy LWM2M devices can be specified directly from the shell command. Moreover, the migration of the LWM2M client registration objects can be skipped by using an argument. For details, refer to LWM2M > LWM2M connector device > Migration of the LWM2M devices in the Protocol integration guide. DM-1866

Fixes

Component Description Issue
Connectivity Due to compatibility issues 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 When removing a device which has child devices, users can now select either to remove a device user or to remove all child devices. Prior to this change, it was possible to select both options in the UI, but such an action is not supported by the backend. MTM-45277
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
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 Two new LWM2M shell commands have been added.
- The new executelegacy command allows LWM2M execute requests with non-standard LWM2M parameters. The behavior of this operation resembles the semantics of the existing execute operation until version 10.15.
- The new coap shell command allows raw CoAP requests to devices to facilitate non-standard communication in exceptional cases.
For details, refer to LWM2M > Handling LWM2M shell commands in the Protocol integration guide.		 DM-2153
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.15.0.329

Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.

Release 10.15.0.327

Fixes

Component Description Issue
Device Management On the Services tab in the device details, the filter for the "Status" column did not work properly and returned no results when a filter was applied. This is now fixed. DM-2002
LWM2M During the LWM2M client registration, if the agent failed to find the registered device from the database due to a communication problem, an internal object related to the device managed object was automatically removed by the agent. Afterwards, LWM2M clients always failed to connect. This is now fixed and the internal object is only removed if the actual device managed object does not exist in the database. DM-2131
LWM2M Due to a limitation of the Leshan library used by the LWM2M agent, only device registration messages were supported where the LWM2M version is attached to the LWM2M object. The LWM2M agent has now been extended to also accept LWM2M registration messages where the LWM2M version is attached to the LWM2M object instance. DM-1893
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.15.0.309

Fixes

Component Description Issue
Device Management On the Shell tab in the device details, when a shell command operation is created, its name now corresponds to the command text if available. If no command text is available then it displays the operation description. DM-2069
Device Management In device list views, when a device was deleted, any related child devices were deleted as well. This functionality has now been enhanced. On device deletion, any existing child hierarchy types, that is, not only devices but also additions and assets are deleted accordingly. DM-2003
Device Management In events and alarms views, custom properties with numeric values were incorrectly parsed and displayed as dates in the Chrome browser. This is now fixed. DM-1999
LWM2M In the older Leshan demo client, the device registration requests for the Cumulocity IoT LWM2M demo device and possibly also some other devices could contain spaces between the core link separators. This was successfully handled by the LWM2M agent 10.14 and below but caused the LWM2M agent 10.15 and above to reject these device requests. Now, the LWM2M server accepts these requests again. The older device registration requests can be processed again. DM-2070
LWM2M In certain cases the migration of LWM2M devices registered on versions before 10.15 reported "Unable to process device" for certain devices. This happened due to adjustments to the device configuration, for example when editing the registration lifetime. With this fix, the migration logic robustness has been improved. DM-2022

Release 10.15.0.285

Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.

Release 10.15.0.278

Fixes

Component Description Issue
Device Management The Assign devices button is now disabled for users without the required permissions. MTM-50928
Device Management The resources dedicated to the advanced-software-mgmt microservice have been increased to ensure that it does not run out of memory for large software sets. DM-1213

Release 10.15.0.263

Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.

Release 10.15.0.262

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 The groups list on the Groups page now allows to filter by the grid's columns. DM-1836
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
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
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.15.0.249

Fixes

Component Description Issue
Cloud Fieldbus The Offset property field in the register configuration now accepts all values. MTM-48256
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 The option to copy the home page dashboard has been removed since it didn't provide useful functionality. DM-1869
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.15.0.234

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
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.15.0.218

Improvements

Component Description Issue
LWM2M The LWM2M bulk registration now also supports the creation of external IDs and extra fragments in managed objects like it is supported in the general bulk registration. Furthermore, it is now possible to assign LWM2M devices to groups as part of the LWM2M bulk registration process. DM-1544

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
LWM2M A security vulnerability CVE-2022-39368 was found in Leshan 2.0.0-M8 and Californium 3.6.0. The dependencies were updated to the latest versions Leshan 2.0.0-M9 and Californium 3.7.0. DM-1734
LWM2M On the Objects tab in the device details, if you select an object containing a timestamp resource, the text box which displays the timestamp now receives the correct timestamp data type and no error message is displayed. DM-1673

Release 10.15.0.207

Fixes

Component Description Issue
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.15.0.198

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

Release 10.15.0.190

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
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 submitting manual changes. DM-1623
Device Management In the Device protocols page, filtering for specific device protocols using a search term is now more efficient. The list is filled and displayed faster with the desired search results. DM-912

Release 10.15.0.175

Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.

Release 10.15.0.172

Improvements

Component Description Issue
Actility The AS ID, AS Key, Admin, and Core API versions can now be configured through the Actility connection in the UI instead of in the properties file. DM-1142

Fixes

Component Description Issue
Device Management On a device grid, when applying filters to columns, this is now saved in the configuration of the grid, and when the user returns to the same page the filters will be visualized and applied. DM-1228
Device Management On a device grid, the clearing filters functionality was not persisting the removal of filters. This issue has been fixed. Whenever the user clears the filters on the grid the information is stored correctly in the configuration. DM-1483
Device Management In the device list view, when a custom column is added it is always positioned after all default columns. DM-1309
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
Device Management The Create smart group button in the All devices list is clickable again when all column filters are cleared. DM-1541
Device Management The device registration wizard had several layout and functionality issues which were fixed by aligning them to the default platform user experience. DM-1335
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.15.0.114

Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.

Release 10.15.0.79

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 The OPC UA artefacts on Edge have the JVM heap size defined relative to the defined memory limit for the container. Security improvements have been added to limit the Docker capabilities. DM-1327
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.15.0.43

Fixes

Component Description Issue

Release 10.15.0.25

Improvements

Component Description Issue
Actility The Actility agent used to support only one connectivity setting per tenant. Now multiple connections can be configured per tenant. For details, refer to Actility LoRa in the Protocol integration guide. DM-543
Actility The Actility device registration screens have been migrated to Angular and the device registration now follows the new device registration flow. For details, see Actility LoRa > Registering LoRa devices in the Protocol integration guide. DM-652
Device Management A new static SmartREST template is available in MQTT:
122,<name>,<version>,<url>,<maintainer>
It allows devices to provide information about the agent running on them. See also MQTT static templates in the Reference guide.		 DM-813
Device Management When one or more devices are associated with an LNS connectivity account then the account can't be deleted or the account name can't be updated. DM-311
Device Management In the Child devices tab of the device details, the groups column has been removed. MTM-45322
Device Management To improve the security during the registration of a new device, a security token policy has been added. The security token policy settings can be configured by the tenant options:
{category: 'device-registration', key: 'security-token.policy', value}
For details, see Device Management > Connecting devices in the User guide. 		MTM-37550
Device Management The general bulk registration component has been migrated from AngularJS to Angular and now follows the new device registration flow. See also Device Management > Connecting devices in the User guide. DM-718
Device Management The new All devices list can read old configurations for the column setup so that the legacy format can be safely deprecated and removed in the future. DM-909
Device Management The column configuration is now stored in a separate object for every different device grid. This allows to have different grid configurations for different pages in our platform. DM-908
Device Management The device grid component (c8y-device-grid) used in various pages in the Device Management application (for example, in the Subassets tab) now allows user-configured columns to be added. DM-907
Device Management The device registration process has been extended by a customizable bulk registration process. Based on the application extension fragment of the deployed microservice, an additional menu entry will be shown in the Register device dropdown menu. For details see Device Management > Extensible device registration in the User guide. DM-320
LWM2M The current LWM2M agent supports the LWM2M protocol v1.1. This allows the LWM2M agent to:
- communicate with a device which supports LWM2M v1.1
- send composite read, observe and write operations to a LWM2M v1.1 device and read the composite data sent from the device
- read single or composite device sent resource data 		DM-397
LWM2M The Java library of the LWM2M agent has been upgraded to version 11. DM-367
LWM2M If the data sent from the client contains the common timestamp resources 5518 and 6050 or the specific timestamp resource for object 6, then the LWM2M agent may use this timestamp. This can be enabled setting the device property enableResourceLevelTimestamp. Currently this property is set to "false" because of backward compatibility, so by default the LWM2M agent still uses it's own date and time for the measurement data. DM-850
MQTT The MQTT message handling has been improved. This results in reduced load on the platform side when many devices disconnect and reconnect in a short period of time, for example due to a network outage. MTM-45142
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
Sigfox The Sigfox agent used to support only one connectivity setting per tenant. Now multiple connections can be configured per tenant. For details, refer to For details, refer to Sigfox in the Protocol integration guide. DM-543
Sigfox The Sigfox device registration screens have been migrated to Angular and the device registration now follows the new device registration flow. For details, see Actility LoRa > Registering Sigfox devices in the Protocol integration guide. DM-651

Fixes

Component Description Issue
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 The groups filter in the Child devices tab has been removed. MTM-45322
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
Device Management The event list and alarm list used to display date values of non-standard properties as strings in simplified extended ISO format (for example, "2022-05-10T00:33:54.317Z"). Now non-standard date properties are formatted as date and time string according to locale (for example, "10 May 2022, 03:33:54"). DM-876
Device Management In the operations list each single operation is labeled by its description property. If no description is available the text property nested in the c8y_Command fragment will be shown instead now (this usually applies to shell operations). If that also isn't available the default text "No command text or description available" is shown. MTM-46629
Device Management When there are too many delete operations to be handled in the background, the system will respond with status "429 - Too Many Requests". MTM-45526
Device Management Fixed an issue with bulk device registration via CSV file upload which occurred on Windows systems that do not recognize *.csv files as text/csv MIME type. This was the case when Excel is not installed on the Windows machine as installing it adds a registry entry for such content type. MTM-40297
Device Management Configurations with external URLs are not supported by devices that only support legacy configurations. If a user sends such a configuration to a legacy device the result will be an empty preview window with no binary to be shown. On configuration creation, above the external URL in the information popup, a corresponding description has been added for the users to be aware of this.
 DM-1096
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 Previously MQTT QoS in consecutive subscriptions to one topic could not be lowered. For example, when subscribing with QoS=2, and unsubscribing and subscribing to the same topic with QoS=1, the platform ignored this and still worked with QoS=2. Now it works as requested. MTM-38437
OPC UA The OPC UA gateway now performs an availability check on the IoT platform before starting up. DM-576