| Cloud Fieldbus |
The Offset property field in the register configuration now accepts all values. |
MTM-48256 |
10.16.119.0 |
n/a |
| 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 |
10.17.0.112 |
Core |
| Device management |
The device list now shows complex columns like c8y_SoftwareList correctly after converting them to strings. |
DM-2410 |
10.17.0.211 |
UI |
| Device management |
In the device grid, issues with applying filters have been fixed. |
DM-2321 |
10.17.0.164 |
UI |
| 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 |
10.17.0.159 |
UI |
| 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 |
10.17.0.119 |
Core |
| 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 |
10.17.0.103 |
UI |
| Device management |
On the Services tab in the device details, the filter for the "Status" column did not work properly and didn't return any results when a filter was applied. This is now fixed. |
DM-2002 |
10.17.0.87 |
UI |
| Device management |
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 |
10.17.0.83 |
Core |
| Device management |
On the Software tab in the device details, the Reload button now correctly updates the Installed software list. |
DM-2005 |
10.17.0.64 |
UI |
| 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 |
10.17.0.46 |
UI |
| 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 |
10.17.0.34 |
UI |
| 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 |
10.17.0.33 |
UI |
| Device management |
On bulk device registration views the Upload button is now disabled if there is no file selected or if the selected file is invalid. |
DM-1641 |
10.16.260.0 |
n/a |
| 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 |
10.16.260.0 |
n/a |
| Device management |
The "Groups" column in the device list formerly displayed 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 |
10.16.246.0 |
n/a |
| Device management |
The option to copy the home page dashboard has been removed since it didn't provide useful functionality. |
DM-1869 |
10.16.191.0 |
n/a |
| Device management |
On the Measurements tab in the device details, a tooltip has been added which shows the whole values in case of truncated values in the Y-axis. Moreover, the information is provided that you can see the whole values by hovering over the axis. |
MTM-48603 |
10.16.142.0 |
n/a |
| Device management |
Devices can now send installed software information to the advanced-software-mgmt microservice without including the URL and software type. These parameters were incorrectly required before and are now made optional. |
DM-1431 |
10.16.129.0 |
n/a |
| Device management |
Fixed an issue where users could not find a location on the map based on the address they entered. |
MTM-49644 |
10.16.104.0 |
n/a |
| 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 |
10.16.103.0 |
n/a |
| Device management |
In the Software repository page, sorting for the column "Device type" did not function properly. This issue is now fixed. |
DM-1712 |
10.16.103.0 |
n/a |
| 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 |
10.16.31.0 |
n/a |
| 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 |
10.16.12.0 |
n/a |
| Device management |
The device registration wizard had several layout and functionality issues which were fixed by aligning it to the default platform user experience. |
DM-1335 |
10.16.8.0 |
n/a |
| Digital Twin Manager |
For assets created with the Digital Twin Manager, custom properties of the type "number" with the value "0" are now displayed properly as "0", not as "Undefined". |
MTM-49870 |
10.16.185.0 |
n/a |
| Loriot |
The memory limit for the Loriot microservice has been increased to 2Gi. |
DM-2427 |
10.17.0.182 |
Core |
| 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 |
10.17.0.81 |
Core |
| 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 |
10.17.0.158 |
Core |
| 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 |
10.17.0.157 |
Core |
| LWM2M |
The LWM2M Agent now ignores trailing commas at the end of object links in the registration request of a LWM2M client. |
DM-2342 |
10.17.0.156 |
Core |
| 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 |
10.17.0.154 |
Core |
| 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 |
10.17.0.146 |
Core |
| 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 |
10.17.0.127 |
Core |
| 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 enables making 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 |
10.17.0.122 |
Core |
| 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 |
10.17.0.82 |
core |
| LWM2M |
The LWM2M device type can be freely chosen by the user. Therefore, devices which do not have the type "c8y_lwm2m" but still are LWM2M devices now also show the LWM2M bootstrap parameters view. |
DM-2066 |
10.17.0.72 |
UI |
| 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 |
10.17.0.47 |
Core |
| 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 |
10.17.0.41 |
Core |
| LWM2M |
A new LWM2M device configuration option has been added to control if the persisted values in the Objects tab get removed in case a read, write or observe observation fails. The option is configurable in the new single device registration in the advanced settings or by having the "c8y_GenericUI_retainOldValuesIfError" fragment in the LWM2M device managed object. For details refer to LWM2M > Registering LWM2M devices > Advanced settings in the Protocol integration guide. |
DM-1560 |
10.16.246.0 |
n/a |
| 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 |
10.16.211.0 |
n/a |
| 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 |
10.16.206.0 |
n/a |
| 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 |
10.16.206.0 |
n/a |
| LWM2M |
- The LWM2M FOTA process now raises an alarm if the observation to the update state resource of object 5 cannot be established.
-All CoAP requests sent to devices and corresponding responses are now consistently logged. |
DM-1711 |
10.16.161.0 |
n/a |
| 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 |
10.16.119.0 |
n/a |
| 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 |
10.16.114.0 |
n/a |
| 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 |
10.16.113.0 |
n/a |
| 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 |
10.16.12.0 |
n/a |
| 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 |
10.17.0.166 |
Core |
| OPC UA |
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 |
10.17.0.142 |
Core |
| OPC UA |
On editing the OPC UA device details, the data reporting value is now always saved properly. |
DM-1668 |
10.16.102.0 |
n/a |
| OPC UA |
Canceling the editing of a variable in the OPC UA device protocol no longer resets the variable data subscriptions to default. |
DM-592 |
10.16.79.0 |
n/a |
| OPC UA |
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 |
10.16.13.0 |
n/a |