10.18.0.405
Info
These release notes refer to build versions:
- cumulocity: 1018.0.405
- ui-c8y: 1018.0.259
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
10.18.0.401
Info
These release notes refer to build versions:
- cumulocity: 1018.0.401
- ui-c8y: 1018.0.255
Fixes
| Product area | Description | Issue | Build version | Build comp. |
|---|---|---|---|---|
| Device Management | An old data model migration mechanism was erroneously removing installed software information from devices when the Advanced Software Management microservice was resubscribed or restarted. This mechanism has entirely been removed so that existing data is no longer modified. | DM-3475 | 10.18.0.398 | cumulocity |
| Device Management | The properties library schema definition for the c8y_SoftwareList fragment did not match the actual managed object properties. Hence, when the Software property was selected in the "Device data" widget no data was shown. The property is now called Software list and displays all software items contained in the c8y_SoftwareList fragment. |
DM-3470 | 10.18.0.254 | ui-c8y |
10.18.0.389
Info
These release notes refer to build versions:
- cumulocity: 1018.0.389
- ui-c8y: 1018.0.247
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
10.18.0.378
Info
These release notes refer to build versions:
- cumulocity: 1018.0.378
- ui-c8y: 1018.0.246
Fixes
| Product area | Description | Issue | Build version | Build comp. |
|---|---|---|---|---|
| LWM2M | In the custom action configuration of LWM2M device protocol resources, the exchange to another external decoder microservice was not effective. This issue is now resolved. | DM-2674 | 10.18.0.373 | lwm2m |
10.18.0.372
Info
These release notes refer to build versions:
- cumulocity: 1018.0.372
- ui-c8y: 1018.0.244
Fixes
| Product area | Description | Issue | Build version | Build comp. |
|---|---|---|---|---|
| LWM2M | Large LWM2M bulk registrations and removals were unreliable due to a race condition. This issue has been fixed. | DM-3141 | 10.18.0.367 | lwm2m |
10.18.0.366
Info
These release notes refer to build versions:
- cumulocity: 1018.0.366
- ui-c8y: 1018.0.240
Fixes
| Product area | Description | Issue | Build version | Build comp. |
|---|---|---|---|---|
| LWM2M | A race condition encountered during simultaneous LWM2M client de-registration and new registration requests has been resolved, improving overall robustness in the registration process. | DM-3124 | 10.18.0.360 | cumulocity |
10.18.0.356
Info
These release notes refer to build versions:
- cumulocity: 1018.0.356
- ui-c8y: 1018.0.233
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
10.18.0.348
Info
These release notes refer to build versions:
- cumulocity: 1018.0.348
- ui-c8y: 1018.0.225
Fixes
| Product area | Description | Issue | Build version | Build comp. |
|---|---|---|---|---|
| Device Management | Sorting and filtering by creationTime and lastUpdated is no longer supported by the Inventory API, therefore it has been replaced by sorting and filtering on creationTime.date and lastUpdated.date properties only. |
DM-3112 | 10.18.0.220 | ui-c8y |
10.18.0.341
Info
These release notes refer to build versions:
- cumulocity: 1018.0.341
- ui-c8y: 1018.0.215
Fixes
| Product area | Description | Issue | Build version | Build comp. |
|---|---|---|---|---|
| LWM2M | An issue prevented position information from the location object 6 to be populated into the device managed object if parts of the coordinates were reported with too high precision. This issue has been fixed. The LWM2M component now rounds the values correctly to the supported level of precision. | DM-3136 | 10.18.0.336 | cumulocity |
10.18.0.329
Info
These release notes refer to build versions:
- cumulocity: 1018.0.329
- ui-c8y: 1018.0.213
Fixes
| Product area | Description | Issue | Build version | Build comp. |
|---|---|---|---|---|
| Device Management | In Chrome, custom event and operation fields having 0 or '0' as a value were incorrectly parsed and displayed as date. This is now fixed. | DM-3098 | 10.18.0.207 | c8y-ui |
10.18.0.320
Info
These release notes refer to build versions:
- cumulocity: 1018.0.320
- ui-c8y: 1018.0.205
Improvements
| Product area | Description | Issue | Build version | Build comp. |
|---|---|---|---|---|
| LWM2M | The LWM2M agent realtime subscription for device operations now has a limited Time-To-Live (TTL) duration. The default TTL duration is 3 minutes. This setting may be configured on platform level. | DM-3067 | 10.18.0.304 | cumulocity |
10.18.0.308
Info
These release notes refer to build versions:
- Core: 10.18.0.308
- UI: 10.18.0.201
Fixes
| Product area | Description | Issue | Build version | Build comp. |
|---|---|---|---|---|
| Device management | Fixed an issue with the German translation of the "Get snapshot from device" operation description and several other similar cases. | MTM-54257 | 10.18.0.198 | UI |
10.18.0.298
Info
These release notes refer to build versions:
- Core: 10.18.0.298
- UI: 10.18.0.191
Fixes
| Product area | Description | Issue | Build version | Build comp. |
|---|---|---|---|---|
| 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 | 10.18.0.288 | Core |
| Device management | The sms-gateway agent sent outgoing requests with the content type application/xml which is not recognized by the DCP API. This has been fixed and outgoing requests are now sent with the content type application/json. |
DM-3003 | 10.18.0.296 | Core |
10.18.0.281
Info
These release notes refer to build versions:
- Core: 10.18.0.281
- UI: 10.18.0.186
Fixes
| Product area | Description | Issue | Build version | Build comp. |
|---|---|---|---|---|
| Device management | Simulators did not use inventory POST/PUT templates properly as they did not specify any ID fields for the object they created/updated. This has now been resolved by adding the corresponding fields ID, External ID and External ID type depending on the SmartREST template used as instruction. |
DM-2853 | 10.18.0.172 | UI |
| Device management | Previously, when loading measurement charts data, there was a performance issue if the measurement series had no units defined, depending on the total number of measurement records. This issue has been addressed and measurements series now load efficiently regardless of units being defined or not. | DM-2785 | 10.18.0.173 | UI |
| OPC UA | When the OPCUA Gateway created an event with a non-numeric data type, the data value was always persisted with 0 and only events containing a numeric value were persisted correctly. This issue is now resolved and the event values are represented correctly for any type of data. | DM-2754 | 10.18.0.266 | Core |
10.18.0.261
Info
These release notes refer to build versions:
- Core: 10.18.0.261
- UI: 10.18.0.170
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
10.18.0.245
Info
These release notes refer to build versions:
- Core: 10.18.0.245
- UI: 10.18.0.164
Fixes
| Product area | Description | Issue | Build version | Build comp. |
|---|---|---|---|---|
| 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 | 10.18.0.154 | UI |
| Device management | After editing a device protocol details page and leaving the page, a confirmation pop-up is now always properly shown. | DM-2700 | 10.18.0.154 | UI |
| Device management | Fixed an issue in the data grid and device grid components where specific string, Boolean, and numeric cell values were wrongly formatted as dates. | DM-2746 | 10.18.0.150 | UI |
10.18.0.229
Info
These release notes refer to build versions:
- Core: 10.18.0.229
- UI: 10.18.0.151
Fixes
| Product area | Description | Issue | Build version | Build comp. |
|---|---|---|---|---|
| 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 | 10.18.0.136 | UI |
| Device management | Fixed an issue in the data grid and device grid components where specific string, Boolean, and numeric cell values were wrongly formatted as dates. | DM-2746 | 10.18.0.150 | UI |
| 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 | 10.18.0.199 | Core |
10.18.0.174
Info
These release notes contain all changes until build versions:
- Core: 10.18.0.174
- UI: 10.18.0.125
Improvements
| Product area | Description | Issue | Build version | Build comp. |
|---|---|---|---|---|
| Device management | The Device Management home page now also provides a customizable dashboard so that users can add customized widgets. | DM-1644 | 10.17.194.0 | UI |
| Device management | Added support for rendering dropdown fields in JSON Schema Formly in the extensible device registration. | DM-1921 | 10.17.67.0 | UI |
| Device management | The step headers "1, 2, 3 ..." of the "Connect smartphone" wizard can no longer be clicked. The navigation now works exclusively via the buttons in the footer of the wizard. Moreover, the text which is displayed if an error occurs during the registration has been revised. If the last step ends in an error message, the last header now also reflects this error status. | DM-1930 | 10.17.25.0 | UI |
| 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 | 10.18.0.5 | Core |
| LWM2M | A LWM2M device can now completely be deleted from the devices list without an additional clean-up operation. This is done in the same way as any other device is deleted, that is, via the delete icon in the respective row. | DM-867 | 10.17.173.0 | UI |
| LWM2M | If event logging is enabled for the LWM2M microservice from the configuration file of the LWM2M agent, the agent now creates new logs as events with detailed information about the reason of failure when a device operation is not executed due to the device connectivity. | DM-231 | 10.17.37.0 | Core |
| OPC UA | The OPC UA device gateway can now be run with Thin Edge. The gateway device is automatically created as a child of the Thin Edge device. For more information on the configurations, refer to the Thin Edge section in OPC UA > Gateway configuration and registration in the Protocol integration guide. | DM-887 | 10.17.174.0 | Core |
| SmartREST 2.0 | Added the SmartREST static template 143 for setting device-supported software types. | DM-1820 | 10.17.224.0 | Core |
| SmartREST 2.0 | Added SmartREST static templates for updating the operation status by its internal ID. 504 for setting the status to executing, 505 for failed, 506 for successful. | DM-1832 | 10.17.188.0 | Core |
| SmartREST 2.0 | Added SmartREST static templates for requesting the device's internal ID (123 for request, 124 for response). | DM-1821 | 10.17.188.0 | Core |
| SmartREST 2.0 | Added the SmartREST static template 201 for creating measurements with multiple fragments and series. | DM-1860 | 10.17.128.0 | Core |
Fixes
| Product area | Description | Issue | Build version | Build comp. |
|---|---|---|---|---|
| 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 | 10.18.0.113 | Core |
| 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 | 10.18.0.118 | UI |
| Device management | The device list now shows complex columns like c8y_SoftwareList correctly after converting them to strings. |
DM-2410 | 10.18.0.78 | UI |
| Device management | Issues with flashing the device availability connection status have been fixed. | MTM-51541 | 10.18.0.73 | Core |
| Device management | In the device grid, issues with applying filters have been fixed. | DM-2321 | 10.18.0.57 | 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.18.0.55 | UI |
| 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.262.0 | UI |
| Device management | On the Software tab in the device details, the Reload button now correctly updates the Installed software list. | DM-2005 | 10.17.141.0 | 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.118.0 | 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.74.0 | 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.73.0 | UI |
| Device management | The Assign devices button is now disabled for users without the required permissions. | MTM-50928 | 10.17.16.0 | UI |
| Loriot | The memory limit for the Loriot microservice has been increased to 2Gi. | DM-2427 | 10.18.0.74 | 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.170.0 | Core |
| 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 | 10.18.0.170 | Core |
| 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 platform connection failures for the devices. In the LWM2M agent, the default settings for this part have been adjusted and made configurable to serve large parallel connections. | DM-2651 | 10.18.0.162 | Core |
| 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 | 10.18.0.155 | Core |
| 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 | 10.18.0.141 | Core |
| 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 | 10.18.0.129 | 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.18.0.57 | 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.18.0.54 | 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.18.0.47 | 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.18.0.46 | 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.18.0.43 | 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.18.0.37 | 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.18.0.6 | Core |
| LWM2M | In the Device objects tab, an issue with entering a parameter in the Execute with parameters field has been resolved. | DM-2160 | 10.17.226.0 | UI |
| LWM2M | The LWM2M agent now ensures that a LWM2M client registration is expired and removed from the database if the LWM2M client does not update its registration within the respective registration lifetime period. | DM-1895 | 10.17.190.0 | 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.178.0 | Core |
| LWM2M | The LWM2M device type can freely be 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.171.0 | UI |
| 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 | 10.17.169.0 | Core |
| 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.107.0 | 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.105.0 | Core |
| LWM2M | The Objects tab now correctly displays JSON values in string fields. | DM-1973 | 10.17.47.0 | Core |
| LWM2M | The LWM2M agent now provides a better processing rate of the external decoder events by parallelizing their execution. | DM-1840 | 10.17.36.0 | Core |
| OPC UA | The endpoint validation happening during the connection to an OPC UA server can now optionally be disabled. This can be done in the gateway configuration by changing the gateway.connectivity.validateDiscoveredEndpoints setting to "false". Alternatively, it can be controlled via the OPC UA server managed object by setting the fragment validateDiscoveredEndpoints to "false". For details, refer to OPC UA in the Protocol integration guide. |
DM-2425 | 10.18.0.157 | Core |
| OPC UA | The application of OPC UA device protocols was unreliable when there were more than 1000 protocols. This is now fixed. | DM-2634 | 10.18.0.155 | Core |
| 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 | 10.18.0.128 | 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.18.0.30 | Core |