Release 10.10.0.41
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.10.0.36
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.10.0.35
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.10.0.33
Fixes
| Component | Description | Issue |
|---|---|---|
| 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 |
Release 10.10.0.32
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | A missing tooltip has been added with information on how to provide a file path when adding a new configuration object to the configuration repository. | MTM-44752 |
Release 10.10.0.31
Fixes
| Component | Description | Issue |
|---|---|---|
| Device Management | 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 |
Release 10.10.0.30
Improvements
| Component | Description | Issue |
|---|---|---|
| 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 |
Release 10.10.0.28
Fixes
| Component | Description | Issue |
|---|---|---|
| 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 | String resources can now again be mapped into measurement values, that is the LWM2M agent accepts numeric (integer and float) values sent as a string. In addition also the following strings will be treated as numeric values:
- Any positive or negative numeric sequence with leading 0 (zero) will be interpreted as octal value, but will be transformed and stored as a decimal number - Any positive or negative alphanumeric sequence containing letters from A to F, starting with 0x will be interpreted as hex value, but will be transformed and stored as a decimal number Strings which do not meet these requirement won't be processed and an error message will be logged. See also LWM2M > Overview in the Protocol integration guide. |
MTM-43661 |
Release 10.10.0.26
Fixes
| Component | Description | Issue |
|---|---|---|
| LWM2M | The LWM2M compatibility with certain versions of the Java 8 JRE has been improved. However, we recommend you to use Java 11 for executing LWM2M. | MTM-42596 |
Release 10.10.0.24
Fixes
| Component | Description | Issue |
|---|---|---|
| LWM2M | The resourceValue fragment added to events and alarms now works with opaque resources. Measurements cannot be created with opaque resource values. If enabled, it will create a warning alarm if non-numeric/non-Boolean values are received. Additionally, the type for no-mapping-known alarms has been improved by including the object ID. See also LWM2M > LWM2M device protocols in the Protocol integration guide. | MTM-41682 |
Release 10.10.0.21
Fixes
| Component | Description | Issue |
|---|---|---|
| LWM2M | When a LWM2M device registration update comes with a different port or address than the previous registration, for example, the LWM2M registration update comes with a new COAP port due to the load balancer's idle timeout being exceeded, all ongoing operations that are not finished meanwhile will be set back to PENDING state, instead of directly canceling them. | MTM-41981 |
Release 10.10.0.20
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.10.0.19
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.10.0.18
Info
There have not been any significant improvements or fixes related to this component since the last Maintenance release.
Release 10.10.0.17
Fixes
| Component | Description | Issue |
|---|---|---|
| LWM2M | The attribute C8Y.lwm2m.enableBootstrapPSKFragmentFallback has been added to the agent's default configuration. If enabled, the LWM2M agent will find the bootstrap PSK ID from the fragments ("bootstrap psk_id") if it cannot be found from the external IDs. See LWM2M > Registration of PSK-secured devices in the Protocol integration guide for more information on the fields required for a bootstrap PSK connection. |
MTM-40632 |
Release 10.10.0.14
Fixes
| Component | Description | Issue |
|---|---|---|
| LWM2M | In order to update the value of attributes associated with any object, instance, or resource, the write attribute command must be used with the desired values. The attributes nomenclature for the shell command has been updated as per the LWM2M 1.0 specification. The attribute greater than must be written as gt instead of greater; less than must be written as lt instead of less, and step as st instead of step. For example: writeattr /{Object ID}/{ObjectInstance ID}/{ResourceID}?pmin={minimum period}&pmax={maximum period}>={greater than}<={less than}&st={step}. See also LWM2M > Handling LWM2M shell commands in the Protocol integration guide. |
MTM-40674 |
Release 10.10.0.12
Improvements
| Component | Description | Issue |
|---|---|---|
| Connectivity | The Connectivity microservice has been extended with a cache for data from the configured connectivity provider to prevent timeout issues. The cache duration can be configured in seconds along with the regular SIM provider settings in the Administration application under Settings > Connectivity. | MTM-38819 |
Fixes
| Component | Description | Issue |
|---|---|---|
| LWM2M | LWM2M bootstrap via PSK requires the existence of an external ID, namely c8y_BootstrapPskId. Before, there was an undocumented fall-back behavior that allowed for bootstrapping LWM2M devices without this external ID if the device could be found using a corresponding fragment. If bootstrap is now carried out using bootstrap in PSK and the external ID is missing, the external ID is automatically recreated if the device can be found in the inventory. Note that this is a temporary and deprecated reestablishment of the fallback behavior which does not remove the need of the external ID c8y_BootstrapPskId. | MTM-39371 |
Release 10.10.0.8
Improvements
| Component | Description | Issue |
|---|---|---|
| Cloud Remote Access | Security for the Cloud Remote Access configuration has been improved. The data broker will not transfer the Cloud Remote Access configuration managedObjects fragment to the destination tenant. | MTM-30013 |
| Connectivity | The connectivity agent has been extended to support the Telefonica SIM connectivity provider. | MTM-36877 |
| Device Monitoring | Audit records will now be created if the device availability is one of: enabled, disabled, the interval assigned to the device has changed, the device is set into maintenance state. | MTM-36563 |
| LoRa | LoRa device registration warning messages have been improved in order to provide more accurate information. | MTM-23215 |
| LoRa Actility, Sigfox | For more clarity, the Little-endian checkbox will now be disabled if the Number of bits field has a value less than 8, as "little-endian" in this case is not supported. | MTM-32844 |
| LWM2M | After a LWM2M device is registered against Cumulocity IoT, post registration operations (if specified) will be sent to the device. With this enhancement, only post registration operations which carry a path to an existing LWM2M object on the respective device and operations without a path will be sent. This enhancement optimizes the communication between the platform and the device. | MTM-36990 |
| LWM2M | The performance for custom LWM2M decoders has been improved by allowing for multiple threads in order to be able to process events in parallel. | MTM-29681 |
| LWM2M | The firmware update process is now automatically cancelled when the firmware update operation is deleted. | MTM-38583 |
| OPC UA | The OPC UA Java library has been upgraded to Java 11. | MTM-38045 |
| OPC UA | For an OPC UA device protocol, when setting the option "Limit device protocol to a set of servers", the server ID is now also displayed in the list, and servers can be searched by ID in addition to the name. | MTM-31660 |
| OPC UA | The subscription to GeneralModelChangeEventType and SemanticChangeEventType can be enabled or disabled using a property (subscribeModelChangeEvent) while configuring each OPC UA Server. | MTM-37672 |
| OPC UA | Improved the HTTP POST retry mechanism by prioritizing the requests, introducing max queue size, no retry HTTP codes. | MTM-37227 |
| OPC UA | To optimize performance, alarm mappings are now stored in-memory with a file based backup & recovery mechanism. This is to minimize REST calls to the event API. | MTM-35291 |
| OPC UA | OPC UA now supports regular expressions in browse path mappings. For details, see OPC UA > Device protocols and OPC UA > Rest API in the Protocol integration guide. | MTM-38009 |
| OPC UA | Inventory update processing modes for OPC UA-related managed objects can now be configured in the gateway, see OPC UA > Gateway configuration and registration > Additional customizations in the Protocol integration guide. | MTM-38279 |
| Sigfox | When registering a Sigfox device the Sigfox certificate key is validated against the pattern described in https://storage.googleapis.com/public-assets-xd-support-sigfox-production-338901379285/att11606881-Sigfox_ready_end_product_certificate.pdf . If the pattern is incorrect an error message will be shown allowing the user to provide the correct key. | MTM-38146 |
| Sigfox | The generation of the user password for Sigfox callbacks has been improved to align with the Cumulocity IoT password policy guidelines. | MTM-26010 |
Fixes
| Component | Description | Issue |
|---|---|---|
| Bulk operations | In the operations section of the bulk operation details, long descriptions broke the correct formatting and visibility of table elements. This has been fixed by limiting/truncating the description text. | MTM-38433 |
| Bulk operations | Bulk operations with status EXECUTING have a cancel option. When all single operations had been created and the user tried to cancel the bulk operation an error occurred. This has been resolved by removing the option to cancel a bulk operation when all its single operations have already been created. | MTM-38907 |
| Bulk operations | Previously bulk operations that were started but not completed became stuck in platform failover scenarios. A mechanism to resume these bulk operations upon restart has been introduced. | MTM-38171 |
| Device Management | The sorting of groups and devices has been changed to be consistent in all places. Previously the sorting of groups and devices in the navigator was not consistent with the sorting in the Subassets tab. Now the sorting will be case-sensitive in both cases, for example "AAA BBB CCC aaa bbb..." instead of "aaa AAA bbb CCC ccc...". | MTM-36844 |
| Device Monitoring | Under certain circumstances, the availability status of devices could show wrong information. This has been fixed so the availability status now is always accurate. The availability calculation now also takes into account correctly the setting for "0" as documented. | MTM-36103 |
| Device Monitoring | In the case that availability monitoring for a device was deactivated, alarms were still incorrectly being raised to indicate a device was unavailable. This behaviour has now been corrected. | MTM-37863 |
| LWM2M | The LWM2M agent did not correctly reflect the status of an operation when it was cancelled in the UI. The agent has been modified to check if an operation has been cancelled before updating the status of that operation. | MTM-37101 |
| LWM2M | The LWM2M agent now processes also values that are part of an observe response message. | MTM-37731 |
| MQTT | Error messages were improved to clearly indicate the root cause for issues when devices using an MQTT connection and device certificates fail to authenticate against the platform. | MTM-36963 |
| MQTT | The JWT token can now be generated for devices authenticated with certificates regardless of the preferred login mode set (Basic, OAuth Internal). Previously it was only possible when the login mode was set to OAuth Internal. | MTM-35965 |
| OPC UA | The OPC UA UI now correctly shows an error message if the queue size or the sampling interval is too large. | MTM-37556 |
| OPC UA | If measurements overflow the range of a long value while converting from Java BigDecimal we convert them now to double values. | MTM-37719 |
| OPC UA | Improved extended node ID parsing with semicolons in the node ID value. | MTM-37294 |
| Smartrest 2.0 | The SmartRest response template CSV preview is now correctly displaying all data. | MTM-29297 |
| UI | Missing German and French translations for LWM2M device operations in the object tab have been added. | MTM-37936 |